It's more of a theory at this point. I have an SR opened regarding the issue, but the engineer has only stated that it's a known issue and that I need to install update 2...which is doesn't sound feasible since it was just released a few weeks ago.  He refuses to provide any details on the root cause.  It seems to only occur when new VMs are provisioned.