Win(PE) NIC issue with pc-q35-6.1

Host environment

• Operating system: Fedora 35
• OS/kernel version: 5.15.6-200.fc35.x86_64
• Architecture: amd64
• QEMU flavor: qemu-system-x86_64
• QEMU version: 6.1.0 (qemu-6.1.0-10.fc35)
• QEMU command line (possibly incomplete, using virt-manager):

  ./qemu-system-x86_64 -M pc-q35-6.1 -m 4096 -enable-kvm -hda hd.qcow2 -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 -device e1000e,netdev=hostnet0,id=net0,mac=[...],bus=pci.1,addr=0x0

Emulated/Virtualized environment

• Operating system: WinPE (German localisation) (Setup.wim from Windows 10 21H2 and 20H2 i believe)
• OS/kernel version: not sure, WDS states 10.0.19041
• Architecture: amd64

Description of problem

When booting WinPE (via PXE via WDS) on a pc-q35-6.1 machine, the NIC will not initialize.

What I got with pnputil.exe /enum-devices /class net is Device has problem: 56 0x38 (CM_PROB_NEED_CLASS_CONFIG) See: CM_PROB_NEED_CLASS_CONFIG

I'm using virt manager and I've tried both e1000e and virtio network adapters (virtio with drivers injected into the image of course). Both yield the aforementioned error and ipconfig remains empty. This is an obscure problem - I haven't checked if a normal windows install behaves the same way, but it might be unique to winpe.

However, with pc-q35-5.2, the NIC initializes without a problem.

Steps to reproduce

1. Create pc-q35-6.1 based vm in virt manager with default settings (network bridged to network bridge)
2. PXE boot Windows Setup
3. Observe hang (observe errors with console SHIFT+F10)

Steps to reproduce working

1. Create pc-q35-5.2 based vm in virt manager with default settings (network bridged to network bridge)
2. PXE boot Windows Setup
3. Observe vm working as normal

Additional information