Am 29.08.2012 um 16:36 schrieb Jim Fehlig:
> Ralf Müller wrote:
>>
>>
>> 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
>>
>
> 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?
> 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...
> 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?
> 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
----------------------------------------------------
> 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: [email protected]
To contact the owner, e-mail: [email protected]
