Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Hey, I don't usually write guides, but I couldn't find one to follow for setting up Windows 11 in QEMU, so I figured I'll write what I found myself. I did this on Manjaro, but you should be able to do it from any distro. Since I just wrote the steps I got to get it to let me install, I can't promise it'll work flawlessly. If there's any later-on issues, just let me know.

 

Prerequisites:

Before starting, you need the following:

  • Windows 11 .iso from Microsoft [link]
  • OVMF - you need this for UEFI/secureboot. I used edk2-ovmf from the arch official repos.
  • SWTPM - you need this for TPM emulation. Again, i used swtpm from the arch repos.
  • qemu & virt-manager - if you don't already have these installed, they'll be in your distro's repo, more than likely.
  • virtio - once you have your VM set up, mount the latest image from here to install virtio drivers for things like networking [link]

Getting started:

In Virtual Machine Manager, create a new VM from the top-left corner.

For step 1, choose local install media.

For step 2, pick your Windows 11 iso. if it's not in the drop-down, choose it by clicking "Browse... > Browse local". It'll auto-detect the OS as Windows 10, this is fine.

For step 3, set your memory and CPU cores. the default (4gb & 2 cores) are the minimum for W11, so I set my RAM to 8gb, but you can always change these values later.

For step 4, make a virtual disk image. The minimum drive size for Windows 11 is 64gb, so it needs to be at least that big.

For step 5, choose your VM name, and then tick off Customize configuration before install.

 

Final setup:

In the overview section, set Firmware to UEFI x86_64: /....../OVMF_CODE.secboot.fd. It has to be secure boot, otherwise Windows 11 won't install. While I was looking into this, I saw some things saying OVMF_CODE.ms.fd instead, if your list has that, that should work as well.

image.png.b7594cea636a33080822ac120445ebfe.png

In boot options, tick off your virtual CD-ROM drive, and then set that as the highest boot priority:

image.png.bffb43d1cbd3d08b155e11186de4fe3d.png -> image.png.b170a4e96c4aba2b62d414defe07627d.png

Finally, add a virtual TPM module. the defaults (CRB, Emulated, 2.0) should be fine.

image.png

 

once you've done that, you should be all set! hit begin installation in the top-left, and you should be able to install Windows 11 without issue.

Post-install:

Once you're in windows, I found that I had to set the DNS manually. Just go to Windows' networking settings and set your preferred DNS server:

image.png.b3b63d6b940b022dda23f4b24f0997e9.png

 

 

Edited by Shawnsg
updated networking info
Link to post
Share on other sites

I've got a couple of questions:
1) Do spice quest tools work? https://www.spice-space.org/download.html 

(direct download link) https://www.spice-space.org/download/windows/spice-guest-tools/spice-guest-tools-latest.exe
They probably do but since you already have it setup it would be easy for you to check heh.

2) Have you tried running WinApps with Win11 client?

WinApps doesn't support Manjaro and is currently looking for maintainers, but there are forks that have Manjaro support, like this one.

I've got that fork setup on two Manjaro KDE desktops, works well with Windows 10 clients.
Curious if Win11 client would work as well. I mean if VirtIO drivers work, RDP is present and if these registry keys are still in use I think it should.

VGhlIHF1aWV0ZXIgeW91IGJlY29tZSwgdGhlIG1vcmUgeW91IGFyZSBhYmxlIHRvIGhlYXIu

Link to post
Share on other sites

I followed the guide.  I used the virtio-win iso to install the Display Adapter.  The "Red Hat QXL controller" driver is installed but comes up with an "!" that says:

 

Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)

 

That same driver works fine in Windows 10 Pro ... so I'm guess Windows 11 is asking for a signed driver.  The result is not able to resize the screen.  Did you have a work around for this?

 

(Nice guide, by the way!)

 

 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×