-1

KVM isn't starting and when i look at the status of the libvirt services every thing but libvirtd-tcp.socket and libvirtd-tls.socket is running and when i use systemctl start on them it says "Job failed. See "journalctl -xe" for details" but i can't see what the problem is. Or at least how i can fix it.

i have tried restarting libvirt-tls.socket and libvirt-tcp.socket. the result of journalctl -xe what i have tried

--update i have now tryed to restart all of the libvirtd services and it said job failed twice and this is the out put of journalctl -xe


zach@latitude:~$ journalctl -xe
░░ 
░░ The job identifier is 6642.
Aug 25 16:28:21 latitude sudo[11254]: pam_unix(sudo:session): session closed for user root
Aug 25 16:28:22 latitude dnsmasq[1277]: read /etc/hosts - 7 addresses
Aug 25 16:28:22 latitude dnsmasq[1277]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Aug 25 16:28:22 latitude dnsmasq-dhcp[1277]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Aug 25 16:28:22 latitude libvirtd[11259]: libvirt version: 8.0.0, package: 1ubuntu7.6 (Rafael Lopez <rafael.lopez@canonical.com> Tue, 20 Jun 2023 11:54:15 +1000)
Aug 25 16:28:22 latitude libvirtd[11259]: hostname: latitude
Aug 25 16:28:22 latitude libvirtd[11259]: Unable to open /dev/kvm: No such file or directory
Aug 25 16:28:22 latitude libvirtd[11259]: Unable to open /dev/kvm: No such file or directory
Aug 25 16:28:22 latitude NetworkManager[873]: <info>  [1692998902.8233] dhcp6 (eno1): activation: beginning transaction (timeout in 45 seconds)
Aug 25 16:28:22 latitude NetworkManager[873]: <info>  [1692998902.8249] dhcp6 (eno1): state changed new lease
Aug 25 16:28:22 latitude dbus-daemon[872]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' (uid=0 pid=873 comm="/usr/sbin/NetworkManag>
Aug 25 16:28:22 latitude systemd[1]: Starting Network Manager Script Dispatcher Service...
░░ Subject: A start job for unit NetworkManager-dispatcher.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit NetworkManager-dispatcher.service has begun execution.
░░ 
░░ The job identifier is 6733.
Aug 25 16:28:22 latitude dbus-daemon[872]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug 25 16:28:22 latitude systemd[1]: Started Network Manager Script Dispatcher Service.
░░ Subject: A start job for unit NetworkManager-dispatcher.service has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit NetworkManager-dispatcher.service has finished successfully.
░░ 
░░ The job identifier is 6733.
Aug 25 16:28:23 latitude kernel: [drm] PCIE gen 3 link speeds already enabled
Aug 25 16:28:23 latitude kernel: [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000).
Aug 25 16:28:23 latitude kernel: radeon 0000:01:00.0: WB enabled
Aug 25 16:28:23 latitude kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00
Aug 25 16:28:23 latitude kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04
Aug 25 16:28:23 latitude kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08
Aug 25 16:28:23 latitude kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c
Aug 25 16:28:23 latitude kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10
Aug 25 16:28:23 latitude kernel: debugfs: File 'radeon_ring_gfx' in directory '0' already present!
Aug 25 16:28:23 latitude kernel: debugfs: File 'radeon_ring_cp1' in directory '0' already present!
Aug 25 16:28:23 latitude kernel: debugfs: File 'radeon_ring_cp2' in directory '0' already present!
Aug 25 16:28:23 latitude kernel: debugfs: File 'radeon_ring_dma1' in directory '0' already present!
Aug 25 16:28:23 latitude kernel: debugfs: File 'radeon_ring_dma2' in directory '0' already present!
Aug 25 16:28:23 latitude kernel: [drm] ring test on 0 succeeded in 1 usecs
Aug 25 16:28:23 latitude kernel: [drm] ring test on 1 succeeded in 0 usecs
Aug 25 16:28:23 latitude kernel: [drm] ring test on 2 succeeded in 1 usecs
Aug 25 16:28:23 latitude kernel: [drm] ring test on 3 succeeded in 4 usecs
Aug 25 16:28:23 latitude kernel: [drm] ring test on 4 succeeded in 3 usecs
Aug 25 16:28:23 latitude kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Aug 25 16:28:23 latitude kernel: [drm] ib test on ring 1 succeeded in 0 usecs
Aug 25 16:28:23 latitude kernel: [drm] ib test on ring 2 succeeded in 0 usecs
Aug 25 16:28:23 latitude kernel: [drm] ib test on ring 3 succeeded in 0 usecs
Aug 25 16:28:23 latitude kernel: [drm] ib test on ring 4 succeeded in 0 usecs
  • `/dev/kvm` existing is pretty straightforward. Did you _try_ to load the relevant kernel modules(s)? What errors did you get in dmesg when you tried? (Not saying you should answer that here, but include the information if you re-ask the question somewhere it's on-topic). – Charles Duffy Aug 25 '23 at 22:05

0 Answers0