[libvirt-users] Does libvirt support xapi/xe toolstack?
Hello, I installed the last version of Xen (xenserver-core-0.9.0-9.x86_64 from yum) and I'm trying to manage my VMs with virsh. The version that I installed is using the Xapi/xe toolstack. The problem I have is that I'm not seeing the VM that is started with "virsh -c xen:/// list --all". Here is what I have: root# xe vm-list uuid ( RO) : 022226ed-07be-37fc-5b52-f798320e2726 name-label ( RW): vm1 power-state ( RO): running uuid ( RO) : 394fa633-f600-45f9-bea7-3bf4a9fd06fd name-label ( RW): Control domain on host: unknown power-state ( RO): running root# virsh -c xen:/// list --all Id Name State ---------------------------------------------------- # According to [1] it seems that libvirt is using Xend daemon to communicate. The problem is that Xend is now deprecated since Xen 4.1. So am I wrong with this assumption or is there something to configure to be able to use libvirt with Xapi/XE toolstack? I looked in the documentation but I only found [2] but I didn't see any special settings... Regards, Guillaume [1] http://libvirt.org/architecture.html [2] http://libvirt.org/drvxen.html
Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit :
According to [1] it seems that libvirt is using Xend daemon to communicate.
After reading more documentation it seems that Xend is mandatory. As everything is not up to date I'd like to know if it is still the case or if there are some possibilities to use XL instead of Xend? Best regards, Guillaume
On Mon, Sep 30, 2013 at 10:49:10AM +0200, Guillaume Thouvenin wrote:
Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit :
According to [1] it seems that libvirt is using Xend daemon to communicate.
After reading more documentation it seems that Xend is mandatory. As everything is not up to date I'd like to know if it is still the case or if there are some possibilities to use XL instead of Xend?
If you have new enough libvirt and Xen >= 4.2 then libvirt will automatically use the libxl APIs instead of XenD. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
"Daniel P. Berrange" <berrange@redhat.com> a écrit :
On Mon, Sep 30, 2013 at 10:49:10AM +0200, Guillaume Thouvenin wrote:
Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit :
According to [1] it seems that libvirt is using Xend daemon to communicate.
After reading more documentation it seems that Xend is mandatory. As everything is not up to date I'd like to know if it is still the case or if there are some possibilities to use XL instead of Xend?
If you have new enough libvirt and Xen >= 4.2 then libvirt will automatically use the libxl APIs instead of XenD.
Thanks for the confirmation. So my version of libvirt seems too old then (I'm using Xen 4.2.2) : # libvirtd --version libvirtd (libvirt) 0.10.2.6 I will try to install libvirt from the git repo. Thanks for your help, Regards.
Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit :
"Daniel P. Berrange" <berrange@redhat.com> a écrit :
If you have new enough libvirt and Xen >= 4.2 then libvirt will automatically use the libxl APIs instead of XenD.
I have compiled a version 1.1.2 (with xapi and xl support) and installed it in /usr/local. I started the daemon but I didn't see my vm1 listed even if everything seems fine in the log: # /usr/local/sbin/libvirtd --daemon # xl list Name ID Mem VCPUs State Time(s) Domain-0 0 2047 32 r----- 188.2 vm1 1 4096 1 -b---- 13.5 # LD_LIBRARY_PATH=/usr/local/lib /usr/local/bin/virsh -c xen:/// list --all Id Name State ---------------------------------------------------- # I see nothing in the libvirtd.log and I see this in libxl-driver.log: # cat libxl/libxl-driver.log xc: debug: hypercall buffer: total allocations:21 total releases:21 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:16 misses:4 toobig:1 xc: debug: hypercall buffer: total allocations:21 total releases:21 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:16 misses:4 toobig:1 xc: debug: hypercall buffer: total allocations:18 total releases:18 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:13 misses:4 toobig:1 xc: debug: hypercall buffer: total allocations:18 total releases:18 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:13 misses:4 toobig:1 xc: debug: hypercall buffer: total allocations:18 total releases:18 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:13 misses:4 toobig:1 Any idea where I should looked to find why I don't see the vm1 with the virsh command? Regards, Guillaume
Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit :
Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit :
"Daniel P. Berrange" <berrange@redhat.com> a écrit :
If you have new enough libvirt and Xen >= 4.2 then libvirt will automatically use the libxl APIs instead of XenD.
I have compiled a version 1.1.2 (with xapi and xl support) and installed it in /usr/local. I started the daemon but I didn't see my vm1 listed even if everything seems fine in the log:
# /usr/local/sbin/libvirtd --daemon # xl list Name ID Mem VCPUs State Time(s) Domain-0 0 2047 32 r----- 188.2 vm1 1 4096 1 -b---- 13.5 # LD_LIBRARY_PATH=/usr/local/lib /usr/local/bin/virsh -c xen:/// list --all Id Name State ----------------------------------------------------
#
I see nothing in the libvirtd.log and I see this in libxl-driver.log:
# cat libxl/libxl-driver.log xc: debug: hypercall buffer: total allocations:21 total releases:21 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:16 misses:4 toobig:1 xc: debug: hypercall buffer: total allocations:21 total releases:21 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:16 misses:4 toobig:1 xc: debug: hypercall buffer: total allocations:18 total releases:18 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:13 misses:4 toobig:1 xc: debug: hypercall buffer: total allocations:18 total releases:18 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:13 misses:4 toobig:1 xc: debug: hypercall buffer: total allocations:18 total releases:18 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:13 misses:4 toobig:1
Any idea where I should looked to find why I don't see the vm1 with the virsh command?
I tried to start the libvirtd in debug mode but I didn't see any obvious error. I know that I'm using the right driver because I see "do_open:1224 : driver 7 xenlight returned SUCCESS" but otherwise I don't know what to look for. I pasted the log of libvirtd that I got when running the "virsh list" command but I don't know if it can help... it is here: http://pastebin.com/N2jJfWuu Guillaume
On lun, 2013-09-30 at 16:38 +0200, Guillaume Thouvenin wrote:
Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit :
Any idea where I should looked to find why I don't see the vm1 with the virsh command?
I don't really know much about Xapi, I'm afraid. Might be worth asking to the xen-api mailing list: http://lists.xenproject.org/cgi-bin/mailman/listinfo/xen-api http://www.xenproject.org/help/mailing-list.html Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
participants (3)
-
Daniel P. Berrange -
Dario Faggioli -
Guillaume Thouvenin