Discussion:
virt-manager unable to connect to libvirt after update
Ralf Müller
2012-08-29 08:03:35 UTC
Permalink
This is a resend from ***@opensuse.org and xen-***@lists.xen.org

Hi there.

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

Any idea what goes wrong?

Best regards
Ralf
Jim Fehlig
2012-08-29 14:36:09 UTC
Permalink
Post by Ralf Müller
Hi there.
Unable to connect to libvirt.
internal error libxenlight state driver is not active
That is odd, since it appears you are using xend. When xend is active,
the legacy libvirt xen driver should be used, not the libxenlight driver.

xend is running correct?

What is the output of 'virsh version'? Also, do you see the same error
when using virsh? E.g. 'virsh list --all'?

You can try restarting libvirtd, and peek at
/var/log/libvirt/libvirtd.log to see the results of probing which xen
driver to use.

Jim
Post by Ralf Müller
- 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
- A Xen host kernel was booted
- The Xen service has been started
Libvirt URI is: xen:///
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
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
Any idea what goes wrong?
Best regards
Ralf
--
To unsubscribe, e-mail: opensuse-virtual+***@opensuse.org
To contact the owner, e-mail: opensuse-virtual+***@opensuse.org
Ralf Müller
2012-08-29 15:05:12 UTC
Permalink
Post by Jim Fehlig
Post by Ralf Müller
Unable to connect to libvirt.
internal error libxenlight state driver is not active
That is odd, since it appears you are using xend. When xend is active,
the legacy libvirt xen driver should be used, not the libxenlight driver.
Can I configure that somewhere?
Post by Jim Fehlig
xend is running correct?
seems to be ok:
# rcxend status
redirecting to systemctl
xend.service - LSB: Starts and stops the Xen management daemon
Loaded: loaded (/etc/init.d/xend)
Active: active (running) since Tue, 28 Aug 2012 08:48:30 +0200; 1 day and 8h ago
Process: 1766 ExecStart=/etc/init.d/xend start (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/xend.service
├ 1998 blktapctrl
├ 2000 /usr/bin/python /usr/sbin/xend start
├ 2008 /usr/bin/python /usr/sbin/xend start
├ 4026 /usr/lib/xen/bin/qemu-dm -d 2 -serial pty -domain-na...
├ 5695 /usr/lib/xen/bin/qemu-dm -d 3 -serial pty -domain-na...
├ 6051 /usr/lib/xen/bin/qemu-dm -d 4 -domain-name gate -vid...
├ 8370 /usr/lib/xen/bin/qemu-dm -d 6 -serial pty -domain-na...
├ 9037 /usr/lib/xen/bin/qemu-dm -d 7 -serial pty -domain-na...
├ 9758 /usr/lib/xen/bin/qemu-dm -d 8 -serial pty -domain-na...
└ 15750 /usr/lib/xen/bin/qemu-dm -d 9 -serial pty -domain-na...
Post by Jim Fehlig
What is the output of 'virsh version'?
Thats fascinating:
# 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

What does this say to me?
Post by Jim Fehlig
Also, do you see the same error
when using virsh? E.g. 'virsh list --all'?
# virsh list --all
WARNING: gnome-keyring:: no socket to connect to
Id Name State
----------------------------------------------------
Post by Jim Fehlig
You can try restarting libvirtd, and peek at
/var/log/libvirt/libvirtd.log to see the results of probing which xen
driver to use.
# rclibvirtd restart; tail /var/log/messages
redirecting to systemctl
...
Aug 29 16:58:09 tower-core libvirtd[19796]: 2012-08-29 14:58:09.976+0000: 19807: info : libvirt version: 0.9.13
Aug 29 16:58:09 tower-core libvirtd[19796]: 2012-08-29 14:58:09.976+0000: 19807: warning : virSecurityManagerNew:136 : Configured security driver "none" disables default policy to create confined guests
Aug 29 16:59:00 tower-core libvirtd[19882]: WARNING: gnome-keyring:: no socket to connect to

Best Regards
Ralf
Jim Fehlig
2012-08-29 15:34:19 UTC
Permalink
Post by Ralf Müller
Post by Jim Fehlig
Post by Ralf Müller
Unable to connect to libvirt.
internal error libxenlight state driver is not active
That is odd, since it appears you are using xend. When xend is active,
the legacy libvirt xen driver should be used, not the libxenlight driver.
Can I configure that somewhere?
Post by Jim Fehlig
xend is running correct?
# rcxend status
redirecting to systemctl
xend.service - LSB: Starts and stops the Xen management daemon
Loaded: loaded (/etc/init.d/xend)
Active: active (running) since Tue, 28 Aug 2012 08:48:30 +0200; 1 day and 8h ago
Process: 1766 ExecStart=/etc/init.d/xend start (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/xend.service
├ 1998 blktapctrl
├ 2000 /usr/bin/python /usr/sbin/xend start
├ 2008 /usr/bin/python /usr/sbin/xend start
├ 4026 /usr/lib/xen/bin/qemu-dm -d 2 -serial pty -domain-na...
├ 5695 /usr/lib/xen/bin/qemu-dm -d 3 -serial pty -domain-na...
├ 6051 /usr/lib/xen/bin/qemu-dm -d 4 -domain-name gate -vid...
├ 8370 /usr/lib/xen/bin/qemu-dm -d 6 -serial pty -domain-na...
├ 9037 /usr/lib/xen/bin/qemu-dm -d 7 -serial pty -domain-na...
├ 9758 /usr/lib/xen/bin/qemu-dm -d 8 -serial pty -domain-na...
└ 15750 /usr/lib/xen/bin/qemu-dm -d 9 -serial pty -domain-na...
Post by Jim Fehlig
What is the output of 'virsh version'?
# 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
What does this say to me?
For some reason, libvirt is insisting on using the qemu driver. What if
you explicitly specify xen? E.g. 'virsh -c xen:/// version'?

I'll try to reproduce this too.

Jim
Post by Ralf Müller
Post by Jim Fehlig
Also, do you see the same error
when using virsh? E.g. 'virsh list --all'?
# virsh list --all
WARNING: gnome-keyring:: no socket to connect to
Id Name State
----------------------------------------------------
Post by Jim Fehlig
You can try restarting libvirtd, and peek at
/var/log/libvirt/libvirtd.log to see the results of probing which xen
driver to use.
# rclibvirtd restart; tail /var/log/messages
redirecting to systemctl
...
Aug 29 16:58:09 tower-core libvirtd[19796]: 2012-08-29 14:58:09.976+0000: 19807: info : libvirt version: 0.9.13
Aug 29 16:58:09 tower-core libvirtd[19796]: 2012-08-29 14:58:09.976+0000: 19807: warning : virSecurityManagerNew:136 : Configured security driver "none" disables default policy to create confined guests
Aug 29 16:59:00 tower-core libvirtd[19882]: WARNING: gnome-keyring:: no socket to connect to
Best Regards
Ralf
--
To unsubscribe, e-mail: opensuse-virtual+***@opensuse.org
To contact the owner, e-mail: opensuse-virtual+***@opensuse.org
Ralf Müller
2012-08-29 15:49:15 UTC
Permalink
Post by Jim Fehlig
For some reason, libvirt is insisting on using the qemu driver. What if
you explicitly specify xen? E.g. 'virsh -c xen:/// version'?
# virsh -c xen:/// version
WARNING: gnome-keyring:: no socket to connect to
error: internal error libxenlight state driver is not active
error: failed to connect to the hypervisor
Post by Jim Fehlig
I'll try to reproduce this too.
Tell me if you need information to do that.

Ralf
Jim Fehlig
2012-08-29 16:56:16 UTC
Permalink
Post by Ralf Müller
Post by Jim Fehlig
For some reason, libvirt is insisting on using the qemu driver. What if
you explicitly specify xen? E.g. 'virsh -c xen:/// version'?
# virsh -c xen:/// version
WARNING: gnome-keyring:: no socket to connect to
error: internal error libxenlight state driver is not active
error: failed to connect to the hypervisor
Post by Jim Fehlig
I'll try to reproduce this too.
Tell me if you need information to do that.
I'm able to reproduce and looking into it now.

Would you have time to open a bug for tracking?

Thanks,
Jim
--
To unsubscribe, e-mail: opensuse-virtual+***@opensuse.org
To contact the owner, e-mail: opensuse-virtual+***@opensuse.org
Jim Fehlig
2012-08-29 22:07:30 UTC
Permalink
Post by Jim Fehlig
Post by Ralf Müller
Post by Jim Fehlig
For some reason, libvirt is insisting on using the qemu driver. What if
you explicitly specify xen? E.g. 'virsh -c xen:/// version'?
# virsh -c xen:/// version
WARNING: gnome-keyring:: no socket to connect to
error: internal error libxenlight state driver is not active
error: failed to connect to the hypervisor
Post by Jim Fehlig
I'll try to reproduce this too.
Tell me if you need information to do that.
I'm able to reproduce and looking into it now.
This turns out to be quite a mess with all the recent upstream changes
wrt loadable driver modules. I'll be working with upstream to get this
resolved. Stay tuned...
Post by Jim Fehlig
Would you have time to open a bug for tracking?
Please open a bug.

Thanks for reporting!
Jim
--
To unsubscribe, e-mail: opensuse-virtual+***@opensuse.org
To contact the owner, e-mail: opensuse-virtual+***@opensuse.org
Ralf Müller
2012-08-30 07:13:06 UTC
Permalink
Post by Jim Fehlig
This turns out to be quite a mess with all the recent upstream changes
wrt loadable driver modules. I'll be working with upstream to get this
resolved. Stay tuned...
I do. Many thanks in advance.
Post by Jim Fehlig
Post by Jim Fehlig
Would you have time to open a bug for tracking?
Please open a bug.
Here it is:
https://bugzilla.novell.com/show_bug.cgi?id=778006

Loading...