vCenter

 View Only

  • 1.  CPU has been disabled.

    Posted Nov 14, 2014 12:46 PM

    I got an error stating CPU has been disabled by guest OS and every time i have to reset the virtual machine as it goes in to hung state. Any suggestions please.



  • 2.  RE: CPU has been disabled.



  • 3.  RE: CPU has been disabled.

    Posted Nov 14, 2014 01:04 PM

    Hi,

    i have gone through thr article but can not found any logs in the VM because when the machine enters in hung state no logs are captured.

    Regards

    Nishant



  • 4.  RE: CPU has been disabled.

    Posted Nov 14, 2014 01:49 PM

    Hi,

    at least some info can be found in virtual machine log file (vmware.log) located at VM working directory.

    however can you please post more info about host and guest versions and builds ...

    There are also some KBs regarding similar issue on SLES etc. see:

    VMware KB: SLES 10 64bit virtual machine becomes unresponsive with the error: The CPU has been disabled by the guest…

    For VMware Workstation:

    VMware KB: Error when booting or shutting down virtual machines: CPU has been disabled  



  • 5.  RE: CPU has been disabled.

    Posted Nov 14, 2014 01:57 PM

    Can you post some screenshot when VM hangs ?



  • 6.  RE: CPU has been disabled.

    Posted Nov 17, 2014 11:34 AM

    Hi,

    We are running SLES 11 which is having higher kernel version that is 3.0.

    I have seen the logs they are same as in the article you have provided in your comments.

    We are running esxi version 5.1 and vcenter appliance 5.5.

    Kindly ask what more information is required.



  • 7.  RE: CPU has been disabled.

    Posted Nov 17, 2014 12:36 PM

    Could sound weird but verify that you have Intel VT enabled on that host in the BIOS.

    Next what setting is under CPU/MMU virtualization for that virtual machine and what OS type is chosen under General settings...?

    What hardware version that VM is?

    At least remove VM from directory and add it back if this doesn't help remove it again...create brand new VM and point wizard to existing disks...check if you are able to power it on then...