similar to: “Unable to connect to libvirt” (xen, xl toolstack, and virt-manager)

hi, i found something im my log: (libvirtd.log) i dont know about this. but it may be helpful for you. So i am forwarding this. 2013-09-26 11:43:58.507+0000: 10718: error : virDriverLoadModule:78 : failed to load module /usr/local/lib/libvirt/connection-driver/libvirt_driver_libxl.so /usr/lib/libxenlight.so.2.0: undefined symbol: xs_check_watch 2013-09-26 11:43:58.790+0000: 10729: error :

hi, i removed all libvirt things form my system and i installed libvirt-0.9.12 frm my repository. then i installed libvirt-1.1.2 from the source with following commands. ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc --with-xen=yes --with-libxl=yes make make install now its works with XM. but with xl its not working... i attached the corresponding screenshots also. kindly

hi, i prepared my xen-4.2.1 document with this mail. kindly refer the below attachment. i installed libvirt 1.1.1 like this it giving the following error: ./autogen.sh --system --with-xen=yes make /daemon/libvirtd -d then i checked with the virsh ->version virsh # version error: failed to connect to the hypervisor error: no valid connection error: Failed to connect socket to

cooldharma06 wrote: > hi, > > i found something im my log: (libvirtd.log) > > i dont know about this. but it may be helpful for you. So i am > forwarding this. > > 2013-09-26 11:43:58.507+0000: 10718: error : virDriverLoadModule:78 : > failed to load module > /usr/local/lib/libvirt/connection-driver/libvirt_driver_libxl.so > /usr/lib/libxenlight.so.2.0: undefined

Hi, Trying to get CPU masking working with xen and it's just stubbornly refusing to work. Spawning a VM with xm directly works fine, but every time I try with libvirt it just ends up having all the flags of the host. Looking at the xen logs, libvirt doesn't appear to be passing any cpu options to xen at all. Running centos 6.5 with the xen 4 packages (4.2.4), but I've also

hi, i am using debian flavor called BOSS. *uname -a* Linux boss 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux i installed XEN-4.2.1 from the source. *virsh # version* error: failed to connect to the hypervisor error: no valid connection error: Failed to connect socket to '/usr/local/var/run/libvirt/libvirt-sock': No such file or directory * * *root@boss[src]#libvirtd -v*

On lun, 2013-09-30 at 11:27 +0530, cooldharma06 wrote: > hi, > Hi, > thanks for your response. > > > i cleaned that above one and installed in this following steps: > > > * sudo apt-get install gcc make pkg-config libxml2-dev libgnutils-dev > libdevmapper-dev libcurl4-gnutls-dev python-dev libpciaccess-dev > libxen-dev libnl-dev > Oh, so you are on

/usr/lib/xen-common/bin/xen-toolstack returns /usr/sbin/xm (or /usr/sbin/xl), I had to modify /usr/lib/xen-common/bin/xen-toolstack-wrapper such a way to make it work: exec "/usr/lib/xen-default/bin/"`echo $TOOLSTACK | awk -F'/' '{ print $4 }'` "$@" originally it returned /usr/sbin/[xm,xl] bringing to an endless loop. Niccol?

Hello, everybody! Does anyone have experience of running win7/winxp with xl? As for me, I got HAL_INITIALIZATION_FAILED BSOD on win7 booting and guest hanging in case of winxp. When i run these guests (with the same configs) with xm, everything is ok. The guests boot perfectly. Did anyone run into it too? I use the lattest xen-unstable, but i saw the problem several months ago too. My

I have an issue on Xen 4.2+ (now on yesterday''s tip) where when I try to use an iso image as cdrom for a pv domU, it appears that the devices is an unusable state on the domU side. DomU kernel output: http://bpaste.net/show/63482/ xen logs: http://bpaste.net/show/63490/ udevadm monitor output: http://bpaste.net/show/63481/ I can work around this issue easily by creating a loop back

Hello, After creating and destroying a number of domUs, I noticed that /local/domain/0/backend starts to get cluttered when using XL. The vif, vfb, vkbd, and vbd sections look like this: 270 = "" 271 = "" 272 = "" 273 = "" 274 = "" 275 = "" Where the dom ID is set to an empty value, however the console

Package: xen-utils-4.2 Version: 4.2.0-1 Severity: important Hello, the default xl toolstack does not work in the Xen Debian packages. It reports that xm toolstack is selected but no way how to change it. The /etc/defaul/xen has no documentation whatsoever. Please make both stack available or properly document how to switch. -- System Information: Debian Release: wheezy/sid APT prefers

Hopefully someone knows the answer to this, BUT has anyone successfully installed the XAPI Toolstack on a Debian Dom0 (such as Squeeze or Wheezy OR even latest Ubuntu is similar enough) WITH Xen 4.2-unstable compiled and running? AND if so, how to do that? Thank you.

Hello, Hope you can help. A while ago users noted performance degradation or dom0 stability issues when shuting down a HVM guest that uses VGA passthrough (e.g. Windows 7), and booting up the guest again. A workaround was to eject the graphics card within Windows, before shutting down the guest. This process is described here: http://blog.ktz.me/?p=219. I tried to follow those instructions, but

tags 648029 +patch thanks Here's a patch for bug #648029 "/usr/lib/xen-common/bin/xen-toolstack (and thus /usr/sbin/xm) works with bash, but not with dash". Works for me, tested with dash and bash. -------------- next part -------------- A non-text attachment was scrubbed... Name: 648029.patch Type: text/x-diff Size: 611 bytes Desc: not available URL:

Hi, I have made a small patch to xen-common so that there's a debconf to control which toolstack to use. Bastian, please let me know what you feel about it, and if you think it should be included in your next upload. Cheers, Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: choose_xl_with_debconf.patch Type: text/x-diff Size: 8584 bytes Desc: not

Processing commands for control at bugs.debian.org: > retitle 655301 xend shouldn't start if TOOLSTACK is not xm Bug #655301 [xcp-xapi] xcp-xapi fails to start Changed Bug title to 'xend shouldn't start if TOOLSTACK is not xm' from 'xcp-xapi fails to start' > reassign 655301 xen-utils-common Bug #655301 [xcp-xapi] xend shouldn't start if TOOLSTACK is not xm Bug

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) :

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

"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