VMware Communities
khammer
Contributor
Contributor
‎10-13-2016 09:16 PM

CPU disable on booting Ubuntu 16.10

After installation of Ubuntu 16.10 x64, I get the "CPU has been disabled by the guest OS" during the boot sequence.  Happened with the beta, too.  Same guest OS works just fine with Hyper-V.  16.04 installs and boots correctly.  Using Workstation 12.5.  There's some kind of kernel panic happening, but I can't capture it.  syslog and kern.log are empty in the /var/log/ path when I drop to a terminal from recovery mode.

Anyone else having this problem?

2016-10-13T23:04:05.116-05:00| svga| I125: SWBScreen: Screen 0 Destroyed: xywh(0, 0, 720, 400) flags=0x3

2016-10-13T23:04:05.116-05:00| svga| I125: SWBScreen: Screen 1 Defined: xywh(0, 0, 640, 480) flags=0x2

2016-10-13T23:04:05.129-05:00| vcpu-1| I125: DISKUTIL: scsi0:0 : capacity=41943040 logical sector size=512

2016-10-13T23:04:05.130-05:00| vcpu-0| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

2016-10-13T23:04:05.130-05:00| vcpu-1| I125: DISKUTIL: scsi0:0 : capacity=41943040 logical sector size=512

2016-10-13T23:04:05.130-05:00| vcpu-1| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

2016-10-13T23:04:05.132-05:00| vcpu-0| I125: DISKUTIL: scsi0:0 : capacity=41943040 logical sector size=512

2016-10-13T23:04:05.132-05:00| vcpu-0| I125: SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8

2016-10-13T23:04:05.402-05:00| svga| I125: SWBScreen: Screen 1 Destroyed: xywh(0, 0, 640, 480) flags=0x2

2016-10-13T23:04:05.404-05:00| svga| I125: SVGA-ScreenMgr: Screen type changed to ScreenTarget

2016-10-13T23:04:05.404-05:00| svga| I125: SWBScreen: Screen 1 Defined: xywh(0, 0, 800, 600) flags=0x2

2016-10-13T23:04:05.405-05:00| svga| I125: SWBScreen: Screen 1 Destroyed: xywh(0, 0, 800, 600) flags=0x2

2016-10-13T23:04:05.405-05:00| svga| I125: SWBScreen: Screen 1 Defined: xywh(0, 0, 800, 600) flags=0x2

2016-10-13T23:04:09.308-05:00| vcpu-0| I125: SCSI scsi0:0: Unsupported command *UNKNOWN (0x85)* issued. --ok

2016-10-13T23:04:09.308-05:00| vcpu-0| I125: SCSI scsi0:0: Unsupported command *UNKNOWN (0x85)* issued. --ok

2016-10-13T23:04:09.349-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x606] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.502-05:00| svga| I125: SWBScreen: Screen 1 Destroyed: xywh(0, 0, 800, 600) flags=0x2

2016-10-13T23:04:09.517-05:00| svga| I125: SWBScreen: Screen 1 Defined: xywh(0, 0, 800, 600) flags=0x2

2016-10-13T23:04:09.518-05:00| svga| I125: SWBScreen: Screen 1 Destroyed: xywh(0, 0, 800, 600) flags=0x2

2016-10-13T23:04:09.518-05:00| svga| I125: SWBScreen: Screen 1 Defined: xywh(0, 0, 800, 600) flags=0x2

2016-10-13T23:04:09.520-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x1b1] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.520-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x1a2] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.520-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x17] (read as zero): rip=0xffffffffa9464712 count=4

2016-10-13T23:04:09.520-05:00| vcpu-0| I125: GetMSR: unknown MSR[0xee] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.520-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x1a2] (read as zero): rip=0xffffffffa9464712 count=2

2016-10-13T23:04:09.520-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x19c] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.520-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x1a2] (read as zero): rip=0xffffffffa9464712 count=3

2016-10-13T23:04:09.520-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x17] (read as zero): rip=0xffffffffa9464712 count=5

2016-10-13T23:04:09.520-05:00| vcpu-0| I125: GetMSR: unknown MSR[0xee] (read as zero): rip=0xffffffffa9464712 count=2

2016-10-13T23:04:09.520-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x1a2] (read as zero): rip=0xffffffffa9464712 count=4

2016-10-13T23:04:09.520-05:00| vcpu-1| I125: GetMSR: unknown MSR[0x19c] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.520-05:00| vcpu-1| I125: GetMSR: unknown MSR[0x1a2] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.520-05:00| vcpu-1| I125: GetMSR: unknown MSR[0x17] (read as zero): rip=0xffffffffa9464712 count=3

2016-10-13T23:04:09.520-05:00| vcpu-1| I125: GetMSR: unknown MSR[0xee] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.520-05:00| vcpu-1| I125: GetMSR: unknown MSR[0x1a2] (read as zero): rip=0xffffffffa9464712 count=2

2016-10-13T23:04:09.583-05:00| vcpu-1| I125: GetMSR: unknown MSR[0x60d] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.587-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x1a2] (read as zero): rip=0xffffffffa9464712 count=5

