internal error: Missing udev property 'ID_VENDOR_ID'

TheProf

Active Member
Credits
1,303
I've been trying to troubleshoot an issue I've been seeing in QEMU/KVM/Virt manager where the libvirtd service upon startup throws the following error:

Code:
Sep 09 22:27:12 end0S libvirtd[487]: internal error: Missing udev property 'ID_VENDOR_ID' on 'usb1'
Sep 09 22:27:12 end0S libvirtd[487]: internal error: Missing udev property 'ID_VENDOR_ID' on '1-11'
Sep 09 22:27:12 end0S libvirtd[487]: internal error: Missing udev property 'ID_VENDOR_ID' on '1-5'
Sep 09 22:27:12 end0S libvirtd[487]: internal error: Missing udev property 'ID_VENDOR_ID' on '1-5.1'
Sep 09 22:27:12 end0S libvirtd[487]: internal error: Missing udev property 'ID_VENDOR_ID' on '1-5.3'
Sep 09 22:27:12 end0S libvirtd[487]: internal error: Missing udev property 'ID_VENDOR_ID' on '1-9'
Upon further searching online trying to figure out why this is not working, some of the folks mentioned that this is due to not having a rule setup in UDEV for Vendor ID. When I check this using:

Code:
udevadm info --export-db
Based on my understanding, this is not the case, as the Vendor ID actually is configured:

Code:
P: /devices/pci0000:00/0000:00:14.0/usb1/1-11
N: bus/usb/001/005
L: 0
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-11
E: SUBSYSTEM=usb
E: DEVNAME=/dev/bus/usb/001/005
E: DEVTYPE=usb_device
E: DRIVER=usb
E: PRODUCT=5e3/610/3298
E: TYPE=9/0/2
E: BUSNUM=001
E: DEVNUM=005
E: MAJOR=189
E: MINOR=4
E: USEC_INITIALIZED=4990390
E: ID_VENDOR=05e3
E: ID_VENDOR_ENC=05e3
E: ID_VENDOR_ID=05e3
E: ID_MODEL=USB2.0_Hub
E: ID_MODEL_ENC=USB2.0\x20Hub
E: ID_MODEL_ID=0610
E: ID_REVISION=3298
E: ID_SERIAL=05e3_USB2.0_Hub
E: ID_BUS=usb
E: ID_USB_INTERFACES=:090001:090002:
E: ID_VENDOR_FROM_DATABASE=Genesys Logic, Inc.
E: ID_AUTOSUSPEND=1
E: ID_MODEL_FROM_DATABASE=Hub
E: ID_PATH=pci-0000:00:14.0-usb-0:11
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_11
E: ID_FOR_SEAT=usb-pci-0000_00_14_0-usb-0_11
E: TAGS=:seat:
E: CURRENT_TAGS=:seat:
What is interesting is that for USB1 (1-11) I do not see this property:

Code:
P: /devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.0
L: 0
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.0
E: SUBSYSTEM=usb
E: DEVTYPE=usb_interface
E: DRIVER=hub
E: PRODUCT=5e3/610/3298
E: TYPE=9/0/2
E: INTERFACE=9/0/2
E: MODALIAS=usb:v05E3p0610d3298dc09dsc00dp02ic09isc00ip02in00
E: USEC_INITIALIZED=5656720
E: ID_USB_CLASS_FROM_DATABASE=Hub
E: ID_USB_PROTOCOL_FROM_DATABASE=TT per port
E: ID_VENDOR_FROM_DATABASE=Genesys Logic, Inc.
E: ID_AUTOSUSPEND=1
E: ID_MODEL_FROM_DATABASE=Hub
E: ID_PATH=pci-0000:00:14.0-usb-0:11:1.0
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_11_1_0
Am I missing something? Not really sure if its related to some IDs missing while others are there? Anyone run into this issue before?

I can confirm this happens on every new install I've done minus Fedora.

Btw, QEMU/KVM work, no issues.. just that I am seeing these errors after installation.
 


f33dm3bits

Gold Member
Gold Supporter
Credits
24,139
I've never come across this error so doesn't sound familiar, does libvirtd successfully start or does it fail to start because of this error? Is this on EndeavourOS?
 

TheProf

Active Member
Credits
1,303
I've never come across this error so doesn't sound familiar, does libvirtd successfully start or does it fail to start because of this error?
No issues what so ever with Libvirtd, this error only happens when I start the libvirtd service. Since I have it enabled, it always starts on boot and I see this error.

I am using endeavourOS, but I was also seeing this on Manjaro as well.
 

f33dm3bits

Gold Member
Gold Supporter
Credits
24,139
Have you updated your system, you most likely have but just to double checking.
 

TheProf

Active Member
Credits
1,303
yep, updated to the latest version as far as I can see with pacman.

I am wondering if it is related to my USB hub, as currently have the HUB attached to my PC and I have USB devices on that hub, such as wireless headset dongle, mouse dongle, keyboard, and some other cables that are connected to the charging ports.
 

f33dm3bits

Gold Member
Gold Supporter
Credits
24,139
Thought so, then I'd start by going throught the libvirt configuration section of the Archwiki, that's what I would do in your situation.
 

dcbrown73

Well-Known Member
Credits
2,827
Everything points to this being an issue with udev rulesets I believe. Not an issue with libvirt. I suspect the udev toolset is not returning the information libvirt is expecting.

While you're seeing this error, I suspect everything is running fine correct? I think it's just angry that it received a null (or something similar) for ID_VENDOR_ID.
 

KGIII

Super Moderator
Staff member
Gold Supporter
Credits
25,899
I came across a cryptic comment under this question:


They explicitly defined the device path and give an example of it. That may be worth looking into.
 

TheProf

Active Member
Credits
1,303
I came across a cryptic comment under this question:


They explicitly defined the device path and give an example of it. That may be worth looking into.
Thanks KGIII, I will look into this as well.
 
$100 Digital Ocean Credit
Get a free VM to test out Linux!

Members online


Top