Comment # 2 on bug 1187555 from Gene Snider

Sorry about that, it does start.  I must have missed the success message when I
looked at the journal output.  Here is the full journal output:

> journalctl --no-hostname -b -u libvirtd
-- Logs begin at Thu 2021-05-06 15:57:41 PDT, end at Mon 2021-06-21 14:20:38
PDT. --
Jun 21 14:13:35 systemd[1]: Starting Virtualization daemon...
Jun 21 14:13:35 libvirtd[1132]: libvirt version: 7.4.0
Jun 21 14:13:35 libvirtd[1132]: hostname: Mobile-PC
Jun 21 14:13:35 libvirtd[1132]: Failed to initialize libnetcontrol.  Management
of interface devices is>
Jun 21 14:13:35 systemd[1]: Started Virtualization daemon.
Jun 21 14:13:36 libvirtd[1132]: internal error: Missing udev property
'ID_VENDOR_ID' on '3-2.1'
Jun 21 14:13:36 libvirtd[1132]: internal error: Missing udev property
'ID_VENDOR_ID' on '3-2.3'
Jun 21 14:13:36 libvirtd[1132]: internal error: Missing udev property
'ID_VENDOR_ID' on '3-2.4'
Jun 21 14:15:37 systemd[1]: libvirtd.service: Succeeded.

Is there any reason for the 'ID_VENDOR_ID' property to be missing?  No such
property shows up in the journal, except in that libvirtd message.

> journalctl -b | grep 'ID_VENDOR_ID'
Jun 21 14:13:36 Mobile-PC libvirtd[1132]: internal error: Missing udev property
'ID_VENDOR_ID' on '3-2.1'
Jun 21 14:13:36 Mobile-PC libvirtd[1132]: internal error: Missing udev property
'ID_VENDOR_ID' on '3-2.3'
Jun 21 14:13:36 Mobile-PC libvirtd[1132]: internal error: Missing udev property
'ID_VENDOR_ID' on '3-2.4'