May 15, 20233 yr I upgraded the motherboard of my Unraid server (5700G to 13600k) now some of my Windows VM's don't boot anymore. The weird thing is that one of the VM's boots without an issue but two other vm's don't. After starting the VM, its stuck at this screen: If I attach the vhd to a Fedora live CD I can mount the disk without an issue and browse my files. This is the configuration <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='15'> <name>Windows 10 LTSC</name> <uuid>dc313c0b-110a-fc81-94af-a97f54747022</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>9</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='4'/> <vcpupin vcpu='4' cpuset='5'/> <vcpupin vcpu='5' cpuset='6'/> <vcpupin vcpu='6' cpuset='8'/> <vcpupin vcpu='7' cpuset='9'/> <vcpupin vcpu='8' cpuset='10'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/dc313c0b-110a-fc81-94af-a97f54747022_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='9' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/user/domains/Windows 10 LTSC/vdisk1.img' index='1'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:d6:4b:da'/> <source bridge='br0'/> <target dev='vnet14'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/5'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/5'> <source path='/dev/pts/5'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-15-Windows 10 LTSC/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> <alias name='tpm0'/> </tpm> <graphics type='vnc' port='5902' autoport='yes' websocket='5702' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> beastserver-diagnostics-20230515-1504.zip Edited May 15, 20233 yr by gvh
May 16, 20233 yr Author Found out it was because WSL2 was enabled and nested virtualization is not supported on Raptor Lake. AM4 did support nested virtualization but 13th gen Intel does not. I was able to boot and run the system with the following changes to the config: <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>Broadwell-noTSX</model> <feature policy='disable' name='hypervisor'/> <feature policy='require' name='vmx'/> <feature policy='disable' name='svm'/> <feature policy='require' name='vme'/> <feature policy='require' name='f16c'/> <feature policy='require' name='rdrand'/> <feature policy='require' name='arat'/> <feature policy='require' name='xsaveopt'/> <feature policy='require' name='abm'/> </cpu> I could start and use my VM without an issue but it was really slow and capped at 4 cores (broadwell architecture?) All of the other cpu models I tried to emulate resulted in a message that the host cpu didn't support some of the features. After a lot of googling found out that this might be an issue in the current Linux kernel and we'll have to wait for a fix. At least I was able to save my VM, after booting I could disable WSL and set my CPU settings to the default settings. I'm now using an Ubuntu VM with remote-ssh in vscode instead of WSL. More info on emulating a CPU to get Hyper-V / WSL2 running: https://www.redpill-linpro.com/techblog/2021/04/07/nested-virtualization-hyper-v-in-qemu-kvm.html
May 16, 20233 yr Solution Yeah, the CPU has no actual issues with nested virt but something's broken in the kernel specifically for nested Hyper-V on intel... hopefully gets fixed at some point Edited May 16, 20233 yr by Kilrah
May 17, 20233 yr Author 10 hours ago, Kilrah said: Yeah, the CPU has no actual issues with nested virt but something's broken in the kernel specifically for nested Hyper-V on intel... hopefully gets fixed at some point The issue has been open since at least 2020 so I have no hope it will be solved soon. Not a lot of people are probably using nested virtualization with KVM / Windows. The frustrating thing is that I didn't even know this issue existed before I upgraded my CPU. I would've stayed with AM4 if I knew this would have been an issue.
May 17, 20233 yr 14 hours ago, gvh said: The issue has been open since at least 2020 so I have no hope it will be solved soon. Not a lot of people are probably using nested virtualization with KVM / Windows. The frustrating thing is that I didn't even know this issue existed before I upgraded my CPU. I would've stayed with AM4 if I knew this would have been an issue. When you say open since 2020, have you got a link, as I would like to track this issue, exact same situation, would have also gone with AMD ha. Edited May 17, 20233 yr by Nano
December 27, 20232 yr Thanks for the advice. Same happened to me with my new 13500. Ran 8700k before, and it was working just fine. Is this fixed in latest unraid version??
December 28, 20232 yr On 5/16/2023 at 9:52 PM, gvh said: Found out it was because WSL2 was enabled and nested virtualization is not supported on Raptor Lake. AM4 did support nested virtualization but 13th gen Intel does not. I was able to boot and run the system with the following changes to the config: <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>Broadwell-noTSX</model> <feature policy='disable' name='hypervisor'/> <feature policy='require' name='vmx'/> <feature policy='disable' name='svm'/> <feature policy='require' name='vme'/> <feature policy='require' name='f16c'/> <feature policy='require' name='rdrand'/> <feature policy='require' name='arat'/> <feature policy='require' name='xsaveopt'/> <feature policy='require' name='abm'/> </cpu> I could start and use my VM without an issue but it was really slow and capped at 4 cores (broadwell architecture?) All of the other cpu models I tried to emulate resulted in a message that the host cpu didn't support some of the features. After a lot of googling found out that this might be an issue in the current Linux kernel and we'll have to wait for a fix. At least I was able to save my VM, after booting I could disable WSL and set my CPU settings to the default settings. I'm now using an Ubuntu VM with remote-ssh in vscode instead of WSL. More info on emulating a CPU to get Hyper-V / WSL2 running: https://www.redpill-linpro.com/techblog/2021/04/07/nested-virtualization-hyper-v-in-qemu-kvm.html I tried uninstalling and disabling everything bound to WSL/wsl2, and then pasted my original xml for my win10, but it still wont start... Any ideas?
January 31, 20242 yr 2023年5月17日上午3点52分，gvh 说： 发现这是因为实现了WSL2和Raptor Lake上不支持撤销虚拟化。AM4确实支持撤销虚拟化，但第13代英特尔不支持。 我能够通过对配置进行以下更改来启动并运行系统： 我无法启动和使用我的虚拟机，但它真的很慢并且上限为 4 个核心（broadwell 架构？） 我尝试模拟的所有其他 cpu 型号都会显示一条消息，表明主机 cpu 不支持某些功能。 经过大量谷歌搜索发现这可能是当前Linux内核中的一个问题，我们必须等待修复。 至少我能够保存我的虚拟机，启动后我可以禁用WSL把CPU设置为默认设置。 我现在在 vscode 中使用带远程 ssh 的 Ubuntu VM，而不是 WSL。 有关模拟 CPU 以运行 Hyper-V / WSL2 的更多信息：https://www.redpill-linpro.com/techblog/2021/04/07/nested-virtualization-hyper-v-in-qemu-kvm.html 应该不是Raptor Lake不支持嵌套虚拟化，我使用Ubuntu22.04安装并使用Docker DESKTOP是完全没有问题的 Edited January 31, 20242 yr by ArchonX
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.