Package: libvirt-daemon Version: 8.9.0-1 Severity: important X-Debbugs-Cc: havis...@azet.sk
Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I am running debian testing (bookworm) amd64 I updated my system (apt full-upgrade) and after reboot VMs were not starting (virt-manager became unusable) running: virsh -c qemu:///system Error registering authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of subject (polkit-error-quark, 0) error: failed to connect to the hypervisor error: error from service: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code4: Failed to open file “/proc/3755/status”: No such file or directory running virt-manager results in virt manager saying that it is not connected: QEMU/KVM - Not Connected, after clicking on it I get this error: Unable to connect to libvirt qemu:///system. error from service: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code4: Failed to open file “/proc/5038/status”: No such file or directory process 5038 is virt-manager and file /proc/5038/status do exist on my system *pid will of course change if I restart virt-manager * What exactly did you do (or not do) that was effective (or ineffective)? Not sure if this is actually libvirt-daemon bug. This can also be polkit or dbus bug, but all apps and my kde-plasma- desktop is running without any issues. I just can't start any Virtual Machines. * What was the outcome of this action? * What outcome did you expect instead? -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-4-amd64 (SMP w/32 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US 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 libacl1 2.3.1-1 ii libblkid1 2.38.1-3 ii libc6 2.36-5 ii libdevmapper1.02.1 2:1.02.185-2 ii libgcc-s1 12.2.0-9 ii libglib2.0-0 2.74.1-2 ii libparted2 3.5-3 ii libpcap0.8 1.10.1-4 ii libpciaccess0 0.17-2 ii libselinux1 3.4-1+b3 ii libtirpc3 1.3.3+ds-1 ii libudev1 252.1-1 ii libvirt-daemon-driver-qemu 8.9.0-1 ii libvirt0 8.9.0-1 ii libxml2 2.9.14+dfsg-1.1+b2 Versions of packages libvirt-daemon recommends: ii libvirt-daemon-driver-lxc 8.9.0-1 ii libvirt-daemon-driver-vbox 8.9.0-1 ii libvirt-daemon-driver-xen 8.9.0-1 ii libxml2-utils 2.9.14+dfsg-1.1+b2 ii lvm2 2.03.16-2 ii mount 2.38.1-3 ii netcat-openbsd 1.219-1 ii qemu-system-x86 [qemu-kvm] 1:7.1+dfsg-2 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.9.0-1 pn numad <none> -- debconf-show failed