VMware "CPU has been disabled by guest..."


So I get the error CPU has been disabled by guest os. Power off or restart. But if I power off, it shuts down. I wana run it. Then error again...



I tryed:  

- Disabled all unnecessary hardware.  

- Turned off USB Legacy support in BIOS.  

- Found no explicit CPU virtualization setting in BIOS...  

- Messed with every setting of the virtual machine.  

- cpuid.1.eax = "0000:0000:0000:0001:0000:0110:1010:0101" stuff. Then everything again.  

- Tryed this with 5 preinstalled VMware osx. (10.5; 10.6; 10.7)  

- Also tryed to install 3 osx to another hdd without virtualization. Those are also not working.  

- I'm pissed!



**Now what else?!**



Thanks for any help!
Try this



[http://www.insanelymac.com/forum/lofiversion/index.php/t232183.html](/posts/bad_link/1624484?url=http%3A%2F%2Fwww.insanelymac.com%2Fforum%2Flofiversion%2Findex.php%2Ft232183.html)
hi kenhaught, thanks for your replies. i finally fixed the problem. i had built the vms on a previous version of esxi, version 5.5, so they had an earlier vm version of the hardware. once i updated the hardware version, of the guest, to "esxi 6.5 and later (vm version 13)" the windows server 2016 option appeared. that is where i'd start as well. osi...
so:
1. physical link (maybe check the patch panel and the cabling that's involved in connecting to the computer, maybe swap cables and try a usb to ethernet adapter to rules the nic out.
2. data link - check the switches and switchports on the way. maybe try to use different portts
3. network - most likely not an issue if all the other computers are working fine...
etc.
but this is pretty much it: enable xmp. run stability testing.
if that is all good and you want to now overclock the cpu then it's time to make a new thread in the overclocking section. first try testing your RAM (goldmemory or memtest)
  

  
if the memory pass the tests try reparing your xp, if repair doesn't pass from any reason, pull your HD take it to your friend, back up the data, and reinstall OS thanks for the support! <3 you guys are really great, so many offers of help these last few days!

unfortunately we aren’t quite there yet. :frowning: this issue is a root problem with the trifecta of the processor, engine and windows. we have fixed the issue with the game freezing during the cabin… thank you for taking interest in my post.

i have solved the problem.it was mistake from my own part.

i have disabled some of the hardware detection services before the update.

i have disabled the "device install service" on the windows service

[[asas]](https://aws1.discourse-cdn.com/arduino/original/4x/5/0/9/509934b6660953c4e848dc95f40efd35d02bfe60.png "asas")

renabling it and rebooting it solved the … Hello,

 

 

We would like to inform you that decoding MCE errors is out of the scope of support for us. As a general recommendation based on the wording for the log, please check the memory modules installed and confirm if one of them has failed.
 
 
 
 
 
 
 
 
 

[View solution in original post](/t5/Server-Products/How-to-decode-MCE-errors/m-p/527769#M13599) thanks, to all of you for the replies, after much trial and error turns out the culprit was the PSU. Amazingly one of the modular plugs had a dead terminal and was not giving power thru the cord, I tried another one of them and boom, GPU read. Seems like GPU was receiving only half the power it needed to fully be operative. With one plug it did turn on and fan blew but it was not functional until the second plug gave the rest of the power. Rediculous lol Thanks all who replied, never even thought of trying another terminal until i started trying to do stupid random things. Now to send back this damn PSU lol




[View solution in original post](/t5/Intel-Desktop-Boards/DX79SR-Board-not-detecting-EVGA-GTX-680-Classified-GPU-on-first/m-p/256500#M12447) maybe the boot disk partition be cleared. you can disable emmc in bios then install a pure windows in ssd. enable emmc after the windows installed. Basically to answer your original question, these are a few things that can cause the YLOD:


Dead/Disconnected HDD


Cold-Joint between the CPU/RSX/EE(If your console has one)


Physical Damage to the Motherboard


Dead power supply


Not enough voltage from the power supply (Failing Power Supply)


Jammed/Disconnected Fan (Not Confirmed)


Overheating


Corrupted NAND Flash


Bad Update


Short Circuit