When I try to start a VM using virt-manager, a popup appears reporting this message:
Reporting the message in text format:
Traceback (most recent call last):
File “/usr/share/virt-manager/virtManager/asyncjob.py”, line 65, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File “/usr/share/virt-manager/virtManager/asyncjob.py”, line 101, in tmpcb
callback(*args, **kwargs)
File “/usr/share/virt-manager/virtManager/object/libvirtobject.py”, line 57, in newfn
ret = fn(self, *args, **kwargs)
File “/usr/share/virt-manager/virtManager/object/domain.py”, line 1329, in startup
self._backend.create()
File “/usr/lib64/python3.10/site-packages/libvirt.py”, line 1353, in create
raise libvirtError(‘virDomainCreate() failed’)
libvirt.libvirtError: L’operazione richiesta non è valida: network ‘default’ is not active
If I start the default network manually, a message reports me that I don’t have enough permissions:
In the details:
Errore nell’avvio della rete ‘default’: internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper) unexpected exit status 5:
dnsmasq: failed to create inotify for /etc/resolv.conf: Permission denied
Traceback (most recent call last):
File “/usr/share/virt-manager/virtManager/asyncjob.py”, line 65, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File “/usr/share/virt-manager/virtManager/asyncjob.py”, line 101, in tmpcb
callback(*args, **kwargs)
File “/usr/share/virt-manager/virtManager/object/libvirtobject.py”, line 57, in newfn
ret = fn(self, *args, **kwargs)
File “/usr/share/virt-manager/virtManager/object/network.py”, line 69, in start
self._backend.create()
File “/usr/lib64/python3.10/site-packages/libvirt.py”, line 3463, in create
raise libvirtError(‘virNetworkCreate() failed’)
libvirt.libvirtError: internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper) unexpected exit status 5:
dnsmasq: failed to create inotify for /etc/resolv.conf: Permission denied
All of this happened after upgrading my operating system. (Booting with the previous deployment everything just works as usual). This is the result of the command rpm-ostree db diff:
rpm-ostree db diff
ostree diff commit from: rollback deployment (c635af84bde19820de27b060e94cf0288e0bf7eb794d7d736cbd1ac399d07c6d)
ostree diff commit to: booted deployment (c5192648715a881dacddf704a0083834a001a3649943e0e2db76edb13f532500)
Upgraded:
libdnf 0.66.0-1.fc35 → 0.67.0-2.fc35
libicu 69.1-2.fc35 → 69.1-6.fc35
librepo 1.14.2-1.fc35 → 1.14.3-1.fc35
rpm-ostree 2022.8-1.fc35 → 2022.9-1.fc35
rpm-ostree-libs 2022.8-1.fc35 → 2022.9-1.fc35
systemd 249.11-2.fc35 → 249.12-3.fc35
systemd-container 249.11-2.fc35 → 249.12-3.fc35
systemd-libs 249.11-2.fc35 → 249.12-3.fc35
systemd-networkd 249.11-2.fc35 → 249.12-3.fc35
systemd-oomd-defaults 249.11-2.fc35 → 249.12-3.fc35
systemd-pam 249.11-2.fc35 → 249.12-3.fc35
systemd-resolved 249.11-2.fc35 → 249.12-3.fc35
systemd-udev 249.11-2.fc35 → 249.12-3.fc35
So there might be something with systemd that perhaps is not working as expected? Or is just a virt manager problem?