No problem getting Hyper-V running on vSphere 5.1, but on the same hosts under vCloud it fails with the Add Roles & Features claiming that there is already another hypervisor running. I'm 99% certain I've made all the expected changes & hacks, and ESXi runs fine - though it has always been more forgiving.
What did I miss? Or is this not currently possible?
The kety bit I was missing was:
You will need to add one additional .vmx parameter which tells the underlying guestOS (Hyper-V) that it is not running as a virtual guest which in fact it really is. The parameter is hypervisor.cpuid.v0 = FALSE
As William Lam has documented here: http://www.virtuallyghetto.com/2012/08/how-to-enable-nested-esxi-other.html
So the process I followed was:
It can probably be all done from vCD...
Setting the guestOS to "winHyperV" works great in vSphere, but on import to vCD it would get changed to "32bit other" (I don't recall the exact lettering).