[SOLVED] Unknown VEN_1AF4&DEV_1057 device

B

bly

Member
Mar 15, 2024
48
10
8
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

1735122528940.png
 
Last edited:
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?

bly said:
The VM also run at 100% CPU all time
Click to expand...
Try giving it 4 or 6 cores & see what happens.

bly said:
unknown PCI device VEN_1AF4&DEV_1057
Click to expand...
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.
 
  • Like
Reactions: 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?
 
  • Like
Reactions: bly
leesteken said:
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?
Click to expand...
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.

1735206712882.png
 
Last edited:
Having the same issue here,
but the latest 1.266 virtio driver, in the Win11 folder under viomem, the device ID is 1058 instead of 1057.
Any idea?
 
Jay629 said:
Having the same issue here,
but the latest 1.266 virtio driver, in the Win11 folder under viomem, the device ID is 1058 instead of 1057.
Any idea?
Click to expand...
I think it's ok, as long as you select "have driver" then select it from the list after the warning it may not be the correct driver.
 
bly said:
I think it's ok, as long as you select "have driver" then select it from the list after the warning it may not be the correct driver.
Click to expand...
If I select browse for driver, and select the viomem folder, nothing shows up (no compatible driver found). Selecting the win11 sub-folder also shows nothing.
Looking at the inf file it's only for device 1058 so I guest something has changed in between.
 
Try this sequence (my system is in another language, translation on your system may be different).

From the unknown driver properties:
General > Driver > Update driver > Search from computer >
click on "Choose from driver list"
> All devices >
click on "Driver disk" > Navigate to viomem\<your system>\<your architecture>
When you click "OK" the driver "VirtIO Viomem Driver" will show up, select it
> Forward > Click YES on the warning panel of doom > Close > Close

HTH :)
 
  • Like
Reactions: LFS-Admin, Taomyn and yunmkfed
bly said:
Try this sequence (my system is in another language, translation on your system may be different).

From the unknown driver properties:
General > Driver > Update driver > Search from computer >
click on "Choose from driver list"
> All devices >
click on "Driver disk" > Navigate to viomem\<your system>\<your architecture>
When you click "OK" the driver "VirtIO Viomem Driver" will show up, select it
> Forward > Click YES on the warning panel of doom > Close > Close

HTH :)
Click to expand...
I have Windows Server 2022 and nothing comes up (0.1.266) I even attempted to let it go through the subdirectories under viomem.

Sorted. I reread the post and figured it out.
 
Last edited:
  • Like
Reactions: bly
You must log in or register to reply here.
Top Bottom