Fedora >> VMM >> Windows 11

I’m setting up Windows 11 and I need a network driver. I go through the files of the virtio-win iso file but amd64 is empty. Am I not supposed to use the virtio-win file? Am I in the wrong spot? Is something hidden? How do I get the network driver?

Thanks!!

The defaults for the network hardware can use a driver that is built into windows I thought.
I do not remember needing to find drivers for the network.

This is how I’m setup

And in the Windows Settings under Network I see this for the connection.

Didn’t work for me. Windows couldn’t ‘identify’ the network. But this is the screen I’m stuck on (before and after the bridge).

It seems it’s setting up a Wifi connection. Usually it’s a wired connect you have in the VM.

Can you share how you have the NIC setup in VMM for your VM?

Maybe Windows setup has changed since I set things up.

Windows isn’t asking for a Wi-Fi connection even though it’s using the symbol in the dialog that we associate with Wi-Fi. It’s asking you to provide any kind of network adapter that has Internet connectivity (a Windows 11 requirement) so that the OOBE setup can continue. Windows seemed to have found the virtual network adapter “Network” and provided it with a driver in the VM but has been unable to detect that it has Internet connectivity.

I would open a command prompt at this point (Shift-F10) and use Windows CLI commands like ipconfig to figure out if the discovered adapter is getting an IP address, default router, etc via DHCP and if it indeed can connect to the Internet. I’d also double check your virtual networking bridge configuration.

Did you make a network bridge for the VM? Is it working?
Can you post the output of ip addr on the host?
Also please confirm the host networking is good.

There is what looks like a good youtube tutorial at

How To PROPERLY Install Windows 11 on KVM (Updated for 2026)

It explains how get the virtio drivers for Windows and a lot of other things.

Hi Chris,

The “Device model” can be e1000e or virtio (if installed on the guest), and the “Network source” is “Virtual network ‘default’:NAT”. This usually puts you in the 192.168.122.0/24 network and uses the existing network connection on your hardware/host. Works fine as long as you are not trying to serve anything from the VM (like RDP …)

@barryascott ‘s VM’s virtual network adapter is configured as an e1000e device type which indeed does have a Windows out-of-the-box driver. You would only need to install the virtio NIC driver if you configured the VM’s virtual Network adapter as a virtio device.

I can’t open the CLI. I’ve got a Apple Magic keyboard and that’s making things even more interesting than trying to run Windows in Fedora.

How do you go about the network bridging? I found something but it didn’t resolve the issue;

sudo nmcli connection add type bridge autoconnect yes con-name [name of bridge] ifname [name of bridge]

sudo nmcli connection add type bridge-slave autoconnect yes con-name bridge-slave-[my ethernet] ifname [my ethernet] master [name of bridge]

sudo nmcli connection down [my ethernet]

sudo nmcli connection up [name of bridge]

Thanks, watching now.

What is the output of ip addr command?
Without this output we cannot know the state of your networking.