- Minor
No issues in 6.7.2.
Existing VMs (Server 2016) with hyper-v enabled won't boot after update -> stuck at TianoCore Logo
Booting into recovery mode works, booting from a install DVD to load virtio drivers and modifiy the bcd works.
Removing "hypervisorlaunchtype auto" from bcd makes the VM boot (but disables hyper-v)
How to reproduce: (in my case, I hope its not just me ...)
1) new VM with Server 2016 Template
2) Install Server 2016/2019
3) enable hyper-v and reboot.
It should either not reboot, boot into recovery or come back with a non working "VMbus" Device in Device manager.
Testet with cpu paththrough (default) and cpu emulation (skylake-client), i440fx (default) and q35.
Coreinfo.exe always shows vmx and ept present in windows. (see screenshot))
Tried to add vmx explicitly without any change, but as far as windows goes, its always enabled.
<feature policy='require' name='vmx'/>
Without kvm_intel active, the unraid-server notices it and says it should be enabled.
# lsmod | grep kvm
kvm_intel 196608 8
kvm 380928 1 kvm_intel
I did not get the chance to test 6.8.0 and could not find a link/archive.
I would test 6.8.0 to see if that qemu/libvirt version works.
Installing hyper-v creates a "VMbus" device in windows, that is not working if you remove "hypervisorlaunchtype auto" from bcd.
I think qemu also uses a "VMbus" device to make Windows VM compatibility easier. Maybe thats part of the "Hyper-V" option in the unraid templates?
Have not tried other hypervisors or windows 10 hyper-v.
As far as kernel options go, "iommu=pt" is a needed workaround for the cheap marvell controller.
I'll try to to install the next server in english for better screenshots 
-
2
