Error when doing vmotion to another host : the virtual machine cannot be restored because the snapshot was taken with VHV enabled. To restore, set vhv.enable to true.

[mauser_]

Hello,

i am trying to migrate some vm`s to another host.

When doing this, i receive the following error (see attachment also) :

On both hosts the HVH is already enabled.

What to do to fix this?

Thx

[admin]

What version of ESXI is running on the target?  What kind of physical CPU is present on the target?

[dave012345]

I am having the same issue. I noticed that it began after upgrading the virtual hardware of these VM's. I get the same exact error only on VMX-10 virtual machines.

I found that this seems to help with some of them but not all: How to set Hardware virtualization --> expose

Has anyone else seen this array of symptoms and come up with a solution?

[dave012345]

I'm seeing the same thing on vSphere 5.5u3 and ESXi 5.5u3 with Intel Xeon E7 cpus

[admin]

Please post a vmware.log file.

[dave012345]

File attached. it has been deidentified. You can find the host referenced by searching "ESXI_HOST" and find the VM name by searching "USER_VM".

Thanks for taking a look.

[admin]

I suspect that the referenced snapshot was taken on a misconfigured ESXi host, with the setting "vhv.enable = TRUE" manually added to /etc/vmware/config.

To enable virtualized hardware-assisted virtualization for the affected VMs, use the web client and navigate to the processor settings screen. Check the box next to "Expose hardware-assisted virtualization to the guest operating system."  This setting is not available under the traditional C# client.

[dave012345]

We did manually add that setting in the past, and it's been nothing but trouble since. Also, the weirdest thing is none of these affected VM's have snapshots. Anyways, I will remove vhv.enable = TRUE from the config file of a host and see if that resolves the issue. Thanks.

[dave012345]

I have removed the VHV setting from the ESXi config file and I've set the hardware virtualization to enabled. Still no luck on these VM's. Is it possible that they or the hosts need to be rebooted before this will take effect?