...
BugZero found this defect 410 days ago.
What were you trying to do that didn't work? Use an autostarted VM after the Leapp upgrade. Please provide the package NVR for which bug is seen: libvirt-8.0.0-23.module+el8.10.0+21023+5962ee04 leapp-upgrade-el8toel9-0.19.0-9.el8 How reproducible: 100% Steps to reproduce On a recent 8.10 installation, create a VM with an pci hostdev and attached to the default NAT network Mark the VM as autostart, reboot host and confirm it's autostarted Run the leapp upgrade Expected results After the final reboot, when I log in the VM is running Actual results The VM is not running. The log complains about connection issues with virtnetworkd-sock which is weird because 8.10 has the monolithic libvirtd daemon and should run also libvirtd monolithically on the target 9.4. After starting the virtnetworkd manually the VM can start. Additional info: it was found when upgrading 8.10->9.4; it reproduces when upgrading 8.10 -> 9.3 with libvirt-9.5.0-7.el9_3.s390x it doesn't reproduce when upgrading 8.9 -> 9.3 libvirt-8.0.0-22.module+el8.9.0+19544+b3045133, leapp-upgrade-el8toel9-0.19.0-1.el8 # systemctl status virtnetworkd ○ virtnetworkd.service - libvirt network daemon Loaded: loaded (/usr/lib/systemd/system/virtnetworkd.service; disabled; preset: disabled) Active: inactive (dead) TriggeredBy: ○ virtnetworkd-ro.socket ○ virtnetworkd-admin.socket ○ virtnetworkd.socket Docs: man:virtnetworkd(8) https://libvirt.org/ journalctl -u virtqemud: 2032]: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory 2032]: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory 2032]: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory 2032]: Unable to release network device '<null>' 2032]: internal error: Failed to autostart VM 'rhel9': Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No s> 2032]: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory 2032]: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory 2032]: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory 2032]: Unable to release network device '<null>'
Done
7.65
SELinux prevents dhcpcd from reading files stored in /run/dhcpcd-ci/ directory7.55
Kernel panic when booting with ARM 64k with image mode7.5
Please backport Fedora 40 changes in xorg-x11-server-Xwayland if needed (2025-02-23)7.5
Please backport Fedora 41 changes in gnome-online-accounts if needed (2025-02-23)7.5
Please backport Fedora 40 changes in geoclue2 if needed (2025-02-23)9.5
swtpm: Windows reports TPM error due to missing SHA1 on RHEL 9 hosts9.35
Cross migration failed9.35
[vfio migration] The Q35 + OVMF VM with a mlx5_vfio_pci VF can not be migrated9.2
System cannot boot when usr is a separate file system with latest systemd-219-78.el7_9.89.2
VM can't autostart after Leapp upgrade