Comment 3 for bug 2031078

should be related to another bug I filed to netplan
https://bugs.launchpad.net/netplan/+bug/1999181

here's journalctl output, with "default logging" enabled in libvirtd.conf
I keep the sequence of log entries as output from journalctl, but deleted not that relevant entries; let me know if I should expect / keep something
=========================================================
Aug 16 18:21:28 ****** audit[399]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirtd//qemu_bridge_helper" pid=399 comm="apparmor_parser"
Aug 16 18:21:29 ****** systemd-networkd[319]: eth1: Interface name change detected, renamed to i350_p1.
Aug 16 18:21:29 ****** kernel: igb 0000:09:00.0 i350_p0: renamed from eth0
Aug 16 18:21:29 ****** kernel: ixgbe 0000:01:00.0: Intel(R) 10 Gigabit Network Connection
Aug 16 18:21:29 ****** systemd[1]: Started Virtualization daemon.
Aug 16 18:21:29 ****** systemd-networkd[319]: eth0: Interface name change detected, renamed to i350_p0.
Aug 16 18:21:29 ****** systemd[1]: Starting Suspend/Resume Running libvirt Guests...
Aug 16 18:21:29 ****** kernel: ixgbe 0000:01:00.1: enabling device (0000 -> 0002)
Aug 16 18:21:29 ****** systemd[1]: Started Dispatcher daemon for systemd-networkd.
Aug 16 18:21:29 ****** systemd[1]: Finished Suspend/Resume Running libvirt Guests.
Aug 16 18:21:29 ****** systemd[1]: Reached target Multi-User System.
Aug 16 18:21:29 ****** systemd[1]: Startup finished in 26.344s (firmware) + 6.367s (loader) + 2.337s (kernel) + 1.888s (userspace) = 36.938s.
Aug 16 18:21:29 ****** libvirtd[437]: 468: info : libvirt version: 8.0.0, package: 1ubuntu7.6 (Rafael Lopez <email address hidden> Tue, 20 Jun 2023 11:54:15 +1000)
Aug 16 18:21:29 ****** libvirtd[437]: 468: info : hostname: ******
Aug 16 18:21:29 ****** libvirtd[437]: 468: error : networkCreateInterfacePool:2250 : internal error: No usable Vf's present on SRIOV PF x540_p0
Aug 16 18:21:29 ****** libvirtd[437]: 468: error : networkCreateInterfacePool:2250 : internal error: No usable Vf's present on SRIOV PF i350_p0
Aug 16 18:21:29 ****** libvirtd[437]: 468: error : networkCreateInterfacePool:2250 : internal error: No usable Vf's present on SRIOV PF x540_p1
Aug 16 18:21:29 ****** libvirtd[437]: 468: error : networkCreateInterfacePool:2250 : internal error: No usable Vf's present on SRIOV PF i350_p1
Aug 16 18:21:29 ****** kernel: ixgbe 0000:01:00.1: Multiqueue Enabled: Rx Queue count = 4, Tx Queue count = 4 XDP Queue count = 0
Aug 16 18:21:29 ****** kernel: ixgbe 0000:01:00.1: 16.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x4 link at 0000:00:1c.0 (capable of 32.000 Gb/s with 5.0 GT/s PCIe x>
Aug 16 18:21:29 ****** networkd-dispatcher[411]: WARNING:Unknown index 6 seen, reloading interface list
Aug 16 18:21:29 ****** kernel: ixgbe 0000:01:00.1: MAC: 3, PHY: 0, PBA No: 000000-000
Aug 16 18:21:29 ****** kernel: igb 0000:09:00.1: 7 VFs allocated
Aug 16 18:21:29 ****** networkd-dispatcher[411]: WARNING:Unknown index 7 seen, reloading interface list
Aug 16 18:21:29 ****** kernel: ixgbe 0000:01:00.1: Intel(R) 10 Gigabit Network Connection
Aug 16 18:21:29 ****** kernel: igb 0000:09:00.0: 7 VFs allocated
Aug 16 18:21:29 ****** systemd-udevd[325]: i350_p0: Process '/usr/sbin/netplan apply --sriov-only' failed with exit code 1.
Aug 16 18:21:29 ****** systemd-udevd[316]: i350_p1: Process '/usr/sbin/netplan apply --sriov-only' failed with exit code 1.
Aug 16 18:21:30 ****** systemd-networkd[319]: i350_p0: Link UP
Aug 16 18:21:30 ****** systemd-networkd[319]: i350_p1: Link UP
Aug 16 18:21:30 ****** kernel: ixgbe 0000:01:00.1 x540_p1: SR-IOV enabled with 7 VFs
Aug 16 18:21:30 ****** kernel: ixgbe 0000:01:00.1: Multiqueue Enabled: Rx Queue count = 4, Tx Queue count = 4 XDP Queue count = 0
Aug 16 18:21:30 ****** kernel: ixgbe 0000:01:00.0 x540_p0: SR-IOV enabled with 7 VFs
Aug 16 18:21:30 ****** kernel: ixgbe 0000:01:00.0: Multiqueue Enabled: Rx Queue count = 4, Tx Queue count = 4 XDP Queue count = 0
Aug 16 18:21:31 ****** kernel: ixgbe 0000:01:00.0: registered PHC device on x540_p0
Aug 16 18:21:31 ****** systemd-networkd[319]: x540_p0: Link UP
Aug 16 18:21:31 ****** kernel: ixgbe 0000:01:00.1: registered PHC device on x540_p1
Aug 16 18:21:31 ****** systemd-networkd[319]: x540_p1: Link UP
=========================================================

I think it is basically libvirtd tries to start the virtual network when PF is up, but VF is not ready yet = systemd starts both netplan and libvirtd in parallel, but libvirtd starts virtual network faster than netplan can complete (related to that --sriov-only log), so libvirtd cannot autostart the virtual network; note that when console is available, I can start networs okay, as VFs are ready;