newunraidusers Posted November 30, 2020 Share Posted November 30, 2020 (edited) I wanted to enable hyper-v on a windows 10 guest. I was able to pass through everything GPU and all no issues and also setup nesting correctly as well. However, I encounter an issue where enabling hyper-v causes a boot loop on the windows 10 guest machine. I was wondering if this is a common issue and if there was any solution, all the research I looked into leads to a dead end. What happens is I get to the tianocore screen then the vm keeps rebooting until it goes through windows automatic repair thing, the only fix is doing a system restore which removes the hyper-v. Here are some places that don't have any working solution https://forums.unraid.net/topic/60452-640-rc9f-windows-10-vm-boot-loop/ https://www.reddit.com/r/HyperV/comments/89va1j/enabling_hyperv_causes_boot_loop/ vm config.txt syslinux config.txt Edited November 30, 2020 by newunraidusers server config Quote Link to comment
itimpi Posted November 30, 2020 Share Posted November 30, 2020 My suspicion is that this is something within Windows. I get exactly the same symptoms on real hardware (UDOO x86). Hyper-V used to work on this hardware but sometime earlier this year one of the Microsoft updates broke it and I get your symptoms. The UDOO can still quite happily run VMs under VirtualBox, just no longer able to run them under Hyper-V. I find this also means that I cannot use WSL2 on the UDOO - trying to enable that causes the same symptoms. Be interested if trying to activate WSL2 causes the same symptoms on your VM. Quote Link to comment
newunraidusers Posted December 1, 2020 Author Share Posted December 1, 2020 11 hours ago, itimpi said: My suspicion is that this is something within Windows. I get exactly the same symptoms on real hardware (UDOO x86). Hyper-V used to work on this hardware but sometime earlier this year one of the Microsoft updates broke it and I get your symptoms. The UDOO can still quite happily run VMs under VirtualBox, just no longer able to run them under Hyper-V. I find this also means that I cannot use WSL2 on the UDOO - trying to enable that causes the same symptoms. Be interested if trying to activate WSL2 causes the same symptoms on your VM. Hi i tried this. WSL worked normally however the WSL2 update did infact cause a bootloop issue Quote Link to comment
itimpi Posted December 1, 2020 Share Posted December 1, 2020 Interesting that you can get exactly the same symptoms on your VM as I get on real physical hardware. I would love hear if you find a solution as it is very likely that it would also work for me. Quote Link to comment
r4zr Posted December 4, 2020 Share Posted December 4, 2020 Similar problems on KVM on CentOS, seems to be an issue with the latest qemu packages: https://serverfault.com/questions/1036113/l0-kvm-and-win10-l1-nested-virtualization-not-working-windows-boot-loop https://bugs.centos.org/view.php?id=17788 Quote Link to comment
Recommended Posts
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.