[virt-tools-list] nternal error libxenlight state driver is not active

Fri Jun 14 19:31:00 UTC 2013

hello again,

On Fri, Jun 14, 2013 at 5:41 PM, Jim Fehlig <jfehlig at suse.com> wrote:

> nesredin mahmud wrote:
> > Hello Jim,
> >
> > thank for you replying me quickly!
> >
> > That was right i did not use --with-libxl option during configuration
> > of libvirt-1.0.6. Now libxenlight is loaded.
> >
> >
> >
> > On Thu, Jun 13, 2013 at 10:40 PM, Jim Fehlig <jfehlig at suse.com
> > <mailto:jfehlig at suse.com>> wrote:
> >
> >     nesredin mahmud wrote:
> >     > hello everyone,
> >     >
> >     > I have problem starting virt-manager (0.9.1). It tries to connect
> to
> >     > xen forever...
> >     > my environment setup is:
> >     > -ubuntu-12.0.4
> >     >
> >     > virsh # version
> >     > Compiled against library: libvirt 1.0.6
> >     > Using library: libvirt 1.0.6
> >     > Using API: Xen 1.0.6
> >     > Running hypervisor: Xen 4.2.0
> >     >
> >     > ERROR: from virt-manager
> >     >
> >     > 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
> >     >
> >     > Traceback (most recent call last):
> >     >   File "/usr/share/virt-manager/virtManager/connection.py", line
> >     1185,
> >     > in _open_thread
> >     >     self.vmm = self._try_open()
> >     >   File "/usr/share/virt-manager/virtManager/connection.py", line
> >     1167,
> >     > in _try_open
> >     >     flags)
> >     >   File "/usr/lib/python2.7/dist-packages/libvirt.py", line 102, in
> >     > openAuth
> >     >     if ret is None:raise libvirtError('virConnectOpenAuth()
> failed')
> >     > libvirtError: internal error libxenlight state driver is not active
> >     >
> >     > I taught the libxenligh was already working.
> >     > I compiled libvirt --with-xen and am using virsh as well.
> >
> >     To enable building the libxl driver use '--with-libxl'.
> >
> >     > And xl is working good.
> >     > I have stopped *xend* as well so that xl will working.
> >
> >     With debug enabled, do you see the libxl driver being initialized by
> >     libvirtd at startup?  E.g. you should see something like
> >
> > virsh # version
> > Compiled against library: libvirt 1.0.6
> > Using library: libvirt 1.0.6
> > Using API: xenlight 1.0.6
> > Running hypervisor: xenlight 4.2.0
> >
> > # tail  -f /var/log/syslog|grep virStateInitialize
> > Jun 14 16:09:59 swart-2 libvirtd: 9643: debug : virStateInitialize:826
> > : Running global init for Remote state driver
> > Jun 14 16:09:59 swart-2 libvirtd: 9643: debug : virStateInitialize:826
> > : Running global init for Network state driver
> >
> >
> >     2013-06-13 20:35:53.755+0000: 27848: debug : virStateInitialize:826 :
> >     Running global init for LIBXL state driver
> >
> > But I dont see the debug message:  Running global init for LIBXL state
> > driver
>
> Strange, you should be seeing more than the two noted above.  E.g. on my
> system with log_level=1 in libvirtd.conf:
>
> 2013-06-14 15:28:14.216+0000: 13314: debug : virStateInitialize:826 :
> Running global init for Remote state driver
> 2013-06-14 15:28:14.216+0000: 13314: debug : virStateInitialize:826 :
> Running global init for Network state driver
> 2013-06-14 15:28:14.365+0000: 13314: debug : virStateInitialize:826 :
> Running global init for Storage state driver
> 2013-06-14 15:28:14.365+0000: 13314: debug : virStateInitialize:826 :
> Running global init for udev state driver
> 2013-06-14 15:28:14.526+0000: 13314: debug : virStateInitialize:826 :
> Running global init for Secret state driver
> 2013-06-14 15:28:14.527+0000: 13314: debug : virStateInitialize:826 :
> Running global init for NWFilter state driver
> 2013-06-14 15:28:14.564+0000: 13314: debug : virStateInitialize:826 :
> Running global init for Xen state driver
> 2013-06-14 15:28:14.564+0000: 13314: debug : virStateInitialize:826 :
> Running global init for LIBXL state driver
> 2013-06-14 15:28:14.602+0000: 13314: debug : virStateInitialize:826 :
> Running global init for QEMU state driver
> 2013-06-14 15:28:19.934+0000: 13314: debug : virStateInitialize:826 :
> Running global init for LXC state driver
> 2013-06-14 15:28:19.965+0000: 13314: debug : virStateInitialize:826 :
> Running global init for UML state driver
>
> > Another problem I have seen after I recompiled libvirt: Virsh does not
> > list the dom0 and domu
>
> Currently, dom0 is not listed by the libvirt libxl driver, similar to
> the qemu or LXC driver not listing the "host" as a domain.  Perhaps this
> needs to be reconsidered though, since in Xen dom0 is just another
> domain and in many way can be managed just like any other domU, e.g.
> memory ballooned, vcpus added, etc.  But this is a separate discussion
> which should be held on the libvirt dev list :).
>
> I got this from libvirt debug:
libvirtd: 11172: error : virConnectListAllDomains:8430 : this function is
not supported by the connection driver: virConnectListAllDomains .

