Unable to connect to the mks: invalid / explicitly disabled state operation is invoked

[andreas190386]

Unable to connect to the mks: invalid / explicitly disabled state operation is invoked,

this always appears when i start a VM the first time (W2k3 or W2K8) from .iso deployed or created from template with customizing file.

than I can only power off the VM.

maybe someone who also had this problem can help me.

br

andreas

[brutwan]

Encountered the same problem today. Occurs when trying to change number of virtual CPUs to 8. The console cannot be displayed but I can connect to the server through RDP. Is there any setting that could resolve the problem besides changing back to 4 CPUs?

[bbricker]

This just happened to me too, I was changing from multi to uni-processor in the device manager within a Windows 2003 Standard server because it was P2V'd from a dual-proc system to a VM with only one vCPU. I just close the console window and reopened it and I could view the VM. Then I rebooted it and did not get the message the 2nd time around. Not sure this helps either of you, but maybe someone will see this thread and know what it is.

[HansdeJongh]

same here, i have a win2k8 r2 3gb extra memory (total of 4). No CD attached.

[Funtoosh]

In my situation, I have selected "Boot into BIOS" and "CD ISO mode" . I uncheced and rebooted, error message has gone.

I did not debug more since I was only testing this product. But if someone has some other idea plesae do share.

Thanks,

Funtoosh

[cnidus]

I have come accross the similar issues a couple of times during VMWare tools / HW upgrades using the basslines with vsphere 4 update manager.

The first time I could not power on the VM at all, as it then said it was in an inconsistant power state. This was eventually solved by migrating VMs off the host ESX server and rebooting the ESX server. Prior to this we also tried restarting the vpxa and management services, with no luck. A very large hammer solution...

Just this morning i came accross the exact same error and it was resolved by shutting down the VM and removing a previously defined CPUID mask on the VM. I suspect this was automatically defined when our cluster was AMD based, but has not caused an issue till now.

Thanks,

Doug

[ReflexTommy]

I just ran into this this morning. Looked at the suggestions about the CPUID or the number of CPU's, but everything was fine and nothing changed. It did make me think about the Paravirtualization option. It was turned on, so I turned it off and booted the VM successfully.

Moral of the story this error has something to do with CPU issues, so check all the options/configs/paravirtualization/additions. Thanks to everyone on this thread for ideas.

[kaziislam]

I had the same problem with a Windows 2008 64bit Enterprise edition VM. I added a CPU (originally had 1) and was able to bring the server up.

[pramodupadhyay5]

this morning i also faced the sma e problem and it got solved by changing the CPUID Mask.....

If you found this or any other answer useful please consider the use of the Helpful or Correct buttons to award points