Member Avatar for MoZo1

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!

Edited by MoZo1 because: n/a
  • 2 Contributors
  • 5 Replies
  • 1K Views
  • 4 Days Discussion Span
  • Latest Post Latest Post by jingda

Dani AI

Generated

Short summary and focused next steps based on the thread: has already tried CPUID masking and BIOS tweaks and pointed to community threads. The VMware message "The CPU has been disabled by the guest operating system" is most often a symptom: the guest executed a CLI/HLT sequence (or crashed) and voluntarily stopped the virtual CPU, so the host log and the guest panic text are the real clues — the vmware host message itself rarely tells the root cause. (knowledge.broadcom.com)

Practical checklist to isolate the root cause (capture logs first):

  • Collect the VM's vmware.log (and host logs) and look for lines referencing VMAutomation_HandleCLIHLTEvent / msg.monitorevent.halt; attach those excerpts when asking for help. (knowledge.broadcom.com)
  • Boot the macOS guest in verbose mode (-v) and copy the full kernel panic backtrace. If you see AppleIntelCPUPowerManagement or "No HPETs available" messages, the problem is usually HPET/ACPI or power-management expectations inside macOS. (dortania.github.io)
  • Toggle the VM's HPET exposure (edit the .vmx or change virtual hardware): try adding or removing hpet0.present = "TRUE" (or upgrade/downgrade the virtual hardware level) because HPET presence interacts with some macOS kernels. (knowledge.broadcom.com)
  • Simplify the VM: set a single vCPU, remove extra virtual devices, and try switching the network adapter from VMXNET3 to E1000/E1000E (network driver bugs have produced identical symptoms for Linux/macOS guests). (unix.stackexchange.com)
  • If virtualization appears grey in BIOS, update BIOS/microcode and reboot/power-cycle the host after enabling VT-x/AMD‑V (VMware often requires a full power cycle after that BIOS change). (community.broadcom.com)

Post the vmware.log excerpt, the guest kernel panic (full backtrace), host CPU model, VMware product/version and VM hardware version for targeted troubleshooting; the vmware halt message is a signal, not the root cause.

Recommended Answers

All 5 Replies

Member Avatar for jingda

Try this

Member Avatar for MoZo1

Yes, this is the CPUid mask, I've already tried. On some versions this makes a difference, some error shows up with CPU state, and after that the same message. But the error is always the same.
Also this thread is about an issue with 10.6.3, but I've also tryed 10.6.7; 10.5.x; 10.4.x OSes, and no difference.

Member Avatar for MoZo1

Update:
CPU virtualization thingy is grey in the bios, but Enabled, so there should be no problem around this.

Member Avatar for MoZo1

Update:
On some versions when applying the CPU mask, I get kernel panic instead. They are still not working thogh.

Member Avatar for jingda

Try uninstalling the app totally and reinstall it again. If that does not work, i am sorry i could not help you with your problem.

Edited by jingda because: n/a
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.