VMware Cloud Community
ericsl
Enthusiast
Enthusiast
Jump to solution

After conversion of Server 2012 system_thread_exception_not_handled winhv.sys

Hello All,

After converting a Server 2012 machine (which is running Hyper-V) and starting in VMware vSphere 5.5 I get a BSOD and system_thread_exception_not_handled winhv.sys

I know that I might need to disable Hyper-V, anything else it could be?

~eric

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
ericsl
Enthusiast
Enthusiast
Jump to solution

No, I was simply converting a machine that already had the Hyper-V role enabled. I disabled Hyper-V and converted it again and it started properly.

However, I did find this article about modifying the vmx file to allow for a machine with Hyper-V enabled to run as a VMware guest. http://blog.pluralsight.com/run-hyper-v-vsphere-5-1

~eric

View solution in original post

0 Kudos
2 Replies
POCEH
VMware Employee
VMware Employee
Jump to solution

Do you want to run hypervisor (HyperV) under hypervisor (ESX)? This is not a good idea even it is possible.

0 Kudos
ericsl
Enthusiast
Enthusiast
Jump to solution

No, I was simply converting a machine that already had the Hyper-V role enabled. I disabled Hyper-V and converted it again and it started properly.

However, I did find this article about modifying the vmx file to allow for a machine with Hyper-V enabled to run as a VMware guest. http://blog.pluralsight.com/run-hyper-v-vsphere-5-1

~eric

0 Kudos