[Bug 1177763] New: Cannot install an existing virtual machine two error messages with Virtual Machine Manager
https://bugzilla.suse.com/show_bug.cgi?id=1177763 Bug ID: 1177763 Summary: Cannot install an existing virtual machine two error messages with Virtual Machine Manager Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs@suse.de Reporter: peter.posts@gmx.net QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- 20201010, Tumbleweed, no additional repositories, fresh install, fresh dup Procedure (German) Hypervisor und Tools installieren KVM-Server - KVM -Werkzeuge sind installiert "Die KVM-Komponenten sind installiert. Auf dem Host können nun KVM-Gastsysteme installiert werden." Start: Virtual Machine Manager Error messages: The libvirtd service does not appear to be installed. Install and run the libvirtd service to manage virtualization on this host. Test: systemctl status libvirtd Result: lux-tw:~ # systemctl status libvirtd ● libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled) Active: inactive (dead) since Thu 2020-10-15 16:55:11 CEST; 4min 7s ago TriggeredBy: ● libvirtd.socket ● libvirtd-ro.socket ● libvirtd-admin.socket Docs: man:libvirtd(8) https://libvirt.org Process: 1258 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=0/SUCCESS) Main PID: 1258 (code=exited, status=0/SUCCESS) Okt 15 16:53:11 lux-tw systemd[1]: Starting Virtualization daemon... Okt 15 16:53:11 lux-tw libvirtd[1258]: libvirt version: 6.8.0 Okt 15 16:53:11 lux-tw libvirtd[1258]: hostname: lux-tw Okt 15 16:53:11 lux-tw libvirtd[1258]: Failed to initialize libnetcontrol. Management of interface devices is d> Okt 15 16:53:11 lux-tw systemd[1]: Started Virtualization daemon. Okt 15 16:55:11 lux-tw systemd[1]: libvirtd.service: Succeeded. Later compared installed packages to an existing and working installation on Leap 15.2. I added the missing packetes, error messages remained -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1177763
Peter McDonough
https://bugzilla.suse.com/show_bug.cgi?id=1177763
Charles Arnold
https://bugzilla.suse.com/show_bug.cgi?id=1177763
https://bugzilla.suse.com/show_bug.cgi?id=1177763#c1
James Fehlig
lux-tw:~ # systemctl status libvirtd ● libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled)
So far so good, libvirtd is enabled and started after running "Install hypervisor and tools".
Active: inactive (dead) since Thu 2020-10-15 16:55:11 CEST; 4min 7s ago
The service is currently inactive due to the '--timeout 120' option passed to libvirtd. As seen below, the service started at 16:53:11 and successfully exited at 16:55:11 (2 minutes later) after no activity.
TriggeredBy: ● libvirtd.socket ● libvirtd-ro.socket
But restarting the service should be triggered by a connection to libvirtd's unix sockets.
● libvirtd-admin.socket Docs: man:libvirtd(8) https://libvirt.org Process: 1258 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=0/SUCCESS) Main PID: 1258 (code=exited, status=0/SUCCESS)
Okt 15 16:53:11 lux-tw systemd[1]: Starting Virtualization daemon... Okt 15 16:53:11 lux-tw libvirtd[1258]: libvirt version: 6.8.0 Okt 15 16:53:11 lux-tw libvirtd[1258]: hostname: lux-tw Okt 15 16:53:11 lux-tw libvirtd[1258]: Failed to initialize libnetcontrol. Management of interface devices is d> Okt 15 16:53:11 lux-tw systemd[1]: Started Virtualization daemon. Okt 15 16:55:11 lux-tw systemd[1]: libvirtd.service: Succeeded.
Does libvirt's virsh command line tool work? E.g. 'virsh capabilities' and 'virsh list'? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1177763
https://bugzilla.suse.com/show_bug.cgi?id=1177763#c2
--- Comment #2 from Peter McDonough
https://bugzilla.suse.com/show_bug.cgi?id=1177763
https://bugzilla.suse.com/show_bug.cgi?id=1177763#c3
--- Comment #3 from James Fehlig
https://bugzilla.suse.com/show_bug.cgi?id=1177763
https://bugzilla.suse.com/show_bug.cgi?id=1177763#c4
--- Comment #4 from Peter McDonough
https://bugzilla.suse.com/show_bug.cgi?id=1177763
https://bugzilla.suse.com/show_bug.cgi?id=1177763#c5
--- Comment #5 from James Fehlig
There is no virt-manager/virt-manager.log. (!)
Odd. Try starting it manually with debug. E.g. 'virt-manger --debug'.
Yast pulls in Leap 15.2 - 26 packages in Tumbleweed only - 22 packages, check below:
I recently disabled some drivers that have limited functionality and minimal upstream development. I also dropped the hard 'Requires' on the gluster storage backend. These changes likely account for the package count difference.
lux-tw:~ # rpm -qa libvirt\* libvirt-glib-1_0-0-3.0.0-1.3.x86_64 libvirt-bash-completion-6.8.0-1.1.noarch libvirt-libs-6.8.0-1.1.x86_64 libvirt-client-6.8.0-1.1.x86_64 libvirt-daemon-6.8.0-1.1.x86_64 libvirt-daemon-driver-storage-core-6.8.0-1.1.x86_64 libvirt-daemon-driver-secret-6.8.0-1.1.x86_64 libvirt-daemon-driver-qemu-6.8.0-1.1.x86_64 libvirt-daemon-driver-nwfilter-6.8.0-1.1.x86_64 libvirt-daemon-driver-nodedev-6.8.0-1.1.x86_64 libvirt-daemon-driver-network-6.8.0-1.1.x86_64 libvirt-daemon-driver-interface-6.8.0-1.1.x86_64 libvirt-daemon-driver-storage-scsi-6.8.0-1.1.x86_64 libvirt-daemon-driver-storage-rbd-6.8.0-1.1.x86_64 libvirt-daemon-driver-storage-mpath-6.8.0-1.1.x86_64 libvirt-daemon-driver-storage-logical-6.8.0-1.1.x86_64 libvirt-daemon-driver-storage-iscsi-direct-6.8.0-1.1.x86_64 libvirt-daemon-driver-storage-iscsi-6.8.0-1.1.x86_64 libvirt-daemon-driver-storage-disk-6.8.0-1.1.x86_64 libvirt-daemon-config-network-6.8.0-1.1.x86_64 libvirt-daemon-driver-storage-6.8.0-1.1.x86_64 libvirt-daemon-qemu-6.8.0-1.1.x86_64
We already verified this set of packages gives you a working libvirt configuration, otherwise virsh would not work. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1177763
https://bugzilla.suse.com/show_bug.cgi?id=1177763#c6
--- Comment #6 from Peter McDonough
https://bugzilla.suse.com/show_bug.cgi?id=1177763
https://bugzilla.suse.com/show_bug.cgi?id=1177763#c13
--- Comment #13 from Peter McDonough
(In reply to John Doe from comment #7)
sudo systemctl status libvirtd: ... virt-manager --debug:
Ah, a small hint that virt-manager is run as a normal user. Is this the case? Same question for you Peter.
I initially saw the problem when starting virt-manager as a normal user. I tried adding a new 'qemu:///system' connection using the "Add Connection" wizard and it worked after providing root passwd. I then added a 'qemu:///session' connection and it also worked. And I no longer see the problem when restarting virt-manager. ...
Sorry, I'm late. Now I notice it, too. In Leap 15.2 the root password is requested when starting the virtual-manager, not so in Tumbleweed. So, adding a new 'qemu:///system' connection using the "Add Connection" wizard and just clicking connect (Verbinden) does it. Everything works as in Leap. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1177763
https://bugzilla.suse.com/show_bug.cgi?id=1177763#c14
--- Comment #14 from Peter McDonough
I added myself to the libvirt group to see if it would change anything but the issue remains the same.
Solution: LIBVIRT GROUP to USER Isn't it always the obvious, which is hardest to see? I didn't add the libvirt group to the user, so the user needs root for starting libvirt. Test: I reinstalled Tumbleweed from a backup, pre-libvirt status. Installed kvm+tools added libvirt group to the user Just to make sure, rebooted Tumbleweed Called up virtual-manager as user, installed and run a virtual machine. No problems at all, apart from the missing KVM Default Network, which needed. sudo virsh net-start default sudo virsh net-autostart --network default Peter -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1177763
https://bugzilla.suse.com/show_bug.cgi?id=1177763#c15
James Fehlig
(In reply to John Doe from comment #9)
I added myself to the libvirt group to see if it would change anything but the issue remains the same.
Solution: LIBVIRT GROUP to USER
There is no need to add your user to the libvirt group unless you set auth_unix_{ro,rw} to 'none' in /etc/libvirt/libvirtd.conf. On SUSE distros libvirtd uses polkit auth by default. Socket permissions on the read-only and read-write sockets are set to 06660, allowing anyone to connect, but they are subjected to polkit auth. The default polkit privileges allow any user to connect to read-only socket, but only root to the read-write socket. virt-manager connects to the read-write socket, so you should be prompted for root passwd if running it as a normal user. If auth on libvirtd's read-only or read-write sockets is set to 'none', then standard unix socket permissions and group membership checks apply. BTW, I'm clearing your needinfo since AFAIK we no longer need info from you :-). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1177763
https://bugzilla.suse.com/show_bug.cgi?id=1177763#c16
Charles Arnold
https://bugzilla.suse.com/show_bug.cgi?id=1177763
https://bugzilla.suse.com/show_bug.cgi?id=1177763#c17
--- Comment #17 from John Doe
The virt-manager fix for this is now in Factory. It should show up soon in Tumbleweed (maybe already there?).
Seems to work fine on tw now for me at least :) -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com