You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to test Hyper-V virtualization for a cross-platform AI agent sandboxing solution and couldn't get Windows 11 to boot after enabling Hyper-V.
I did have /sys/module/kvm_intel/parameters/nested enabled by default. After trial and error, I found out that certain cpu flag changes are needed. It's able to boot after adding "-hypervisor".
However, after many attempts, I didn't get things working with quickemu and switched to libvirt.
Here's the guide for installing Windows with quickemu and then migrating to libvirt. WSL2 works fine now. https://gist.github.com/lhotari/907e903f3360af340aac42b2f3c458ea
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I wanted to test Hyper-V virtualization for a cross-platform AI agent sandboxing solution and couldn't get Windows 11 to boot after enabling Hyper-V.
I did have
/sys/module/kvm_intel/parameters/nestedenabled by default. After trial and error, I found out that certain cpu flag changes are needed. It's able to boot after adding "-hypervisor".However, after many attempts, I didn't get things working with quickemu and switched to libvirt.
Here's the guide for installing Windows with quickemu and then migrating to libvirt. WSL2 works fine now.
https://gist.github.com/lhotari/907e903f3360af340aac42b2f3c458ea
Beta Was this translation helpful? Give feedback.
All reactions