[SOLVED] Unknown VEN_1AF4&DEV_1057 device

[bly]

Hi all, I am stuck with an unknown PCI device VEN_1AF4&DEV_1057 in my Windows 11 VM, can someone tell me what is it and how to fix the missing driver issue?

I noticed it after a migration from Windows 10 to 11, I did those steps without success:
- added virtio 0.1.266 disk and did "repair" install for both virtio drivers and qemu guest

The VM also run at 100% CPU all time but dunno if related to this issue.
Attached here a snapshot of its settings, if you see something amiss please tell me.
TIA, Andrea

 

[bly]

Options setting:

 

[gfngfn256]

Your config looks pretty regular, just not sure why the main HD is called virtio0 and not the usual scsi0 for your config - maybe some historic messing around?

The VM also run at 100% CPU all time

Try giving it 4 or 6 cores & see what happens.

unknown PCI device VEN_1AF4&DEV_1057

So that is Vendor 1AF4, which is Red Hat, & Device 1057
This site - which usually has all the Red Hat virtual devices also does not find it. The closest I found is device 1053 which is a VirtIO socket. Strange. What is the history of this VM?
Maybe just disable/remove this device in Windows & see what happens. If not you can just ignore it.

 

[leesteken]

It's probably the virtual IOMMU (but I couldn't be bothered to check), which is rather new. Do you really need that? Have you tried using the Intel variant instead of the VirtIO one? Proxmox does not make the VirtIO drivers, so maybe ask fedorapeople.org when they have a Windows 11 driver?

 

[bly]

It's probably the virtual IOMMU (but I couldn't be bothered to check), which is rather new. Do you really need that? Have you tried using the Intel variant instead of the VirtIO one? Proxmox does not make the VirtIO drivers, so maybe ask fedorapeople.org when they have a Windows 11 driver?

Hi, it seems it is it.
For some reason it wasn't automatically detected and I had to update the driver with the "have disk" option to let it to be installed.
I "suppose" it is it because if I try to load a different driver, the system warns me the driver may be not the one for the device I am installing it to, but in this case I hadn't any warning, and install went fine and device shows properly without the usual "not enabled" mark that happens when you mess with wrong drivers.

 

[bly]

Maybe just disable/remove this device in Windows & see what happens. If not you can just ignore it.

Hi, installing the memory driver above it also solved the 100% CPU issue. They were related, indeed.