Asked By
Vendy
0 points
N/A
Posted on - 06/18/2012
Can someone help me out with my VMware? I was working on a very important project of mine and was attempting the proxy to be virtualized.
I managed to convert the file to vmx properly, but after importing them to my workstation an error report appeared. It says that “ A virtual CPU has entered the shutdown state. ” (the full detail can be seen in the screen shot below.)
It forces me to shutdown my machine.
"ProxySG-VA-5-VMare Workstation
A virtual CPU has entered the shutdown state. This would have caused a physical
machine to restart, This can be caused by an incorrect configuration of the virtual
machine, bug in the operating system or a problem in the VMware Workstation
software. Press Ok to restart the virtual machine or Cancel to power off the virtual
machine."
I’ve been searching for a solution to this problem,
but I can’t find any. Please, I need your help here.
Thank you!
Answered By
kingteja
0 points
N/A
#113455
Error Encountered A virtual CPU Has Entered The Shutdown State.
MAY be OPERATING SYSTEM u have installed missed one of the important DLL file if u wont have any problem in RE-INSTALLING your OS try that i will sure work…
Error Encountered A virtual CPU Has Entered The Shutdown State.
If you are not the one who initiated the shutting down of the machine then you should check if your virtual machine is properly configured by going to its settings and verifying that the virtual machine is running on the proper settings. If all settings are fine and the problem still happens, you should check your computer for problems.
Close your virtual machine then check your computer for any possible errors. Use a disk utility application to check the system. For a much thorough diagnostic test on your computer, use disk utility applications like PC Tools Performance Toolkit, Norton Utilities, or Norton SystemWorks. Restart your computer then see if the virtual machine will run without the previous problem appearing again. If the same thing happened again, you may try reinstalling the virtual machine to try a possible fix on the problem.
