January 26, 20251 yr I didn't realize it was a big no-no, and from my Windows 10 Pro VM I went into "Add/Remove Windows Features" and ticked ON the Hyper-V feature. Now the Windows VM does not boot. I tried changing the order of the boot and booting from the ISO and I don't see any way to get into Safe Mode. None of the recovery options are working. Going into the recovery console DOS mode doesn't help me as the DSIM commands won't let me remove the Hyper-V component now. I really don't want to re-install the Windows VM unless I absolutely must... I also tried just disabling the Hyper-V from the VM settings, thinking maybe without it it will work, didn't help as well... Is there a simple solution for my problem?
February 2, 20251 yr On 1/26/2025 at 3:39 PM, DrMor said: I didn't realize it was a big no-no... I have the same problem and I am still looking for a solution to this issue. But, could you please elaborate on why is this a big no-no? I feel like I am missing something. Thanks.
February 2, 20251 yr Author 4 minutes ago, si3glaw said: I have the same problem and I am still looking for a solution to this issue. But, could you please elaborate on why is this a big no-no? I feel like I am missing something. Thanks. Yeah, I don't really understand why. It's a no-no because it breaks the VM, but why exactly I have no idea. If anyone can explain that'll be great.
February 2, 20251 yr From my undestanding, so called nested virtualization is possible and it's also supported, regarding the MS Hyper-V... But I also haven't yet found a way to achieve this. Everytime I enable HV functionality inside MS Server 2022, same thing happens. It breaks the VM and it seems like something is totally blocking the CPU cores. Furthermore, I am not trying to find the proper CPU parameters for XML template. So far, w/o success... I have a i9-14900KS and I am trying to find settings based on this CPU. When / IF I find anything, I will let you know.
February 18, 20251 yr Solution https://gitlab.com/qemu-project/qemu/-/issues/1031 To wrap up: . enable pass through with additional XML lines You can put these lines just above the end of the /domain line as show below. <qemu:commandline> <qemu:arg value='-cpu'/> <qemu:arg value='host,level=30'/> </qemu:commandline> </domain> From what I read these parameters work with Intel 12th, 13th and 14th (mine) Gen processors. I wrote this post under a different topic weeks ago, sorry about late response. Edited February 18, 20251 yr by si3glaw line format.
March 4, 20251 yr Author On 2/18/2025 at 12:52 PM, si3glaw said: https://gitlab.com/qemu-project/qemu/-/issues/1031 To wrap up: . enable pass through with additional XML lines You can put these lines just above the end of the /domain line as show below. <qemu:commandline> <qemu:arg value='-cpu'/> <qemu:arg value='host,level=30'/> </qemu:commandline> </domain> From what I read these parameters work with Intel 12th, 13th and 14th (mine) Gen processors. I wrote this post under a different topic weeks ago, sorry about late response. YES! That solved it. So simple. Thank you so much!
September 11, 2025Sep 11 For a brief moment I thought that this fixed my non-booting Windows 10 VM. It stopped working after I migrated my Unraid server to Ugreen DXP8800 Plus. But the reason why it finally booted, was that I dropped allocated cores to just one. So if anyone knows how I can allocate more, please tell.Also, if I add the extra qemu:commandline tags, it complains about hyperv vpindex support.
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.