VM won't start on Windows 10 after moving it from Windows 7

[artifexcrast1nu]

I'm trying to move a Ubuntu 16.04 virtual machine to my Windows 10 Pro desktop from my Windows 7 Pro laptop. I've attached the log file I get.

[bluefirestorm]

Based on the log, I see the host machine is an i7-7500U and that the crash is caused by some vCPU error.

But I also see this in the log

2017-05-03T14:56:21.559-07:00| vmx| I125: The following VT-x features are required for VT-x support in VMware Player; however, these features are not available on this host:

2017-05-03T14:56:21.559-07:00| vmx| I125: hostCpuFeatures = 0x217d

2017-05-03T14:56:21.559-07:00| vmx| I125: hostNumGenPerfCounters = 8

2017-05-03T14:56:21.559-07:00| vmx| I125: hostNumFixedPerfCounters = 3

2017-05-03T14:56:21.559-07:00| vmx| I125: hostPerfCtrArch = 4

2017-05-03T14:56:21.559-07:00| vmx| I125: MONITOR MODE: allowed modes          : BT

2017-05-03T14:56:21.559-07:00| vmx| I125: MONITOR MODE: user requested modes   : BT HV HWMMU

2017-05-03T14:56:21.559-07:00| vmx| I125: MONITOR MODE: guestOS preferred modes: HWMMU HV BT

2017-05-03T14:56:21.559-07:00| vmx| I125: MONITOR MODE: filtered list          : BT

2017-05-03T14:56:21.559-07:00| vmx| I125: MsgHint: msg.monitor.BTnoLM2

2017-05-03T14:56:21.559-07:00| vmx| I125+ Binary translation is incompatible with long mode on this platform. Long mode will be disabled in this virtual environment and applications requiring long mode will not function properly as a result. See http://vmware.com/info?id=152 for more details.

Are you able to set the Preferred mode to "Automatic" and uncheck the "Virtualize Intel VT-x/EPT" option? The virtualize Intel VT-x option needs to be checked only if you want to run a VM within the VM.

[artifexcrast1nu]

It was set to automatic. It had been set to 1 core and changing it to 2 cores didn't change the outcome. The Virtualize Intel box was not checked.

[bluefirestorm]

I don't have any Kaby Lake machines; so I don't have an idea why the unsupported CPU features are showing up in the log you provided.

Are you able to run other existing or new VMs on this Windows 10 host?

If this is the only VM you have, can you try to create and run a new VM just to see whether you run into the same/similar problem; which can possibly suggest some issue with Kaby Lake.

[artifexcrast1nu]

This is the log I got when I tried making a new VM using the same Ubuntu ISO as the first. Also had an error with that. I don't know what to make of the differences between the logs.

[bluefirestorm]

I had looked at the log a few times as I wasn't sure if you had accidentally given me an log of the previous machine. But I did see you created a ubuntu2.vmx.

I still see the same error.

However, notice the log date; looks like stuck at 03 May 2017. Is there something wrong with the host machine clock settings?

EDIT: Perhaps try rebooting the host machine if you had been using sleep/hibernate or simply closing the lid of the laptop. Clock problems tend to cause other problems as well. So fixing the clock problem might fix this problem, too.

2017-05-03T14:58:10.139-07:00| vmx| I125: The following VT-x features are required for VT-x support in VMware Player; however, these features are not available on this host:

2017-05-03T14:58:10.139-07:00| vmx| I125: hostCpuFeatures = 0x217d

2017-05-03T14:58:10.139-07:00| vmx| I125: hostNumGenPerfCounters = 8

2017-05-03T14:58:10.139-07:00| vmx| I125: hostNumFixedPerfCounters = 3

2017-05-03T14:58:10.139-07:00| vmx| I125: hostPerfCtrArch = 4

2017-05-03T14:58:10.139-07:00| vmx| I125: MONITOR MODE: allowed modes          : BT

2017-05-03T14:58:10.139-07:00| vmx| I125: MONITOR MODE: user requested modes   : BT HV HWMMU

2017-05-03T14:58:10.139-07:00| vmx| I125: MONITOR MODE: guestOS preferred modes: HWMMU HV BT

2017-05-03T14:58:10.139-07:00| vmx| I125: MONITOR MODE: filtered list          : BT

2017-05-03T14:58:10.139-07:00| vmx| I125: MsgHint: msg.monitor.BTnoLM2

2017-05-03T14:58:10.139-07:00| vmx| I125+ Binary translation is incompatible with long mode on this platform. Long mode will be disabled in this virtual environment and applications requiring long mode will not function properly as a result. See http://vmware.com/info?id=152 for more details.

[wila]

Hi,

Is VT-x enabled in the laptop? Can you check in the BIOS/EFI ?

If it was enabled recently, then please be aware that you have to power cycle the host in order to make the change stick.

For more details about VT-x troubleshooting, please see the following document:

Trouble-shooting Intel VT-x Issues

--

Wil

[artifexcrast1nu]

I'll check, but why would that effect the creation of the new VM on the desktop?

[wila]

Hi,

Your host has to have VT-x support and have that support exposed to the guest in order to be able to run 64 bit guests.

--

Wil