Good to know. I taught the new driver would support it. strange!

As for not seeing domUs, were those domUs created with libvirt?  libvirt
> won't know about domains managed by another libxl application, e.g.
> those created with 'xl create ...'.
>
> I really don't know where virsh tool stack stores guest domains. I didnt
use virsh to create guest machines. In stead, I use xl, xenD/xm  and
virt-manager. But I know here xen tool stack store guest domain information:
- xenD/xm =>
/var/lib/xend/domains/71de4ea9-3d30-f108-9eda-1f2a55bec4cb/config.sxp
-xl=> /var/lib/xen/userdata-d.*.xl

I made some test on the old and new libvirt driver with virt-manager.0.9.5

*1. libxl driver + virt-manager - i*t can connect to xen. But i could not
create the domain. Some location needed by virt-manager are not found in my
distribution i guess..you can see it from  the debug

2013-06-14 18:22:37,307 (connection:161): Using libvirt API for netdev
enumeration
2013-06-14 18:22:37,308 (connection:201): Using libvirt API for mediadev
enumeration
2013-06-14 18:22:56,477 (connect:121): Showing open connection
2013-06-14 18:23:00,409 (connect:110): Cancelling open connection
2013-06-14 18:23:00,409 (connect:116): Closing open connection
2013-06-14 18:23:35,036 (create:169): Showing new vm wizard
2013-06-14 18:23:35,041 (create:867): Guest type set to os_type=hvm,
arch=x86_64, dom_type=xen
2013-06-14 18:23:40,984 (create:867): Guest type set to os_type=xen,
arch=x86_64, dom_type=xen
2013-06-14 18:23:49,160 (storagebrowse:74): Showing storage browser
2013-06-14 18:23:50,828 (config:702): get_default_directory(image):
returning /var/lib/xen/images
2013-06-14 18:24:00,243 (storagebrowse:80): Closing storage browser
2013-06-14 18:24:15,920 (create:1854): Creating a VM test
  Type: xen,xen
  UUID: bbb37921-3a00-7c08-64f5-fe237c9cd907
  Install Source: None
  OS: None:None
  Kernel args: None
  Memory: 512
  Max Memory: 512
  # VCPUs: 1
  Filesize: 0.117477416992
/usr/local/share/virt-manager/virtManager/baseclass.py:240: GtkWarning:
Unknown property: GtkTable.halign
  util.sanitize_gtkbuilder(self.uifile))
2013-06-14 18:24:16,081 (util:353): Could not open
"/etc/sysconfig/keyboard" [Errno 2] No such file or directory:
'/etc/sysconfig/keyboard'
2013-06-14 18:24:16,081 (util:323): Could not open "/etc/X11/xorg.conf":
[Errno 2] No such file or directory: '/etc/X11/xorg.conf'
2013-06-14 18:24:16,093 (util:383): Didn't match keymap 'se' in keytable!
2013-06-14 18:24:16,134 (util:353): Could not open
"/etc/sysconfig/keyboard" [Errno 2] No such file or directory:
'/etc/sysconfig/keyboard'
2013-06-14 18:24:16,134 (util:323): Could not open "/etc/X11/xorg.conf":
[Errno 2] No such file or directory: '/etc/X11/xorg.conf'

*2. virt-manager + xenD/xm..*
libvirtd: 11901: info : libvirt version: 1.0.6
Jun 14 21:17:51 swart-2 libvirtd: 11901: error : xenHypervisorDoV2Sys:959 :
Unable to issue hypervisor ioctl 3166208: Permission denied
Jun 14 21:18:53  libvirtd: last message repeated 5 times

I really dont mind if either  way virt-manager works for me. I guess the
first problem is concerns to the distribution am using, ubuntu. But the
second one..i really dont get it. I run virt-manager with root permission.

thank you

Best

//nas

> Regards,
> Jim
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/virt-tools-list/attachments/20130614/8e1d871e/attachment.htm>