When starting Sandbox on VMWare it loads and then stops at some point. The last message seen on the screen is
Started Network Manager Script Dispatcher Service.
See attached screenshot.
Then it stay at this stage forever (I waited about 1 hour) and computer utilizes 100% CPU.
Below are some last messages from vmware.log file, which are recorded just before it starts hanging
2016-12-25T16:56:47.639-05:00| mks| I125: MKS-HWinCompMux: Started GDI presentation backend 2016-12-25T16:56:47.639-05:00| mks| I125: MKS-SWB: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 1. 2016-12-25T16:56:47.717-05:00| vcpu-0| I125: CPT: vmstart 2016-12-25T16:56:47.717-05:00| vcpu-3| I125: CPT: vmstart 2016-12-25T16:56:47.733-05:00| vcpu-2| I125: CPT: vmstart 2016-12-25T16:56:47.733-05:00| vcpu-1| I125: CPT: vmstart 2016-12-25T16:56:47.873-05:00| vcpu-3| I125: DDB: "longContentID" = "55a2ba22ca54e2242cab8f95fd5bb2e6" (was "5c5aff5be980c52bdd0aa5ad05fced86") 2016-12-25T16:56:47.951-05:00| vcpu-3| I125: PatchSetProcessOne: Remote EagerValidate Enabled 2016-12-25T16:56:48.189-05:00| vcpu-1| I125: PatchSetProcessOne: Remote EagerValidate Enabled 2016-12-25T16:56:48.220-05:00| vcpu-2| I125: PatchSetProcessOne: Remote EagerValidate Enabled 2016-12-25T16:56:48.345-05:00| vmx| I125: VNET: MACVNetLinkStateTimerHandler: 'ethernet0' state from 6 to 1. 2016-12-25T16:56:48.763-05:00| vcpu-0| I125: PatchSetProcessOne: Remote EagerValidate Enabled 2016-12-25T16:57:12.249-05:00| vmx| I125: VNET: MACVNetLinkStateTimerHandler: 'ethernet0' state from 1 to 5.
The Sandbox VM needs at least 8GB of ram, but I have found it works much better if you can assign 10-12GB to it. Do you have enough memory to try that to see if it resolves the problem?
Have you tried shutting it down and restarting the VM?
This is not a memory related issue. It exists regardless of the memory allocated. I have allocated 12 gb of memory to the VM, both on Virtual Box and VMWare and it persists. This start process is stuck in a loop. Looking for where it is initiated in the start up script.
Yes, if you upgrade your system memory to 16GB, then it should resolve the problem. If you have 8GB of memory, you can't give all 8GB to the VM because your host computer needs a minimum of 2-3GB just to run it's base OS.