Your message dated Fri, 25 Nov 2022 14:41:56 +0100
with message-id <y4dgjibvcykeh...@qwark.sigxcpu.org>
and subject line Re: Bug#1011518: libvirt-daemon: libvirtd does not load the
KVM module automatically
has caused the Debian Bug report #1011518,
regarding libvirt-daemon: libvirtd does not load the KVM module automatically
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1011518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvirt-daemon
Version: 8.3.0-1
Severity: important
X-Debbugs-Cc: chandru...@gmail.com
Dear Maintainer,
libvirtd used to load the appropriate kvm module automatically on
startup, but appears to have stopped doing so with the latest update. I
see the following lines in the output of sudo systemctl status libvirtd.
libvirtd[1122]: Unable to open /dev/kvm: No such file or directory
libvirtd[1122]: internal error: failed to query mdevs from mdevctl: Error: No
such file or directory (os error 2)
I have verified that virtualization is enabled in firmware settings.
Restarting libvirtd after loading the kvm-amd module using modprobe
resolved the issue.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.17.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libvirt-daemon depends on:
ii libblkid1 2.38-4
ii libc6 2.33-7
ii libdevmapper1.02.1 2:1.02.175-2.1
ii libgcc-s1 12.1.0-2
ii libglib2.0-0 2.72.1-1
ii libparted2 3.5-1
ii libpcap0.8 1.10.1-4
ii libpciaccess0 0.16-3
ii libselinux1 3.3-1+b2
ii libtirpc3 1.3.2-2
ii libudev1 251-2
ii libvirt-daemon-driver-qemu 8.3.0-1
ii libvirt0 8.3.0-1
ii libxml2 2.9.14+dfsg-1
Versions of packages libvirt-daemon recommends:
ii libvirt-daemon-driver-lxc 8.3.0-1
ii libvirt-daemon-driver-vbox 8.3.0-1
ii libvirt-daemon-driver-xen 8.3.0-1
ii libxml2-utils 2.9.14+dfsg-1
ii lvm2 2.03.11-2.1
ii netcat-openbsd 1.218-5
ii qemu-system-x86 [qemu-kvm] 1:7.0+dfsg-7
Versions of packages libvirt-daemon suggests:
pn libvirt-daemon-driver-storage-gluster <none>
pn libvirt-daemon-driver-storage-iscsi-direct <none>
pn libvirt-daemon-driver-storage-rbd <none>
pn libvirt-daemon-driver-storage-zfs <none>
ii libvirt-daemon-system 8.3.0-1
pn numad <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: libvirt/8.5.0-1
Hi Chandra,
On Sun, Jul 24, 2022 at 08:10:35AM +0530, Chandra Sekar Srinivasan wrote:
> The bug appears to be resolved in 8.5.0-1. The kvm_amd module is now loaded
> on boot without requiring additional configuration.
Marking as fixed then.
Thanks,
-- Guido
--- End Message ---
