Windows 10: W10 VM on W2K19 VM on KVM Host !! nested VM's

Hi folks

So far got HYPER-V to run on a Virtual machine creating a lower level W10 VM - The W2K19 machine is itself a VM running on under KVM/QEMU

So far only got Gen 1 to work -- with Gen 2 machine starts but no video - will look at that later

but here's the Gen 1 VM

So LVL 0 --> Host (Arch linux KVM kernel 5.10.7)
LVL1 W2K19 server with HYPER-V enabled
LVL2 W10 Pro running as a VM on LVL1 VM





Now to sort out networking !!!!! to the main Host

This gets to be quite fun

BTW you need in the host to enable nested virtualisation of course and set the CPU to passthru (in the cpu use host-passthru in the dropdown if using virtual machine manager .

Cheers
jimbo

:)

 

KVM Host --W10 VM with HYPER -V running another VM (Nesting)


Hi there.

It seems some CPU's will handle HYPER-V in a VM running on a Host where a HYPERVISOR (KVM in this case) is already running.
One needs to make a few mods otherwise booting up the VM running UNDER the HYPER-V (the 2nd level VM) will freeze.

I'm currently playing with this -- it looks like some modules from QEMU need to be updated -- and one needs to use IOMMU to get any sort of decent I/O throughput - even on SSD's.

I'll post back when I've got some better results -- note I haven't a CLUE about AMD CPU's . I think also getting USB and SOUND on to the second level VM could be a problem. PCI passthru is pretty easy from the KVM Host to the Windows VM (ist level) but passing that to the second level VM is proving somewhat problematical.

(HOST --CENTOS 7 with KVM, ist level VM W10 pro with HYPER-V enabled, second level VM W7 ultimate -- all x-64 machines).

I believe also performance can be improved by switching from Full virtualisation to "Para virtualision" on the guests -- easily enough done with settings in KVM - but then passthru gets a bit ????.

Anyway I've got some time to play with all this --when I'm done I'll post a guide. It should work also for most other common Linux distros capable of running KVM.

Tip - don't use the libvirt manager GUI as a console for your VM's as once in Full screen you can't always get back to Windowed mode -- might be my mouse etc. Use RDP / VNC instead -- no problem connecting to VM's even if you are running the VM's on your local machine.

Cheers
jimbo

 

KVM Host --W10 VM with HYPER -V running another VM (Nesting)


Hi,

I would also like to try this on Ubuntu 14.04
Can you please let me know how to get it working.
You mentioned that some modules of QEMU needs to be updated.
Any details on how to get this working will be helpful

Regards,
Sagar

 

Account failed logon 4625 on VM guest when clicking the entry of VM guest on failover cluster Manager on VM Host

Issue:

We found a multiple failed logon events on VM guest (evert ID 4625) with account (the account you logon on VM host) when we clicking the entry of VM guest on failover cluster manager console on VM host with Integration servers (Data Exchange) is enabled.



How to reproduce:

1. Check the “Data Exchange” is enabled on a VM guest (Enabled by default, right?)
2. Open Failover Cluster Manager Console on VM host.
3. Click the VM guest entry
4. Then you may found multiple failed logon events on that VM guest.

Reference:

Hyper-V Integration Services



Question:

1. Does the multiple failed logons are normal or necessary?
2. If the failed logons are normal and necessary to be happened and the “Data exchange” function is good to be enabled to gather data from VM guest, any recommendation for us to correct or avoid these failed logon?

Please advise.



Constrain:

We have no chance to use same account and password on VM hosts and VM guests (because all account are managed by password management) and the Audit Policy of Audit Credential Validation must be enabled.