similar to: Bug#688216: xen-utils-4.2: xl does not 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.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

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,

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

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-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.1 Version: 4.1.3-7 Severity: normal pygrub looks for extlinux config files "/boot/isolinux/isolinux.cfg" and "/boot/extlinux.conf", but the default Debian installation uses the config file "/boot/extlinux/extlinux.conf". (See /usr/lib/xen-4.1/bin/pygrub lines 405-407.) ...Marvin -- System Information: Debian Release: 7.0 APT prefers testing

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.1 Version: 4.1.3-7 Severity: normal The function is_disk_image in /usr/lib/xen-4.1/bin/pygrub at line 45 distinguishes a partitioned disk from a partition by looking for 0xaa55 at offset 0x1fe in the image, but this is the bootsector signature, not the partition table signature. extlinux and other bootloaders put this signature there on bootable partitions (which don't

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal The grub.cfg created by a default Debian installation uses many configuration statements that pygrub does not recognize, and pygrub is unable to find any kernel to load. ...Marvin -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500,

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal pygrub does not recognize the include statement in extlinux.conf. The default Debian installation of extlinux creates a stub extlinux.conf which includes linux.cfg, where all the linux image entries are. This means that even if bugs 697407 and 697409 are fixed, pygrub still can't find the right kernel on a default Debian installation

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

Package: xen-utils-4.1 Version: 4.1.3-4 Severity: important Tags: patch Bug presented in sid, with patch attached. Similar bug is also present in stable and testing versions. How to reproduce: Install xen-utils-4.1 in a domU, and run: /etc/init.d/xen start Expected result: xenstored running (or to have any other easy way to get it running within a domU) xenstored is not just something

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

Package: libxen-4.2 Version: 4.2.0-1 Severity: normal Hello, in xen 4.1 Debian packagers removed blktap uselessly as is documenteted in the blktap bug. in xen 4.2 qemu-dm is removed. This removes any reasonable way to access disks and reserves Debian Xen for diskless DomU use. Essentially Debian Xen packages are now useless. -- System Information: Debian Release: wheezy/sid APT prefers

Package: xen-utils-4.4 Version: 4.4.1-9+deb8u8 Severity: normal Under Xen 4.1 in Debian 7 (wheezy), the following works when included in a DomU configuration in "/etc/xen/cfg/" -- bootloader = '/usr/lib/xen-default/bin/pygrub' After upgrading to Xen 4.4 as part of an upgrade to Debian 8 (jessie), the DomU silently fails to start. Examination of the log files shows that the