the cpu has been disabled by the guest operating system vmware что делать
Fix: The CPU has been disabled by the guest operating system
Power off or reset the virtual machine
Several users have been complaining about getting the “CPU has been disabled by the guest operating system” error when trying to play a virtual machine inside the VMware Workstation application. Most affected users report that the issue suddenly started occurring after the image was functioning fine for. This doesn’t seem like an OS-specific error since users have reported this occurring with Linux, MacOS and Windows images.
The CPU has been disabled by the guest operating system. Power off or reset the virtual machine.
What is causing The CPU has been disabled by the guest operating system error
We investigated this particular issue by looking at various user reports. As it turns out, there are several scenarios that will lead to the apparition of this particular issue. Here’s a list of common scenarios that are known to trigger this error message:
If you’re struggling to resolve this particular issue, this article will provide you with a couple of troubleshooting methods that will help your cause. Below you have a few methods (with step-by-step instruction) that other users in a similar situation have successfully used to get the issue resolved.
For the best results, follow the methods below in order until you encounter a fix that is successful in resolving the issue for you. Let’s begin!
Method 1: Enable VT-X (Intel Virtualization) from BIOS Settings
Since this is one of the most common scenarios, let’s start by ensuring that VT-X is enabled in your BIOS settings. Your machine might have shipped with VT-X disabled by default, a 3rd party application might have done it for you or you might have manually disabled the technology in the past.
In any case, every motherboard manufacturer will include an option to disable or enable the VT-X technology in their BIOS settings. It’s just a matter of finding out the exact path of doing so.
Keep in mind that the exact steps for accessing the BIOS setting will be different according to your motherboard manufacturer. But there is some common ground – you’ll need to press the BIOS (SETUP) key during the initial startup procedure to gain entry into your BIOS Settings.
Typically, the BIOS key is either one of the F keys (F2, F4, F8, F10, F12) or the Dell key (for Dell computers). If you don’t know your BIOS key, you can spot it during the very first screen (referred to as SETUP). Additionally, you can search for your specific BIOS key online according to your motherboard model.
Press the BIOS key during the startup procedure
Once you gain entry into your BIOS settings, you can typically find the Virtualization Technology entry listed as VTx/VTd. Enable it, save the changes in your BIOS settings and reboot your machine.
Enabling Virtualization Technology (VTx/VTd) from the BIOS Settings
At the next startup, open the same image in VMware Workstation and see if the issue has been resolved. If you’re still encountering the same issue, move down to the next method below.
Method 2: Performing a CPU ID masking procedure
The “CPU has been disabled by the guest operating system” error can also occur if a security check disables the processor – if an unwelcomed processor is found. This typically happens if you try to move the image from a machine with an Ivy Bridge architecture to another with Sandy Bridge architecture (or vice versa).
Whenever this scenario occurs, your system will refuse to boot up the image unless the CPU ID is masked. This modification can be done pretty easily if you have VMware ESXi or a different premium product, but with VMware workstation, there is no GUI option to do this.
However, there is a way to mask the CPU ID by modifying the VMX file of the image. To do this, you’ll need a powerful text editor like Notepad++. Here’s a step by step guide on how to edit the VMX file of the image in order to resolve the “CPU has been disabled by the guest operating system” error:
Note: If you’re on Windows 10 and you can’t see the extensions in File Explorer, access the View tab using the ribbon at the top and make sure that the box associated with File name extensions is checked.
If this method was not successful, move down to the final method below.
Method 3: Creating a new virtual machine
If the two methods above didn’t enable you to resolve the “CPU has been disabled by the guest operating system” error, you either have a disk configuration problem or you recently performed an operation that corrupted your virtual machine.
But regardless of what caused the error, you can resolve it by creating a new guest machine from scratch. But keep in mind that doing so means that you’ll lose any data stored within the guest machine.
If you decide to do this, here’s a quick guide on creating a new virtual machine:
You will be able to run the new guest machine without seeing the “CPU has been disabled by the guest operating system” error during the initial Boot procedure.
Fixing “The CPU has been disabled by the guest operating system” when running OS X Lion on VMWare
My OS X Lion VMware image, which has always been working fine on my computer, a 2.53GHz Intel Core i5 HP notebook, stopped working when I migrated to a Dell Core i7 notebook. The machine would immediately stop at boot-up with the following VMware error message:
“The CPU has been disabled by the guest operating system. Power off or reset the virtual machine.”
Troubleshooting the issue
My first thought was that the VMware patcher to enable OS X guest on Windows was somehow not executed successfully. I tried to reinstall VMware, rerun the patcher, and install different versions of VMware many times but to no avail. I finally tried to enable verbose boot using:
and the screen showed a little bit of more information, although not much useful:
There is no problem indicated by the above messages – it is simply part of the OS X boot process. The CPU was apparently halted as soon as the boot device was detected (indicated by the info ‘root device uuid is…’) without even attempting to boot further. Following a strange idea, I reverted the virtual machine to one of the previous snapshot, saved when OS X Lion was already running, and received the following warning about processor features difference:
The features supported by the processor(s) in this machine are different from the features supported by the processor(s) in the machine on which the snapshot was saved.
I chose to proceed, and guess what, my OS X booted up and functioned properly without further problems. For more than 2 weeks, due to time constraints, I simply worked with the virtual machine in that saved state, suspended it when done and reverting back to the snapshot (after saving all data) when I needed to reboot!
Solution: CPU ID masking
Recently I had some free time and determined to solve the problem completely. Following a Google search of the root device uuid message, I found this blog which describes a similar problem and the solution for VMware ESXi by editing the CPU ID:
I am using VMware workstation, which does not have such an option to mask the CPU ID. However, using instructions from this forum, I was able to change the CPU ID by modifying the VMX file and add the following line:
With this change, my OS X Lion booted up properly and there is no need to work with it in a saved state anymore.
But what makes OS X Lion dislike my new laptop’s processor and refuse to boot up? The fact that the unmodified virtual machine can still work on the new processor with the previously saved state implies that the processor difference is probably not critical – it was most likely a check that disables the processor if an unwelcome processor is found! With further research I realized that my new laptop processor architecture is Ivy Bridge, as compared with Sandy Bridge in my old laptop. Max OS X Lion doesn’t like Ivy Bridge architecture, and thus refuses to boot up unless the CPU ID is masked to make OS X think it’s running on a Sandy Bridge processor. What a hassle created by Apple, the virtual machine would have booted up properly and saved me precious time troubleshooting without this check.
Luckily, according to my research, this is probably not needed with Mountain Lion, since it supports Ivy bridge natively. I have not had the time to verify this, however.
On a side note, when trying to connect your USB device to the Mac virtual machine via VMware menu, you may receive the following error message:
“The connection for the USB device was unsuccessful. The device is currently in use”
When this happens, first check if the error message is telling you the truth. Stop all Windows applications that are currently using the device, reboot your laptop and the virtual machine and try again. If that doesn’t help and you’re using a new laptop with USB 3.0 ports, most likely you’ve hit a known problem – VMware does not support most USB 3.0 chips on Windows host. The Linux version does, however. This means, on Windows, you must revert back to a USB 2.0 or USB 1.1 port to avoid this error. So much for backwards compatibility!
In my case, I was lucky. My laptop has 4 USB ports, 3xUSB 3.0 ports and 1xUSB 2.0 port. I plugged the device to the USB 2.0 port and VMware was able to connect the device successfully.
ToughDev
A tough developer who likes to work on just about anything, from software development to electronics, and share his knowledge with the rest of the world.
92 thoughts on “ Fixing “The CPU has been disabled by the guest operating system” when running OS X Lion on VMWare ”
Thank you so much. I was stuck for like hours. I tried to understand what you did here, but was a little confused, but with much trial and error, finally got it to work! THANKS.
Did not work for my using AMD quad core and no hardware virtuzation in the bios. I want to code IOS apps
Hi, you would first need to patch the kernel to make it work with AMD processor. The image is meant for Intel processor only. Try to google for the AMD kernel, you’ll find it.
Furthermore, if your processor does not support hardware virtualization, you will need a hardware virtualization unlocker for VMWare to make it try to run the OS X virtual machine without virtualization. I would however say that the speed of the virtual Mac without hardware virtualization will be too slow for simple tasks such as chatting or browsing, let alone to develop iOS app using xCode.
As an alternative, try to consider Hackintosh OS x86 and install Mac OS on your computer directly, if your hardware is compatible. If it works it will be stable and much more productive
It is, there is a space between the 10- and the 8. The real url should be:
http://www.cachem.fr/vmware-os-x-10-8-mountain-lion-windows-7/
Thanks a lot that helped me solve the problem..
You need a decryption key for that
.encoding = «windows-1252»
paevm = «TRUE»
config.version = «8»
virtualHW.version = «7»
numvcpus = «4»
cpuid.coresPerSocket = «2»
scsi0.present = «TRUE»
scsi0.virtualDev = «lsilogic»
memsize = «2048»
scsi0:0.present = «TRUE»
scsi0:0.fileName = «Mac OS X Lion.vmdk»
ide1:0.present = «TRUE»
ide1:0.autodetect = «TRUE»
ide1:0.deviceType = «cdrom-raw»
floppy0.startConnected = «FALSE»
floppy0.fileName = «»
floppy0.autodetect = «TRUE»
ethernet0.present = «TRUE»
ethernet0.connectionType = «nat»
ethernet0.virtualDev = «e1000»
ethernet0.wakeOnPcktRcv = «FALSE»
ethernet0.addressType = «generated»
usb.present = «TRUE»
ehci.present = «TRUE»
pciBridge0.present = «TRUE»
pciBridge4.present = «TRUE»
pciBridge4.virtualDev = «pcieRootPort»
pciBridge4.functions = «8»
pciBridge5.present = «TRUE»
pciBridge5.virtualDev = «pcieRootPort»
pciBridge5.functions = «8»
pciBridge6.present = «TRUE»
pciBridge6.virtualDev = «pcieRootPort»
pciBridge6.functions = «8»
pciBridge7.present = «TRUE»
pciBridge7.virtualDev = «pcieRootPort»
pciBridge7.functions = «8»
ich7m.present = «TRUE»
firmware = «efi»
roamingVM.exitBehavior = «go»
displayName = «Mac OS X Lion»
guestOS = «windows7»
keyboard.vusb.enable = «TRUE»
mouse.vusb.enable = «TRUE»
monitor.virtual_exec = «hardware»
monitor.virtual_mmu = «software»
nvram = «Mac OS X Lion.nvram»
virtualHW.productCompatibility = «hosted»
extendedConfigFile = «Mac OS X Lion.vmxf»
ide1:0.startConnected = «FALSE»
sound.present = «TRUE»
sound.fileName = «-1»
sound.autodetect = «TRUE»
isolation.tools.hgfs.disable = «TRUE»
sharedFolder0.present = «TRUE»
sharedFolder0.enabled = «TRUE»
sharedFolder0.readAccess = «TRUE»
sharedFolder0.writeAccess = «TRUE»
sharedFolder0.hostPath = «D:\»
sharedFolder0.guestName = «D»
sharedFolder0.expiration = «never»
sharedFolder.maxNum = «1»
ethernet0.generatedAddress = «00:0c:29:a3:d9:43»
tools.syncTime = «FALSE»
uuid.location = «56 4d 9d d2 90 27 25 ca-8b 4b 36 7c f1 a3 d9 43»
uuid.bios = «56 4d 9d d2 90 27 25 ca-8b 4b 36 7c f1 a3 d9 43»
cleanShutdown = «FALSE»
replay.supported = «FALSE»
replay.filename = «»
scsi0:0.redo = «»
pciBridge0.pciSlotNumber = «17»
pciBridge4.pciSlotNumber = «21»
pciBridge5.pciSlotNumber = «22»
pciBridge6.pciSlotNumber = «23»
pciBridge7.pciSlotNumber = «24»
scsi0.pciSlotNumber = «16»
usb.pciSlotNumber = «32»
ethernet0.pciSlotNumber = «33»
sound.pciSlotNumber = «34»
ehci.pciSlotNumber = «35»
vmotion.checkpointFBSize = «134217728»
usb:1.present = «TRUE»
ethernet0.generatedAddressOffset = «0»
usb:1.deviceType = «hub»
mks.enable3d = «TRUE»
mks.keyboardFilter = «allow»
policy.vm.managedVMTemplate = «FALSE»
policy.vm.managedVM = «FALSE»
applianceView.enabled = «FALSE»
applianceView.showAtPowerOn = «FALSE»
applianceView.coverPage.name = «»
tools.remindInstall = «FALSE»
checkpoint.vmState = «»
cpuid.1.eax = «0000:0000:0000:0001:0000:0110:1010:0101»
usb:1.speed = «2»
softPowerOff = «FALSE»
RemoteDisplay.vnc.enabled = «FALSE»
vmci0.present = «FALSE»
smc.present = «FALSE»
scsi0:1.present = «FALSE»
usb:0.present = «TRUE»
usb:0.deviceType = «mouse»
usb:0.port = «0»
usb:0.parent = «-1»
Are you using an AMD core? If this is the case, the patch in the article will not work. Try with an Intel core.
my processor is : Intel(R) Core(TM) i7 CPU Q720 @ 1.60GHz
i get a kernel panic as well
I replaced the nvram proper for ADM «OS X Mountain Lion.nvram»
This file I found it include in OS X Mountain Lion 10.8.3 VMware Image/OS X Mountain Lion/amd/OS X Mountain Lion.nvram
The folder amd is a hiding file.
Hi, it is be rather difficult to find the AMD kernel for the vmware image of OS X. Most images on the net support only Intel processors. Keep trying and you’ll find it. I did come across some AMD kernel links a few months ago but did not have the time to test it.
This comment has been removed by the author.
Hi, let me know your machine configuration. Will try to do some research on this.
thanks it is working
Can you send me the code please
eng_kaddoura@yahoo.com
seriously my message wasn’t accept. im not typing it again damn it. just go to setting, options, first option, change from mac os server 64bit to mac os server…. grrr
There is a known problem with Blogger which may sometimes discard your comment if you have to log in to your Google account first before posting. It may also happen if the account has been logged on for a while without any activity. Blogger would just then reload the page with an empty comment box after you submit the comment and whatever you have typed is lost. This is irritating for me too but so far the only workaround I know of is to type in Notepad first, then copy/paste it over
For the OS change in the VM settings, thanks for sharing your findings with me. I am sure it will help others who may still encounter the problem after editing the VMX file to enable the cpu masks following the article.
Thank you, it works really great!
Thank you so much!! very appreciated.
My PC IS Made for Hardware virtualization, But it doesn’t have an Intel core i5 or i7 processor.
I remember doing this on the same PC, and I fucked around not knowing what I was doing till I fixed it, But I can’t seem to remember what I did, I have tried everything and can’t fix it, Tell me if you find a few new ways to fix this problem.
after applying the AMD kernel
enable “Boot with EFI instead of BIOS”
in Virtual Machine Settings under Options
Thank you soo very much! it really works awsum thanks alot… God Bless You
cpu- amd athlon
asus motherboard
4gb ram
windows 7 ultimate 64 bit
tried with several versions of vmware (8,9 series) and same error every where
I have been searching for the solutions since weeks and no result.
PLEASE some body help me out guys.
Very informative post thanks for such help.
Yeah! great bro. You have done great job in this post. Thanks
when installing mac os x lion 10.7 error message coming
the cpu has been disabled by the gust operating system why how to fix this i have intel core i3 4 gb ram plsss help
Hi guys, pls can someone help me out. I have been try to fix this error your CPU has been disable by the guest. Am use macOS 10.12 Sierra VMware with VMware workstation, I followed up the tutorial but I keep receiving this massage. Pls I need help
Hey
“after applying the AMD kernel”
How do I apply a kernel?
“enable “Boot with EFI instead of BIOS”
how do i apply amd kernel.
and that line at the end of the file
featureCompat.enable = “FALSE”
I got error that, your cpu has been disabled by guest operating system,while installing linux in vmware,so what i have to do plz help..
I want to thanks Abdallah for the good answer (AMD cpu).
The CPU has been disabled by the guest operating system #14
Comments
Nolij commented Apr 12, 2020
Upon launch it shows the Apple logo, then shows this error message and never boots: «The CPU has been disabled by the guest operating system. Power off or reset the virtual machine.»
I’m on latest version of Workstation, latest Windows 10, and using a previously proven working Catalina (10.15) iso.
I added this to the vmx file as I remember having to do this with old unlocker and still didn’t work.
smc.version = «0»
Other VMs still work fine.
The text was updated successfully, but these errors were encountered:
au10tic commented May 8, 2020 •
I also must say i have an AMD Ryzen 5 2200G CPU
smc.version = «0»
cpuid.0.eax = «0000:0000:0000:0000:0000:0000:0000:1011»
cpuid.0.ebx = «0111:0101:0110:1110:0110:0101:0100:0111»
cpuid.0.ecx = «0110:1100:0110:0101:0111:0100:0110:1110»
cpuid.0.edx = «0100:1001:0110:0101:0110:1110:0110:1001»
cpuid.1.eax = «0000:0000:0000:0001:0000:0110:0111:0001»
cpuid.1.ebx = «0000:0010:0000:0001:0000:1000:0000:0000»
cpuid.1.ecx = «1000:0010:1001:1000:0010:0010:0000:0011»
cpuid.1.edx = «0000:1111:1010:1011:1111:1011:1111:1111»
featureCompat.enable = «FALSE»
chppppp commented Jun 8, 2020 •
au10tic commented Jun 8, 2020
what VMware workstation are you trying? and are you installing macOS or spinning up an existing one?
chppppp commented Jun 8, 2020
au10tic commented Jun 8, 2020
@chppppp yep! AMD doesn’t get all the love 😏
Nolij commented Jun 9, 2020
Ryzen 9 3900x here. I’ll check that video out. Thanks!
chppppp commented Jun 9, 2020
@xdMatthewbx if you find a download link for Workstation 15.0.3, post it here and save us some google time 🙂
Nolij commented Jun 9, 2020
@xdMatthewbx if you find a download link for Workstation 15.0.3, post it here and save us some google time 🙂
If this doesn’t work I’ll just use another solution as I can’t find a download on google that doesn’t get 500 detections on virustotal.
ghost commented Sep 1, 2020
Use this Guide to install Catalina on VMWare
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Processors
To install MacOS Mojave 10.14 on VMware Workstation on Windows 10; I have gone through following links:
The CPU has been disabled by the guest operating system. Power off or reset the virtual machine.
Also please find the attached screenshot.
Desktop Configuration is as Processor: AMD FX 8320, Motherboard: ASUS M5A97 and RAM: 16GB (HyperX Fury).
I read some articles. The error occurs in case of AMD Processor. Please let me know what I need to do for resolving this issue.
Found this MAC VMWare Forum that you can ask: Community: Workstation Pro |VMware Communities
Thank you replying for my post.
Already I posted this issue on other forums/ communities. Now I posted this issue on both communities also that you suggested.
I didn’t find resolutions yet from any forums. According to some forums and Google search; the issue I posted is generally because of AMD Processor.
That’s why I posted here also.
You mentioned that the CPU works fine in Windows other VMWare environment except in APPLE OS. Which seems to indicate, at least to me, it is a APPLE OS issue with VMWare.
I would contact APPLE Support and see if they can give you any suggestions or since you are using Windows to install APPLE OS in a VMWare environment, maybe post your question at Microsoft Forums.
No harm in opening a AMD EMAIL SUPPORT Ticket and see what they suggest from here: Online Service Request | AMD
To be blunt, I really can’t give you any good advice since I am unfamiliar with VMWare and APPLE OS. That only thing I am able to do is possibly help find sources that might be helpful.
EDIT: I notice you got an answer from the first link. It says it is normal for the error to occur with APPLE OS on a Windows environment:
This is the expected behavior with running a MacOS on non-Apple branded hardware.
Please see Apple’s EULA for how to legally run a virtual MacOS instance.
The cpu has been disabled by the guest operating system vmware что делать
I was using Nougat 7 VM based on FreeBSD. everything was fine when my PC went down due to unexpected power interruption.
After turning it on again everything was fine except for this VM. Now it shows the error mentioned as title, screenshot and log is also attached.
I’ve seen that before @vijayrana968. It didn’t worked.
It looks like there are some CPU maskings in the vmx file.
The cpuid.0 masking looks unnecessary as leaf 0 is just the «GenuineIntel» string and furthermore the value mask applied to ecx didn’t change its value (it’s still ntel)
While the cpuid.1.eax entry masks to a Pentium III Katmai desktop processor (family 6 model 7 stepping 6)
From the log, the guestOS seems to be expecting x2APIC and TSC-Deadline capabilities in the CPU while the i7-950 does not seem to have those capabilities.
Try to mask these off from the guestOS by adding this to the vmx file
Coincidentally, there are few lines in the log before the CPU error and one line after that shows some APIC thermal monitor vector register operations; although I can’t say that these are the direct cause of the problem. APIC is supported by i7-950 processor but not x2APIC.
2017-08-07T23:20:16.498+05:00| vcpu-0| I125: APIC THERMLVT write: 0x10000
2017-08-07T23:20:16.498+05:00| vcpu-2| I125: APIC THERMLVT write: 0x10000
2017-08-07T23:20:16.498+05:00| vcpu-3| I125: APIC THERMLVT write: 0x10000
2017-08-07T23:20:16.498+05:00| vcpu-1| I125: APIC THERMLVT write: 0x10000
I don’t know if this new masking will help with your current powering up problem but try it out anyway.
Also since the i7-950 does not support x2APIC, try reducing the number of vCPUs to just 1 (currently the setting is 4) as x2APIC is really designed for multiprocessors. I would think you aren’t gonna lose much processing power in the Nougat VM as you are already trying to mask it to a 32-bit only Pentium III.
CPU masking was done after the problem in hope it could resolve it but didn’t worked. Now as you mentioned they were unnecessary I removed them and tried again but again no luck, tried again with 1 processor still didn’t worked and you quoted APIC is supported by i7-950 processor but not x2APIC. things were going just fine before that power glitch. is there any way I could get data from that VM?
I didn’t hold up much hope that the cpuid.1.ecx mask would work as it was working before unless it was some sort of recovery that Nougat OS was going through to recover from sudden power loss that required the use of certain CPU features.
Anyway, maybe it is just plain corruption of file(s) within the VM OS.
I don’t know much about data recovery, FreeBSD and Nougat OS and what filesystem it uses. And I dislike the Nougat candy, not that I eat candies these days. I see it as a punishment to be offered Nougat candy; or as sick challenge to not break your teeth while eating one :smileylaugh:
I would suggest backup the VMDKs of the Nougat VM. The way I see it the more times you boot up and modify the virtual disk, the higher the risk the recovery process gets more difficult if not impossible.
I can only suggest create another VM that is capable of reading the Nougat VM filesystem and add a copy of the VMDK of the broken Nougat VM as another drive that you can recover the data/files from.
EDIT: if the Nougat VM uses a filesystem that the Windows host recognises such as FAT32, you could just map a copy of the VMDK as a drive using the «Map virtual disks. » from the File menu.