2016-10-13T23:04:09.671-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x611] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.671-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x639] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.671-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x641] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.671-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x619] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.946-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x1b1] (read as zero): rip=0xffffffffa9464752 count=2

2016-10-13T23:04:09.946-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x60d] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.946-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x3f8] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.946-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x3f9] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.946-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x3fa] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.946-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x630] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.946-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x631] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:09.946-05:00| vcpu-0| I125: GetMSR: unknown MSR[0x632] (read as zero): rip=0xffffffffa9464712 count=1

2016-10-13T23:04:10.332-05:00| vcpu-0| I125: APIC THERMLVT write: 0x10000

2016-10-13T23:04:10.332-05:00| vcpu-1| I125: APIC THERMLVT write: 0x10000

2016-10-13T23:04:10.332-05:00| vcpu-0| I125: Vix: [2760 vmxCommands.c:7301]: VMAutomation_HandleCLIHLTEvent. Do nothing.

2016-10-13T23:04:10.332-05:00| vcpu-0| I125: MsgHint: msg.monitorevent.halt

2016-10-13T23:04:10.332-05:00| vcpu-0| I125+ The CPU has been disabled by the guest operating system. Power off or reset the virtual machine.

2016-10-13T23:04:10.332-05:00| vcpu-0| I125+ ---------------------------------------

Reply
7 Replies
dariusd
VMware Employee
VMware Employee
‎10-13-2016 09:58 PM

Could you please post the entire vmware.log as an attachment in this thread?  (Just use the Attach function in the lower-right corner when composing a reply here... Please don't copy-and-paste the whole logfile into the reply!)

Thanks,

--

Darius

Reply
0 Kudos
khammer
Contributor
Contributor
‎10-13-2016 10:31 PM

Full log attached.

Also, seems I'm not the only one having this problem (see here for another post on youtube just a few minutes ago).  Their solution, which seems to work for me, is to add the following line to the .vmx file:

cpuid.1.eax = "0000:0000:0000:0001:0000:0110:1010:0101"

vmware.log.zip
Reply
0 Kudos
dariusd
VMware Employee
VMware Employee
‎10-16-2016 09:53 PM

Thanks; We're investigating now.

My experiments here suggest that the problem only manifests in VMs where more than one virtual CPU core is available.  If you reduce the VM to only one processor with only one core (without your cpuid fix in place), does that resolve the problem there for you too?  Even if that might not be a useful workaround in the long term, it would be good to try it out just to check that we're looking at the same problem...

Cheers,

--

Darius

Reply
0 Kudos
RogerLeigh
Enthusiast
Enthusiast
‎10-17-2016 02:53 AM

I'm also seeing this.  Windows 7 x64 host with an Intel Core i7-3770 CPU.  Reducing the core count from 4 to 1 has no effect--the CPU is still disabled in early boot.

See also: https://answers.launchpad.net/ubuntu/+question/402993 for another report.

Regards,

Roger

Reply
0 Kudos
Nohk
Contributor
Contributor
‎10-18-2016 09:31 AM

M..... the same post https://answers.launchpad.net/ubuntu/+question/402993‌ mentioned the CPU Core i7-4800MQ, i7-4900k and i5-4210U all have the same problem. The i5-4210U one is my post there. I use only 1 cpu and 1 core on the guest machine.

Reply
0 Kudos
dariusd
VMware Employee
VMware Employee
‎10-19-2016 11:32 PM

Hi everyone,

The underlying cause of this problem is this: Bug #1630774 “kernel invalid opcode in intel_powerclamp” : Bugs : linux package : Ubuntu

To work around the problem, add the kernel command-line option modprobe.blacklist=intel_powerclamp either directly at the grub menu during boot, or add it to the guest OS's default grub configuration as follows:

  1. As root, edit the file /etc/default/grub using your favorite editor.

       user@ubuntu:~$ sudo vi /etc/default/grub

  2. Modify the GRUB_CMDLINE_LINUX_DEFAULT option to read "quiet modprobe.blacklist=intel_powerclamp".  In the default installation, that option will already be set to "quiet" on line 11, so you'll just need to add a space and then the additional option.  Save the file and exit the editor.
  3. As root, run the update-grub utility.  (Ignore the warnings about the GRUB_TIMEOUT and GRUB_HIDDEN_TIMEOUT settings.)

       user@ubuntu:~$ sudo update-grub
       Generating grub configuration file ...
       Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
       Found linux image: /boot/vmlinuz-4.8.0-22-generic
       Found initrd image: /boot/initrd.img-4.8.0-22-generic
       done
       user@ubuntu:~$

  4. Reboot the guest OS.

We're working on requesting that OS vendors promptly incorporate the fix for the underlying defect.  Thanks for your patience!

Cheers,

--

Darius

Reply
VamshiSeshasaya
Contributor
Contributor
‎10-12-2020 08:48 AM

For those whoever is still facing the issue with even Ubuntu 20.04, Please see this article VMware Knowledge Base for resolution

Reply
0 Kudos