Open tuxpeople opened 3 years ago
You need to check in libvirtd logs, for systemd e.g.: journalctl -u libvirtd -n 1000 -f
. Maybe the bridge bridge99
tied to the physical NIC didn't exist yet, then it fails to setup the network.
Same issue here since I update to Fedora 34.
For me journalctl -u libvirtd -n 1000 -f
give the following:
-- Boot 96183c7b2a98412ab4c228b37c9658e2 --
juin 23 09:20:38 fedora systemd[1]: Starting Virtualization daemon...
juin 23 09:20:38 fedora systemd[1]: Started Virtualization daemon.
juin 23 09:20:38 fedora libvirtd[1256]: libcap-ng used by "/usr/sbin/libvirtd" failed due to not having CAP_SETPCAP in capng_apply
juin 23 09:20:38 fedora libvirtd[1258]: libcap-ng used by "/usr/sbin/libvirtd" failed due to not having CAP_SETPCAP in capng_apply
juin 23 09:22:38 fedora systemd[1]: libvirtd.service: Deactivated successfully.
I find these two upstream bugs report: https://bugzilla.redhat.com/show_bug.cgi?id=1924218 https://bugzilla.redhat.com/show_bug.cgi?id=1952715#c4
Didn't find a workaround for now.
This is what I try:
Even with -v, not that much of information. Let's try it manually by copying the command from above:
Is it me, using it wrong or is it a bug?