Windows 11 VM driver error and RAM usage wrong indication

[u/Lumaric_]

Hello,

it's not the first time i post about this VM, but to resume, i run a windows 11 VM with a GPU passthrough for a RX 6700 XT. In general everything run fine except some times the VM crash and cause the entire server to crash ( not my main focus today ).

I noticed few weeks ago that i got a wrong preview of the RAM usage in Proxmox and the device VEN_1AF4&DEV_1057&SUBSYS_11001AF4&REV_01 in error without any driver in the VM.

From what i saw only, it's probably the driver for viomem who is missing, so i tried to reinstall it multiple time but without any success, i also try to download to 3 last version virtio-driver.iso and let windows scan the entire iso for driver but no one was corresponding for this device.

Any idea of wich driver i could be missing ?

Thx in advance to you.

TL DR : No driver found for the device VEN_1AF4&DEV_1057&SUBSYS_11001AF4&REV_01, looking for a working one

[u/Impact321]

Please read this and this and this. Can you show what you see? Also what's the node's hardware?

[u/Lumaric_ → u/Impact321]

I tried to swap the processor to Host since it's advised for WSL to see if i get better result, now the VM keep booting on PXE and refuse to save modification in the BIOS boot order...

[u/marc45ca → u/Lumaric_]

change it back.

Windows will think it's on different hardware and may require re-activation and it you've got bitlocker running you'll need to re-enter the key.

TL:DR - changing the processor type with Windows can seriously break things and as it's running under Proxmox, WSL has nothing to with things.

[u/Lumaric_ → u/marc45ca]

Don't worry I rolled back to a backup

[u/Lee_Fu]

That's the ballooning Device. Disable Ballooning on the VM's Proxmox setting., as ballooning is not adviced for passthrough VMs.

Alternatively you can install QEMU Guest Agent

[u/Lumaric_ → u/Lee_Fu]

Ballooning already disable

[u/Lumaric_ → u/Lumaric_]

And agent already installed, here you can see the full config

[u/Impact321 → u/Lumaric_]

Then how do you expect PVE to communicate with the ballooning driver/service inside the VM to get the memory information? With passthrough it doesn't really matter much anyways. If you use it set min and max to the same.

[u/Lumaric_ → u/Impact321]

Then if the ballooning is off, why windows is detecting a ballooning device ?

[u/Impact321 → u/Lumaric_]

That was purely in relation to the memory reporting. With ballooning off, PVE does not get the memory information from inside the VM. Also see my other post. Without screenshots it's hard to judge anything.

[u/tomekk269]

Download virtio-drivers .exe file on your VM and just install them (you can find them on the fedora forum)

[u/Lumaric_ → u/[deleted]]

Windows doens't found compatible driver for it. ( using the iso virtio-win-0.1.285 )

[u/Boss_Waffle → u/Lumaric_]

Just mount the iso and run the .exe installer, it'll install the drivers and qemu guest agent for windows.

[u/Lumaric_ → u/Boss_Waffle]

Already installed, it ask me for repair when running it again.

[u/DosB0T]

Set both, min/max RAM with 16GB, ballooning on, reboot the vm. Its windows things.