[Bug 778006] New: virt-manager unable to connect to libvirt after update
https://bugzilla.novell.com/show_bug.cgi?id=778006 https://bugzilla.novell.com/show_bug.cgi?id=778006#c0 Summary: virt-manager unable to connect to libvirt after update Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: jdouglas@suse.com ReportedBy: ralf@bj-ig.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/536.25 (KHTML, like Gecko) Version/6.0 Safari/536.25 I'm running a Xen-Server using the OpenSuSE Tumbleweed repository. After I updated this system the day before (zypper dup --from Tumbleweed; zypper up; reboot) virt-manager is not able to connect to libvirt anymore. All domU's are up and running, "xm list" shows them correctly, but virt-manager reports the following after start: Unable to connect to libvirt. internal error libxenlight state driver is not active Verify that: - A Xen host kernel was booted - The Xen service has been started Details Unable to connect to libvirt. internal error libxenlight state driver is not active Verify that: - A Xen host kernel was booted - The Xen service has been started Libvirt URI is: xen:/// Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 1027, in _open_thread self.vmm = self._try_open() File "/usr/share/virt-manager/virtManager/connection.py", line 1009, in _try_open flags) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 102, in openAuth if ret is None:raise libvirtError('virConnectOpenAuth() failed') libvirtError: internal error libxenlight state driver is not active rclibvirtd status reports: libvirtd.service - Virtualization daemon Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled) Active: active (running) since Tue, 28 Aug 2012 09:19:18 +0200; 33min ago Main PID: 11360 (libvirtd) CGroup: name=systemd:/system/libvirtd.service └ 11360 /usr/sbin/libvirtd --listen # uname -a Linux tower-core 3.5.2-39-xen #1 SMP Wed Aug 15 21:49:59 UTC 2012 (4904750) x86_64 x86_64 x86_64 GNU/Linux # rpm -q xen xen-4.1.2_17-1.10.1.x86_64 # virsh version WARNING: gnome-keyring:: no socket to connect to Compiled against library: libvir 0.9.13 Using library: libvir 0.9.13 Using API: QEMU 0.9.13 error: failed to get the hypervisor version error: internal error Cannot find suitable emulator for x86_64 # virsh list --all WARNING: gnome-keyring:: no socket to connect to Id Name State ---------------------------------------------------- Reproducible: Always Steps to Reproduce: 1. Update a xen server using Tumbleweed -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=778006 https://bugzilla.novell.com/show_bug.cgi?id=778006#c James Fehlig <jfehlig@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jfehlig@suse.com AssignedTo|jdouglas@suse.com |jfehlig@suse.com QAContact|qa-bugs@suse.de |jdouglas@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=778006 https://bugzilla.novell.com/show_bug.cgi?id=778006#c1 James Fehlig <jfehlig@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |ralf@bj-ig.de --- Comment #1 from James Fehlig <jfehlig@suse.com> 2012-08-31 03:48:46 UTC --- Got to the bottom of this and have a patch committed upstream http://libvirt.org/git/?p=libvirt.git;a=commit;h=f781e27653c7e50747c414a916c... I've backported it to 0.9.13 and submitted to the Virtualization project. Can you give it a try. Looks good in my testing. Thanks. http://download.opensuse.org/repositories/Virtualization/openSUSE_12.2/x86_6... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=778006 https://bugzilla.novell.com/show_bug.cgi?id=778006#c2 --- Comment #2 from Ralf Müller <ralf@bj-ig.de> 2012-08-31 07:04:22 UTC --- Beside the problem: # zypper up libvirt-0.9.13-224.1.x86_64 Problem: nothing provides libc.so.6(GLIBC_2.15)(64bit) needed by libvirt-0.9.13-224.1.x86_64 Solution 1: do not install libvirt-0.9.13-224.1.x86_64 Solution 2: break libvirt-0.9.13-224.1.x86_64 by ignoring some of its dependencies where I choose 2. I now get: # virsh list WARNING: gnome-keyring:: no socket to connect to Id Name State ---------------------------------------------------- 0 Domain-0 running 2 domU1 idle ... and virt-manager is up and running. So I would say: problem found. Great job. Are you able to push this update to the tumbleweed repository? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=778006 https://bugzilla.novell.com/show_bug.cgi?id=778006#c3 --- Comment #3 from Andres Nogueiras Melendez <aaugusto@uvigo.es> 2012-08-31 10:07:09 UTC --- Created an attachment (id=504183) --> (http://bugzilla.novell.com/attachment.cgi?id=504183) All the steps to show diagnostic of bug reproduced, then libvirt updated and a few steps to see everything is OK -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=778006 https://bugzilla.novell.com/show_bug.cgi?id=778006#c4 Andres Nogueiras Melendez <aaugusto@uvigo.es> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aaugusto@uvigo.es --- Comment #4 from Andres Nogueiras Melendez <aaugusto@uvigo.es> 2012-08-31 10:08:15 UTC --- The new version of libvirt (224.1) is fine. Many thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=778006 https://bugzilla.novell.com/show_bug.cgi?id=778006#c5 James Fehlig <jfehlig@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED CC| |carnold@suse.com InfoProvider|ralf@bj-ig.de | Resolution| |FIXED --- Comment #5 from James Fehlig <jfehlig@suse.com> 2012-08-31 14:54:40 UTC --- New package containing the fix submitted to Factory, SR#132204.
Are you able to push this update to the tumbleweed repository?
I'm not sure how tumbleweed is pieced together, but assume submitting to Factory is enough to have it show up there eventually. I've never explicitly submitted to tumbleweed in the past. Thanks again for testing and reporting the problem! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=778006 https://bugzilla.novell.com/show_bug.cgi?id=778006#c6 --- Comment #6 from Bernhard Wiedemann <bwiedemann@suse.com> 2012-08-31 17:00:09 CEST --- This is an autogenerated message for OBS integration: This bug (778006) was mentioned in https://build.opensuse.org/request/show/132204 Factory / libvirt -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=778006 https://bugzilla.novell.com/show_bug.cgi?id=778006#c7 --- Comment #7 from Ralf Müller <ralf@bj-ig.de> 2012-08-31 15:22:06 UTC --- (In reply to comment #5)
Are you able to push this update to the tumbleweed repository?
I'm not sure how tumbleweed is pieced together, but assume submitting to Factory is enough to have it show up there eventually. I've never explicitly submitted to tumbleweed in the past.
Can you please actively check that back? As far as I know factory is your development repository for the next release. Last time I reported a bug it took literally month and intense communication from solution to an actual update packet in a production repository. Don't know if Suse has modified the procedure since that, but it would be nice to not need to reference bleeding edge repositories from production servers ;)
Thanks again for testing and reporting the problem!
Has been a pleasure. Less then 48 hours from reporting to solution - great! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=778006 https://bugzilla.novell.com/show_bug.cgi?id=778006#c8 --- Comment #8 from James Fehlig <jfehlig@suse.com> 2012-09-05 02:57:16 UTC --- (In reply to comment #7)
Can you please actively check that back? As far as I know factory is your development repository for the next release. Last time I reported a bug it took literally month and intense communication from solution to an actual update packet in a production repository.
Well, there seems to be some automated way packages are pulled from Factory for tumbleweed. I just noticed the libvirt tumbleweed package was updated by gregkh 1 day ago :). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=778006 https://bugzilla.novell.com/show_bug.cgi?id=778006#c9 --- Comment #9 from Ralf Müller <ralf@bj-ig.de> 2012-09-05 06:33:09 UTC --- (In reply to comment #8)
Well, there seems to be some automated way packages are pulled from Factory for tumbleweed. I just noticed the libvirt tumbleweed package was updated by gregkh 1 day ago :).
That sounds promising - thank you very much. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com