Comment 4 for bug 2031078

I found that besides SRIOV pool, a storage pool cannot be auto-mounted as well, likely failing with the same reason = libvirt running too fast / early? it is a [dir pool] pointing to a dir on a mountpoint (4TB) with a 5400rpm HDD; root and boot reside on SATA SSD

extract from journalctl -b, timezone is GMT+8
-----------------------------------------------
Aug 30 02:15:56 ****** systemd[1]: Found device ST4000LM016-1N2170 NTFS.
Aug 30 02:15:56 ****** systemd[1]: Mounting /****/4TB...
Aug 30 02:15:57 ****** libvirtd[450]: internal error: No usable Vf's present on SRIOV PF x540_p0
Aug 30 02:15:57 ****** libvirtd[450]: internal error: No usable Vf's present on SRIOV PF i350_p1
Aug 30 02:15:57 ****** libvirtd[450]: internal error: No usable Vf's present on SRIOV PF x540_p1
Aug 30 02:15:57 ****** libvirtd[450]: internal error: No usable Vf's present on SRIOV PF i350_p0
Aug 30 02:15:57 ****** systemd[1]: Starting Record Runlevel Change in UTMP...
Aug 30 02:15:57 ****** libvirtd[450]: cannot open directory '/****/4TB/CDIMAGES': No such file or directory
Aug 30 02:15:57 ****** libvirtd[450]: internal error: Failed to autostart storage pool 'CDIMAGES': cannot open directory '/****/4TB/CDIMAGES': No such file or directory
Aug 30 02:15:58 ****** systemd[1]: Mounted /****/4TB.
Aug 30 02:15:58 ****** systemd[1]: Startup finished in 37.044s (firmware) + 6.098s (loader) + 2.776s (kernel) + 2.442s (userspace) = 48.361s.
Aug 30 02:15:58 ****** networkd-dispatcher[418]: WARNING:Unknown index 22 seen, reloading interface list