Your message dated Mon, 15 Feb 2021 09:22:19 +0100 with message-id <[email protected]> and subject line Re: [Pkg-libvirt-maintainers] Bug#982822: Resolution has caused the Debian Bug report #982822, regarding virt-manager: Documentation in /usr/share/doc/virt-manager is outdated 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 [email protected] immediately.) -- 982822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982822 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: virt-manager Version: 1:3.2.0-3 Severity: important Dear Maintainer, after upgrading to bullseye, I lost my virtual machines in virt-manager. virt-manager tells me QEMU/KVM - Not Connected on debug output I get rd@h370:~$ virt-manager --debug [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (cli:204) Launched with command line: /usr/bin/virt-manager --debug [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (virtmanager:163) virt-manager version: 3.2.0 [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (virtmanager:164) virtManager import: /usr/share/virt-manager/virtManager [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (virtmanager:201) PyGObject version: 3.38.0 [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (virtmanager:205) GTK version: 3.24.24 [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (systray:77) Using AppIndicator3 for systray [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (systray:463) Showing systray: False [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (inspection:206) python guestfs is not installed [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (engine:113) Loading stored URIs: qemu:///system [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (engine:461) processing cli command uri= show_window=manager domain= [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (engine:464) No cli action requested, launching default window [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (manager:185) Showing manager [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (engine:316) window counter incremented to 1 [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (engine:211) Initial gtkapplication activated [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (connection:482) conn=qemu:///system changed to state=Verbinden [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (connection:902) Scheduling background open thread for qemu:///system [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (connection:837) conn.close() uri=qemu:///system [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (connection:482) conn=qemu:///system changed to state=Getrennt [Sun, 14 Feb 2021 22:21:42 virt-manager 16789] DEBUG (engine:179) Autostart connection error: Unable to connect to libvirt qemu:///system. Stellen Sie sicher, dass der »libvirtd«-Dienst läuft. Libvirt URI is: qemu:///system Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 922, in _do_open self._backend.open(cb, data) File "/usr/share/virt-manager/virtinst/connection.py", line 153, in open conn = libvirt.openAuth(self._open_uri, File "/usr/lib/python3/dist-packages/libvirt.py", line 104, in openAuth if ret is None:raise libvirtError('virConnectOpenAuth() failed') libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory I found many reports that permission issues can cause this, e.g. https://kifarunix.com/how-to-fix-qemu-kvm-not-connected-error-on-ubuntu-20-04/ I then checked /usr/share/doc/virt-manager/README.Debian and found that this is outdated root@h370:~# grep libvirt /usr/share/doc/virt-manager/README.Debian Access to the libvirt socket is controlled by membership in the "libvirt" See also /usr/share/doc/libvirt-daemon-system/README.Debian.gz. root@h370:~# zgrep libvirt /usr/share/doc/libvirt-daemon-system/README.Debian.gz gzip: /usr/share/doc/libvirt-daemon-system/README.Debian.gz: No such file or directory root@h370:~# addgroup rd libvirt addgroup: The group `libvirt' does not exist. root@h370:~# Neither the group `libvirt' exists nor the referenced README.Debian '/usr/share/doc/libvirt-daemon-system/README.Debian.gz' I rated the report as important, since /usr/share/doc/virt-manager/README.Debian is probably read by many new virt-manager users in bullseye. Thanks Rainer -- System Information: Debian Release: bullseye/sid APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'testing'), (105, 'proposed-updates'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/6 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de:en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages virt-manager depends on: ii dconf-gsettings-backend [gsettings-backend] 0.38.0-2 ii gir1.2-gtk-3.0 3.24.24-1 ii gir1.2-gtk-vnc-2.0 1.0.0-1 ii gir1.2-gtksource-4 4.8.0-1 ii gir1.2-libosinfo-1.0 1.8.0-1 ii gir1.2-libvirt-glib-1.0 3.0.0-1 ii gir1.2-vte-2.91 0.62.2-1 ii python3 3.9.1-1 ii python3-dbus 1.2.16-5 ii python3-gi 3.38.0-2 ii python3-gi-cairo 3.38.0-2 ii python3-libvirt 6.1.0-1+b3 ii virtinst 1:3.2.0-3 Versions of packages virt-manager recommends: ii gir1.2-appindicator3-0.1 0.4.92-8 ii gir1.2-spiceclientglib-2.0 0.39-1 ii gir1.2-spiceclientgtk-3.0 0.39-1 pn libvirt-daemon-system <none> Versions of packages virt-manager suggests: ii gir1.2-secret-1 0.20.4-2 pn gnome-keyring <none> ii ksshaskpass [ssh-askpass] 4:5.20.5-1 pn python3-guestfs <none> ii virt-viewer 7.0-2 Versions of packages virt-manager is related to: ii libvirt-clients 7.0.0-1 ii libvirt-daemon 7.0.0-1 ii libvirt0 7.0.0-1 ii osinfo-db 0.20210202-1 -- no debconf information
--- End Message ---
--- Begin Message ---Hi Rainer, On Sun, Feb 14, 2021 at 11:53:49PM +0100, Rainer Dorsch wrote: > It seems the main issue was that libvirt-daemon-system was not installed > after > the update. Found that by searching for /etc/libvirt/qemu.conf > > In addition I had to put the default network to active: > > rd@h370:~$ apt-file search qemu.conf > libvirt-daemon-system: /etc/libvirt/qemu.conf > rd@h370:~$ > > root@h370:~# apt-get install libvirt-daemon-system > [...] > root@h370:~# addgroup rd libvirt > Füge Benutzer »rd« der Gruppe »libvirt« hinzu ... > Benutzer rd wird zur Gruppe libvirt hinzugefügt. > Fertig. > root@h370:~# virsh net-list --all > Name Status Automatischer Start Bleibend > ----------------------------------------------------- > default Inaktiv nein ja > > root@h370:~# virsh net-start default > Netzwerk default gestartet > > root@h370:~# virsh net-list --all > Name Status Automatischer Start Bleibend > ---------------------------------------------------- > default Aktiv nein ja > root@h370:~# > > https://askubuntu.com/questions/1036297/cant-start-kvm-guest-network-default-is-not-active > > I think the core of the issue is rather why libvirt-daemon-system was > installed after the upgrade, the documentation seems to be ok for me. Even > from having not found /usr/share/doc/libvirt-daemon-system/README.Debian.gz I > could have concluded that libvirt-daemon-system is missing, but I concluded > wrongly that the package was renamed. See the NEWS.Debian on the package layout for bullseye. If you feel there's something significant missing it's best to propose an MR on salsa. Cheers, -- Guido > > Thanks > Rainer > > > -- > Rainer Dorsch > http://bokomoko.de/ > > _______________________________________________ > Pkg-libvirt-maintainers mailing list > [email protected] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers
--- End Message ---
