similar to: Bug#648029: patch for Bug#648029 xen-toolstack (and thus xm) works with bash, but not dash

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"

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

Accepted: libxen-4.1_4.1.2-4_amd64.deb to main/x/xen/libxen-4.1_4.1.2-4_amd64.deb libxen-dev_4.1.2-4_amd64.deb to main/x/xen/libxen-dev_4.1.2-4_amd64.deb libxen-ocaml-dev_4.1.2-4_amd64.deb to main/x/xen/libxen-ocaml-dev_4.1.2-4_amd64.deb libxen-ocaml_4.1.2-4_amd64.deb to main/x/xen/libxen-ocaml_4.1.2-4_amd64.deb libxenstore3.0_4.1.2-4_amd64.deb to

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

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

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,

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,

QUESTION: What, if anything, can I do so that I can use xl (in place of xm) with libvirt 1.0.2 and Xen 4.2.1 in Ubuntu 13.04? BACKGROUND: I am testing a fully updated (as of March 27) installation of Ubuntu 13.04 that includes the following packages: libvirt - version 1.0.2-0ubuntu9 xen-hypervisor-4.2-amd64 - version 4.2.1-0ubuntu1 Upon setting TOOLSTACK=xm in /etc/default/xen (as well as

I''ve migrated my Dom0 host to Xen 4.2.0 + xl toolstack. With ''xm'' toolstack, configs in /etc/xen/auto are autostarted, assuming xend/xendomains services are started. IIUC, when using xl toolstack, those services are not to be started; and, afaict, the installation process for 4.2 has them disabled by default. Now, the configs in /etc/xen/auto are simply ignored. I

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

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

Hello, Currently it seems that the drbd disk type with Xen''s XL toolstack (vs XM) to get the automatic promotion/demotion behavior of drbd devices is not supported. Is there something I can tweak with the block-drbd script to get this to work? Thanks, Chris _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

Hello, Currently it seems that the drbd disk type with Xen''s XL toolstack (vs XM) to get the automatic promotion/demotion behavior of drbd devices is not supported. Is there something I can tweak with the block-drbd script to get this to work? Thanks, Chris _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

Hej folks, I''m messing around with DRBD once again but with a new Xen 4.1.2 installation using the XL toolstack instead of the xend daemon. However, after getting my DRBD installed and a device operational, trying to create a domU using the drbd block device doesn''t want to work: xl create -c test.cfg Parsing config file test.cfg Unknown disk type: drbd My config has: disk

Hi, I was just wondering if it is possible to cause a script to run (configured in the domu.cfg file) each time "xm create domu.cfg" is run, but before the machine is actually started? ie, I''d like to "setup" the disks for the VM before xen/qemu tries to use the devices and allocate to the domu. I''m using xen 4.1.3 on Debian testing, and using the xm

Control: tag -1 +patch commit 717323e8f7398d45f8dc923a20a75baa7333adf1 Author: Ian Campbell <ijc at hellion.org.uk> Date: Fri Aug 16 16:39:11 2013 +0100 * debian/xen-utils.README.Debian: Document how to change toolstack * debian/changelog: Update diff --git a/xen/debian/changelog b/xen/debian/changelog index 6100e75..9426897 100644 --- a/xen/debian/changelog +++

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}" !=

Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> diff -r 3b409f65abae docs/man/xm.pod.1 --- a/docs/man/xm.pod.1 Thu Dec 01 17:26:48 2011 +0000 +++ b/docs/man/xm.pod.1 Thu Dec 01 18:01:35 2011 +0000 @@ -1,6 +1,6 @@ =head1 NAME -xm - Xen management user interface +xm - Obsolete xen management user interface =head1 SYNOPSIS @@ -8,10 +8,14 @@ B<xm> I<subcommand>

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

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