In a test environment I have ESXi 5.1 installed on bare metal, then nested ESXi 5.1 server VMs and a couple guest VMs on that. I've been trying to nest Hyper-V 2012 (unsupported, I know) in that environment and keep running into what appears to be corruption of the Hyper-V VM. I've had the Hyper-V 2012 running with two guest VMs up for several days, then find the server VM has gone into an unrecoverable 'invalid state'.
Recently I've been consistently seeing ESXi throwing a pink screen crash when I start a nested Hyper-V guest VM. My sense is that the cause of my troubles is ESXi's memory overcommit and/or Hyper-V's lack of support for it, when the Hyper-V VM's committed memory butts heads with ESXi's need to expand memory for other VMs. I haven't seen anything in logging, only a sharp spike in resource utilization when the guest VM starts and before the server crashes.
Has anyone else seen these behaviors with nested Hyper-V 2012, or have any ideas?
Thanks