Public bug reported:

After upgrading from 22.04 to 24.04, a VM set to autostart is no longer
starting.

service status indicates the problem is /dev/dri not existing.


tim@black:~$ systemctl status libvirtd
○ libvirtd.service - libvirt legacy monolithic daemon
     Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: 
enabled)
    Drop-In: /etc/systemd/system/libvirtd.service.d
             └─override.conf
     Active: inactive (dead) since Thu 2024-07-18 13:36:29 AEST; 5min ago
   Duration: 2min 50.748s
TriggeredBy: ● libvirtd-ro.socket
             ● libvirtd-admin.socket
             ● libvirtd.socket
       Docs: man:libvirtd(8)
             https://libvirt.org/
    Process: 5454 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, 
status=0/SUCCESS)
   Main PID: 5454 (code=exited, status=0/SUCCESS)
      Tasks: 2 (limit: 32768)
     Memory: 24.3M (peak: 37.1M)
        CPU: 369ms
     CGroup: /system.slice/libvirtd.service
             ├─5820 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
             └─5821 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper

Jul 18 13:33:38 black libvirtd[5454]: hostname: black
Jul 18 13:33:38 black libvirtd[5454]: cannot open directory '/dev/dri': No such 
file or directory
Jul 18 13:33:38 black libvirtd[5454]: internal error: Failed to autostart VM 
'ubuntu24.04': cannot open directory '/dev/dri': No such file or directory
Jul 18 13:33:44 black dnsmasq[5820]: reading /etc/resolv.conf
Jul 18 13:33:44 black dnsmasq[5820]: using nameserver 127.0.0.53#53
Jul 18 13:33:44 black dnsmasq[5820]: reading /etc/resolv.conf
Jul 18 13:33:44 black dnsmasq[5820]: using nameserver 127.0.0.53#53
Jul 18 13:36:29 black systemd[1]: libvirtd.service: Deactivated successfully.
Jul 18 13:36:29 black systemd[1]: libvirtd.service: Unit process 5820 (dnsmasq) 
remains running after unit stopped.
Jul 18 13:36:29 black systemd[1]: libvirtd.service: Unit process 5821 (dnsmasq) 
remains running after unit stopped.


This override fixes it:

/etc/systemd/system/libvirtd.service.d/override.conf


[Unit]
After=multi-user.target dev-dri.device

[Service]
ExecStartPre=/bin/sleep 10

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: libvirt-daemon-system 10.0.0-2ubuntu8.2
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 18 13:41:03 2024
InstallationDate: Installed on 2023-08-10 (343 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
SourcePackage: libvirt
UpgradeStatus: Upgraded to noble on 2024-07-16 (2 days ago)
modified.conffile..etc.apparmor.d.abstractions.libvirt-qemu: [modified]
modified.conffile..etc.apparmor.d.usr.lib.libvirt.virt-aa-helper: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.libvirtd: [modified]
modified.conffile..etc.init.d.apport: [modified]
modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/libvirt/qemu.conf']
mtime.conffile..etc.apparmor.d.abstractions.libvirt-qemu: 
2024-07-16T10:47:15.550409
mtime.conffile..etc.apparmor.d.usr.lib.libvirt.virt-aa-helper: 
2024-07-16T14:54:43.518479
mtime.conffile..etc.apparmor.d.usr.sbin.libvirtd: 2024-07-16T14:53:58.911077
mtime.conffile..etc.init.d.apport: 2024-04-23T21:30:10

** Affects: libvirt (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug noble wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073442

Title:
  Failed to autostart VM: cannot open directory '/dev/dri': No such file
  or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2073442/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to