search for: toolstacks

Package: xen-utils-common Version: 4.1.2-3 Severity: important /etc/default/xen, which carries the TOOLSTACK setting, is not honored by xend init script. The xend initscript doesn't check for the value of TOOLSTACK. It just populates it in its initscript. lnx200-39:/etc/init.d# grep TOOLSTACK * xend:TOOLSTACK=$(/usr/lib/xen-common/bin/xen-toolstack 2>/dev/null) xend: if [ -z

...s.README.Debian @@ -1,6 +1,21 @@ Xen for Debian ============== +Toolstack selection +------------------- + +The selection of which toolstack to run can be made by editing /etc/default/xen +and updating the TOOLSTACK variable. Note that you will need to reboot after +doing this. + +The following toolstacks are available: + - xl: modern upstream default toolstack. + - xapi: an alternative toolstack from the xenserver.org project. + - xm: the older legacy upstream toolstack. + +xl and xm are part of the xen-utils packages, while xapi is provided by the +xcp-xapi packages. + Config behaviour ---------...

During some discussions and handwaving, including discussions with some experts on the Xenserver/XCP storage architecture, we came up with what we think might be a plausible proposal for an architecture for communication between toolstack and driver domain, for storage at least. I offered to write it up. The abstract proposal is as I understand the consensus from our conversation. The concrete

i am trying to add auto migration feature in XEN. so is anyone has worked related to migration part. i need help regarding files related to migration. -- Regards Gautam _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

From: Stefano Stabellini <stefano.stabellini@eu.citrix.com> When disk is a cdrom and the drive is empty the "params" node in xenstore might be missing completely: cope with it instead of segfaulting. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> --- hw/xen_disk.c | 16 +++++++++++----- 1 files changed, 11 insertions(+), 5 deletions(-) diff --git

Package: xcp-xapi Severity: important The README doc mentions: 4/ Configuring Xen and XCP -------------------------- 4.1/ Switch using xl instead of xm and xend to control Xen As of writing, you should do that: sed -i "s/TOOLSTACK=/TOOLSTACK=xl/" /etc/default/xen Where as the init script checks for: # Exit cleanly if TOOLSTACK != xapi if [ "${TOOLSTACK}" !=

Package: xen-utils-common Version: 4.1.2-7 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, The script /usr/lib/xen-common/bin/xen-toolstack improperly aborts if *either* `xm` or `xl` cannot be found in the xen-dir (/usr/lib/xen-4.0/bin). This means that a default installation (e.g. following Debian wiki on the subject, namely installing xen-linux-system and

tags 466683 +patch thanks commit 765ac4708e4dd8a6fea0028d631a7c3363b286b7 Author: Ian Campbell <ijc at hellion.org.uk> Date: Fri Aug 16 10:30:17 2013 +0100 * debian/changelog: Update * debian/templates/control.main.in: Update descriptions for some packages. diff --git a/xen/debian/changelog b/xen/debian/changelog index 6100e75..e5b25ef 100644 --- a/xen/debian/changelog +++

On Tue, 2013-10-22 at 11:52 +0200, PASZTOR Gyorgy wrote: > When you use xl toolstack, you can't reboot domUs. > When you switch back to xm toolstack, than reboot works again. > I think the problem with the debian packaged version is the same as in > this thread: > http://lists.xen.org/archives/html/xen-devel/2011-09/msg01289.html > I also think it's a security issue,

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important Tags: security patch When you use xl toolstack, you can't reboot domUs. When you switch back to xm toolstack, than reboot works again. I think the problem with the debian packaged version is the same as in this thread: http://lists.xen.org/archives/html/xen-devel/2011-09/msg01289.html I also think it's a security issue,

There's no date defined yet, but Wheezy freeze will happen soon. How do we plan on concluding on this bug report? Recap for the actual bug I reported: If you want to start xapi, execute the following steps: 1) Start /etc/init.d/xend 2) Stop /etc/init.d/xend 3) Start /etc/init.d/xcp-xapi Step 1 is required because you need access to /proc/xen/ Step 2 is required because xapi cannot run

I have just installed Xen by following http://wiki.xen.org/wiki/Xen_Beginners_Guide All in all pretty good, however it mentions using the xl toolset but when I first installed only the xm toolset would work. This was great for creating linux based domains but it gave me an error about hvm when I tried creating a Windows domain. I then apt-get install xen-tools-common and edited /etc/default/xen

Hello, is there a way to start automatically the vncviewer when a domU starts? When I was using the xm toolstack I could use "xm create domain.cfg -vncviewer" or something similar (if I''m not wrong), but I don''t know how to do it with the xl toolstack. At the moment, I have to create the domain using xl create domU.cfg, then xl list to see the domU id and then xl

Hi, I am using XEN-4.1.2 and linux-2.6.32 as dom0. After I upgraded stackless python from 2.5 to 2.7 (and rebuilt xen). XenAPI became unusable, I spent some time to investigate XenAPI,py, it looks fine. So, I guess xend has problem with python 2.7, because it always returned method unknown. Do I have to tweak xend to let it support python 2.7? Thanks, Eric /root # python Python 2.7.5 Stackless

Hi, "Ian Campbell" <ijc at hellion.org.uk> ?rta 2013-10-22 11:17-kor: > On Tue, 2013-10-22 at 11:52 +0200, PASZTOR Gyorgy wrote: > > When you use xl toolstack, you can't reboot domUs. > > When you switch back to xm toolstack, than reboot works again. > > I think the problem with the debian packaged version is the same as in > > this thread: > >

Processing commands for control at bugs.debian.org: > user pkg-xen-devel at lists.alioth.debian.org Setting user to pkg-xen-devel at lists.alioth.debian.org (was ijc at debian.org). > usertags 599520 toolstack-xend There were no usertags set. Usertags are now: toolstack-xend. > close 599520 4.4.0-1 Failed to add fixed version '4.4.0-1' to 599520: Not altering archived bugs; see

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

/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?

Ian Campbell wrote: > + * Expand on the descriptions of some packages. (Closes: #466683) Trivial typo here: > Package: libxen-dev > Section: libdevel > Depends: libxen- at version@ (= ${binary:Version}), libxenstore3.0 (= ${binary:Version}), ${misc:Depends} > Description: Public headers and libs for Xen > This package contains the public headers and static libraries for

Package: xen-utils-common Version: 4.1.2-1 Severity: grave Justification: renders package unusable (Grave because dash is the default /bin/sh) With dash 0.5.5.1-7.4 as /bin/sh, /usr/sbin/xm enters an infinite loop of reexcuting itself. When run with bash, it works correctly. I traced that to /usr/lib/xen-common/bin/xen-toolstack; here's the diff between "/bin/sh -x /usr/sbin/xm"