similar to: Bug#688227: xen-utils-4.2: /etc/default/xen TOOLSTACK undocumented

Package: xen-utils-4.2 Version: 4.2.0-1 Severity: normal Hello, xl is supposed to be current tool for managing virtual machines on xen (in absence of any working GUI for that in Debian). However, xl produces this: # xl list ERROR: A different toolstack (xm) have been selected! There is no info in README.Debian I could find how to cahnge this selection. Reportedly both xl and xm work

Package: xen-utils-4.2 Version: 4.2.0-1 Severity: normal Hello, xl-network-configuration.markdown which is referenced ins the sample configuration and is supposed to detail networking configuration is not installed. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (910, 'testing'), (900, 'stable'), (410, 'unstable'), (200,

Package: xen-utils-4.2 Version: 4.2.0-1 Severity: normal Hello, I tried running a xen domain but it complains about missing file not in current xen-utils: libxl: error: libxl_dm.c:1086:libxl__spawn_local_dm: device model /usr/lib/xen-4.2/bin/qemu-dm is not executable: No such file or director $ apt-file search qemu-dm xcp-xapi: /usr/lib/xcp/lib/qemu-dm-wrapper xen-utils-4.1:

Package: xen-utils-4.2 Version: 4.2.0-1 Severity: important Hello, I tried running a DomU usinga disk image file for storage. This tries to use qemu-dm to attach the file as disk which does not exist. When I set up a loop device using the disk image and use that as disk it attaches without issues. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (910,

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,

Subject: xen-utils-4.1: /usr/lib/xen-default missing Package: xen-utils-4.1 Version: 4.1.3-1 Severity: important Dear Maintainer, when using paravirtualization with xen and libvirt the path for pygrub is: /usr/lib/xen-default/bin/pygrub But this path is not provided with xen-utils-4.1 and will brake upgrades to wheezy. With xen-utils-4.0 and debian squeeze this path is provided with

Package: xen-utils-4.6 Version: 4.6.0-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these

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

Package: xen-utils-4.1 Version: 4.1.3-5 Severity: important Dear Maintainer, The xen 4.1.3 release misses this 4.2 patch mentioned in this thread: http://lists.xen.org/archives/html/xen-devel/2012-06/msg01909.html As a result, MSI delivery does not work properly for PVHVM guest. In my case, PCI devices passthroughed from host does not work properly, the guest kernel complains about missing

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: xen-utils-4.1 Version: 4.1.3-2 Severity: important Dear Maintainer, Creating a new HVM domU fails with the following error: map shared IO page returned error 22 I've narrowed it down to qemu-dm which fails to start: # /usr/lib/xen-4.1/bin/qemu-dm [...] qemu_map_cache_init nr_buckets = 10000 size 4194304 errno0 = 2 domid = -1 shared page at pfn 0 errno1 = 3 errno2 = 22 map shared IO

Package: xen-utils-4.1 Version: 4.1.4-2 Severity: normal -- System Information: Debian Release: 7.0 ? APT prefers testing ? APT policy: (990, 'testing'), (500, 'testing-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages

Package: xen-utils-4.4 Version: 4.4.1-6 Severity: normal Dear Maintainer, The xen-utils-4.4 package in jessie is missing the gdbsx binary. This is useful to have when one wishes to debug Xen domains, and complicated to obtain if one does not have it ready. The same package on at least Ubuntu 14.04.1 LTS does contain this binary, in /usr/lib/xen-4.4/bin. However, if you have no objections I

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

Package: xen-utils-4.4 Version: 4.4.1-9 Severity: normal # /usr/lib/xen-4.4/bin/xl create -c /etc/xen/katana Parsing config from /etc/xen/katana libxl: error: libxl_utils.c:217:logrename: failed to rotate logfile - could not rename /var/log/xen/qemu-dm-katana.log.6 to /var/log/xen/qemu-dm-katana.log.7: Permission denied Segmentation fault The above happens repeatably when I run xl on a system

Package: xen-utils-4.4 Version: 4.4.1-3 Severity: important Hello, qemu-dm is no longer present in xen-utils-4.4. As reported in xen Wiki, without qemu-dm is not possible to passthrough vga adapters. Please consider to include it again in the build of xen-utils. Many Thanks. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing')

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

Package: xen-utils-4.3 Version: 4.3.0-3 Severity: normal II'm install xen-4.3 from official repository. When i try create virtulal machine got error: xl -vvvv create /etc/xen/xlexample.hvm Parsing config from /etc/xen/xlexample.hvm libxl: debug: libxl_create.c:1230:do_domain_create: ao 0x19811c0: create: how=(nil) callback=(nil) poller=0x1981220 libxl: verbose:

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

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