Error installing Win 11 on QEMU/KVM


martyfelker

Well-known member
Member
VIP
Local time
5:46 PM
Posts
366
Location
Floyd, VA USA
OS
Fedora Silverblue Rawhide Debian 13 Ubuntu 25.10,
Got this interesting screen when try to boot into a Win 11 omsta;;atopm pm QEMU/KV<
 

Attachments

  • Screenshot_win11_2023-06-18_00:43:39.png
    Screenshot_win11_2023-06-18_00:43:39.png
    2.5 KB · Views: 8

My Computer My Computer

At a glance

Fedora Silverblue Rawhide Debian 13 Ubuntu 25...AMD Ryzen 7 7800X3D 8-Core64GBNvidia
OS
Fedora Silverblue Rawhide Debian 13 Ubuntu 25.10,
Computer type
PC/Desktop
Manufacturer/Model
HomeBrew
CPU
AMD Ryzen 7 7800X3D 8-Core
Motherboard
Gigabyte
Memory
64GB
Graphics Card(s)
Nvidia
Monitor(s) Displays
Dell
Hard Drives
3 ssd 2 spinners configured as raid 0
Keyboard
Eluktronics
Mouse
Eluktronics
Browser
Firefox and Chromium
Other Info
Gnome 46
Got this interesting screen when try to boot into a Win 11 omsta;;atopm pm QEMU/KV<
Sometimes you get that if you've specified the wrong or an unbootable boot device in the Virtual Machines config menu -- if you click the show boot menu in the virtual machine manager and then when booting the VM you see that screen just type EXIT and you should then see a list of bootable devices. It's not usually "An error".

If you've also specified "virtio" as the type of disk rather than SATA then windows won't load initially since it won't have a disk driver - If you want to use virtio (and it's better than the standard sata / ahci driver) then once you've booted up windows install the virtio drivers from the fedora site - iso is available for direct download. Install on the GUEST of course !!!!. Same for the NIC's -- unless you've got a spare nic on your pc to pass thru to the VM use virtio for the NIC adapter -- better performance than the standard e1000e virtual adapter. If poss try and avoid shared wifi from the host. If you must use wifi then it's better to use a separate usb>wifi adapter for the VM.

If you use a separate physical NIC for networking in the GUEST then you don't need to specify NAT, Bridging or even any NIC at all in the VM's config- -- Just add directly to the GUEST either by USB redirect, add Host USB device or add Host pci device in the config and install any relevant driverson to the guest. Host to guest communication (and vice versa) will work just as llike any other two physical machines on a LAN

I have on my test HOST machine 2 LAN devices so I can dedicate one to the VM. Direct LAN gives network performance almost 100% of the Host. (Use Bridging rather than NAT if you can't add a separate usb type wifi / lan adapter etc) - but that's another story too).

Screenshot_20230730_102113.png

for example (I've deliberately set boot from a non bootable disk for an example to replicate your screens)

Screenshot_20230730_105731.png

after entering EXIT - (English ??? Enter Exit sounds like a contradiction in terms !!!) you should see bootmanager and then

Screenshot_20230730_105827.png


select your device -- etc.


Cheers
jimbo
 
Last edited:

My Computer My Computer

At a glance

Windows XP,11 Linux Fedora Rawhide pre-releas...2 X Intel i7
OS
Windows XP,11 Linux Fedora Rawhide pre-release 46
Computer type
PC/Desktop
CPU
2 X Intel i7
Screen Resolution
4KUHD X 2
Back
Top Bottom