Ralf Müller wrote:
> This is a resend from [email protected] and [email protected]
>
> 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
>
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
> 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
>
>
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
