Greetings, I'm running Hyper-V (2012 not R2) nested on vSphere 6.0
Everything works except the Hyper-V integration services. The virtual machines on Hyper-V for some reason thinks they are a physical system and they don´t let start/install/upgrade the integration services. Some screenshots documenting the issue:
I've tried everything I know or been able to find:
I've seen this issue documented in this post: http://vblog.is/?p=94 and the solution seems to downgrade the ESXi 6.0 host to 5.5 and that is not an option for me (and I really need the integration services running for testing purposes).
Any help will be appreciated, thanks,
Sorry. It looks like the issue was only fixed for AMD hardware in vSphere 6.0P01.
I'm going to try to push a patch through for vSphere 6.0P02. Unfortunately, I cannot come up with a viable workaround in the interim.
Please try vSphere 6.0p01 or later (U1 is available now).
Thank you for your quick response, I've updated my eviroment to 6.0 U1 as you suggested and the behavior is the same: the integration services on the nested Hyper-V vms doesn't work at all (the integration services doesn't start or can be updated / installed).
Any other suggestion? Thanks in advance,
If you suspended the Hyper-V VM to do the upgrade, you will have to power it off and power it on again. If not, can you upload the latest vmware.log file?
Sorry. It looks like the issue was only fixed for AMD hardware in vSphere 6.0P01.
I'm going to try to push a patch through for vSphere 6.0P02. Unfortunately, I cannot come up with a viable workaround in the interim.
No problem, good to know it is not possible right now
Can you explain a little what is the issue?
Thanks for your time and support,
When a nested VM issues a CPUID instruction from ring 3, the emulation of the instruction is being handled by the host hypervisor rather than the guest hypervisor. Since the Hyper-V VM has to be configured so that CPUID reflects a physical system (or Hyper-V will refuse to load), that's also what the nested guest sees.
The fix doesn't appear to have been included in ESXi600-201511001 either. Any idea when it will become available?
I am trying to push it into ESXi 6.0 Update 2, but since this isn't a supported configuration, it may not make the bar.
Thank you for the update, please let us know any advance
The change has been accepted for ESXi 6.0 update 2. (Sorry; I can't give you a date for that.)
I'm really happy to report that this seems to be working again now that vSphere 6.0u2 has shipped! During my initial testing of nested Hyper-V in vSphere 6.0u1, Integration Services were failing to show VM heartbeat, as described in this thread. See:
Testing again with vSphere 6.0u2 as jmattson suggested, appears this issue has been resolved. Thanks so much to the VMware team for getting this issue worked out! Validated with nested Windows Server 2016 TP4 with Hyper-V and a Windows Server 2016 TP4 VM (see screenshot below). I suspect all other versions of Windows w/Hyper-V will work without issue.
Cheers,
-@youngtech
Thanks jmattson! Looks like that did the trick (see reply).
Cheers!
-@youngtech