Description of problem: virt-manager create new VM, "No virtual networks available" and no NAT in the pop-up as expected. Version-Release number of selected component (if applicable): virt-manager-1.6.0-1.3.git3bc7ff24c.fc29.noarch virt-manager-common-1.6.0-1.3.git3bc7ff24c.fc29.noarch [chris@flap ~]$ rpm -qa | grep qemu qemu-block-iscsi-3.0.0-1.fc29.x86_64 qemu-kvm-3.0.0-1.fc29.x86_64 qemu-block-ssh-3.0.0-1.fc29.x86_64 qemu-audio-pa-3.0.0-1.fc29.x86_64 qemu-block-rbd-3.0.0-1.fc29.x86_64 qemu-ui-curses-3.0.0-1.fc29.x86_64 qemu-system-x86-3.0.0-1.fc29.x86_64 qemu-block-curl-3.0.0-1.fc29.x86_64 qemu-common-3.0.0-1.fc29.x86_64 qemu-audio-alsa-3.0.0-1.fc29.x86_64 qemu-audio-oss-3.0.0-1.fc29.x86_64 qemu-system-x86-core-3.0.0-1.fc29.x86_64 qemu-guest-agent-3.0.0-1.fc29.x86_64 qemu-block-nfs-3.0.0-1.fc29.x86_64 qemu-block-gluster-3.0.0-1.fc29.x86_64 qemu-ui-gtk-3.0.0-1.fc29.x86_64 qemu-img-3.0.0-1.fc29.x86_64 qemu-ui-sdl-3.0.0-1.fc29.x86_64 qemu-block-dmg-3.0.0-1.fc29.x86_64 libvirt-daemon-driver-qemu-4.7.0-1.fc29.x86_64 ipxe-roms-qemu-20170710-5.git0600d3ae.fc29.noarch qemu-audio-sdl-3.0.0-1.fc29.x86_64 [chris@flap ~]$ rpm -qa | grep libvirt libvirt-daemon-driver-storage-iscsi-4.7.0-1.fc29.x86_64 libvirt-glib-1.0.0-7.fc29.x86_64 libvirt-daemon-driver-storage-iscsi-direct-4.7.0-1.fc29.x86_64 libvirt-gobject-1.0.0-7.fc29.x86_64 libvirt-daemon-driver-vbox-4.7.0-1.fc29.x86_64 libvirt-libs-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-libxl-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-secret-4.7.0-1.fc29.x86_64 python2-libvirt-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-storage-scsi-4.7.0-1.fc29.x86_64 libvirt-gconfig-1.0.0-7.fc29.x86_64 libvirt-daemon-driver-storage-zfs-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-storage-sheepdog-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-storage-gluster-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-storage-core-4.7.0-1.fc29.x86_64 libvirt-bash-completion-4.7.0-1.fc29.x86_64 libvirt-daemon-config-nwfilter-4.7.0-1.fc29.x86_64 libvirt-daemon-config-network-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-storage-4.7.0-1.fc29.x86_64 libvirt-client-4.7.0-1.fc29.x86_64 libvirt-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-storage-disk-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-storage-mpath-4.7.0-1.fc29.x86_64 libvirt-daemon-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-uml-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-interface-4.7.0-1.fc29.x86_64 python3-libvirt-4.7.0-1.fc29.x86_64 libvirt-daemon-kvm-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-qemu-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-storage-logical-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-nodedev-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-nwfilter-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-network-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-storage-rbd-4.7.0-1.fc29.x86_64 libvirt-daemon-driver-lxc-4.7.0-1.fc29.x86_64 How reproducible: Always Steps to Reproduce: 1. Fedora 28 host where this was working as expected; and then dnf system upgrade to Fedora 29 and now no network 2. Create a new VM, and pointing to a Fedora 28 Workstation ISO as the installation source 3. Actual results: No virtual networks available Expected results: NAT should be the default Additional info:
Looks like bug 1224398 except neither a reboot, nor restarting libvirtd works.
Created attachment 1493555 [details] journalctl log
I can confirm that cleanly installed Fedora 29 provides a working networking for both the host and the guest OS in a VM. I have tested this particular case yesterday. Today, I have tested according to your description and I did the following: * I cleanly installed Fedora 28 and virt-manager. * I set up a VM with Fedora 29 Live Iso and ran it inside -> both the host and the VM had working networking. * I updated Fedora 28 and the situation was the same, networking was fine. * I upgraded system to Fedora 29 and tried again -> both the host and the VM had fully working networking. I could not reproduce this bug.
Per Comment #3 I'm closing. libvirt-daemon-config-network is the thing that provides the 'default' network, not sure what wrong in the stock case.