similar to: Bug#688311: xen-utils-4.2: qemu-dm not available

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

So how do I set up an HVM with Debian? I tried with device_model_version="qemu-xen", and I got this: libxl: error: libxl_dm.c:1086:libxl__spawn_local_dm: device model /usr/lib/xen-4.2/bin/qemu-system-i386 is not executable: No such file or directory I also tried device_model_version="qemu-xen-traditional", and I got this: libxl: error: libxl_dm.c:1086:libxl__spawn_local_dm:

Package: xen Version: 4.1.2-3 Severity: wishlist Hi, we're patching libvirt (incompletely atm) and also virtinst to cope with Debian's derivation from upstream to put things into /usr/lib/xen-<version> managed via alternatives to /usr/lib/xen-default. While the basic idea is great to be able to switch between different xen versions it would us get closer to upstream if we had a

Package: libxen-dev Version: 4.1.1-2 Severity: wishlist Hi, please make it possible to link against libxenlight by including libxenlight.so and libxl.h into libxen-dev. This is needed to enable the xenlight interface in libvirt. Cheers, -- Guido -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (50, 'unstable'), (1,

Package: xen Version: 4.1.1 Severity: wishlist On the xen-qemu-dm-4.0 package, I enabled audio support, but since this is packaged in 4.1, audio support is gone. What I did for squeeze, is: --- a/configure 2010-03-23 17:08:39.000000000 +0800 +++ b/configure 2010-03-23 17:09:30.000000000 +0800 @@ -1382,6 +1382,9 @@ echo "#define CONFIG_VDE 1" >> $config_h echo

Qemu upstream now can be added on xen >=4.2, seabios added support for xen: seabios (1.7.1-1) unstable; urgency=low * updated to new minor upstream release (1.7.1): - native scsi boot support (Closes: #652530) - usb-attached scsi boot support - Xen support (Closes: #678042) - better integration with qemu - some bugfixes * removed fix-==-in-shell.patch (not

An upstream patch for xen 4.4 to disable both traditional and upstream qemu compilation and use upstream qemu from debian package is available: http://lists.xen.org/archives/html/xen-devel/2013-08/msg00393.html I haven't had time to test it yet but it should work and it should be easy and fast to backports to 4.3. -------------- next part -------------- A non-text attachment was scrubbed...

Package: xen-utils-common Version: 4.0.0-1 Severity: important The xm utility requires python-xml but the package does not depend on it. # xm new --help_vars Unexpected error: <type 'exceptions.ImportError'> Please report to xen-devel at lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-4.0/bin/xm", line 8, in <module>

Package: xen-utils-4.3 Version: 4.3.0-3+b1 Severity: normal When I try to create an HVW withDevian/xen, I run into trouble. It used to work, maybe with xen 4.1, but it has never worked since. Bug 688311 was filed, with the same exact problem. That bug was somehow closed and no resolution or explanation was provided. I have seen posts mentioning "traditional" and "upstream"

Hello, when I boot DomU which uses DHCP to configure IPv4 address it does never get a lease. The packets travel to Dom0 where the dhcp server receives them, sends a reply, that travels to DomU where dhclient receives it, says the checksum is invalid, and discards it. The problem is documented here: http://old-list-archives.xen.org/archives/html/xen-users/2006-02/msg00152.html

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3 Severity: grave Justification: causes non-serious data loss -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') 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

Processing commands for control at bugs.debian.org: > forcemerge 688311 688638 Bug #688311 [xen-utils-4.2] xen-utils-4.2: qemu-dm not available Bug #688638 [xen-utils-4.2] xen-utils-4.2: cannot run PV DomU off a disk image Severity set to 'normal' from 'important' Bug #688311 [xen-utils-4.2] xen-utils-4.2: qemu-dm not available Marked as found in versions xen/4.2.0-1; no longer

http://bugs.freedesktop.org/show_bug.cgi?id=23092 Summary: Syslog flooded with "nouveau 0000:01:00.0: Unhandled PFIFO_INTR - 0x00000010" Product: xorg Version: 7.4 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

Hi, > xen-utils-4.1 is not in unstable, so this is not really helpful. I can still install it in my VM and this page shows a xen-utils-4.1 in sid: http://packages.debian.org/sid/xen-utils-4.1. I'm not sure what you mean when you say it's not in unstable. > Could you please explain why "exit 1" is a crash? "exit 1" is obviously not a crash. However, qemu-dm

Hi, We found a crash in qemu-dm contained in the xen-utils-4.1 package. You are being contacted because your are listed as one of the maintainer of xen-utils-4.1. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the seriousness of the bug before it is publicly disclosed. The bug report that will

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: grave Justification: renders package unusable qemu-dm sends out this: - supported machines are: pc Standard PC (default) isapc ISA-only PC - instead of: - Supported machines are: xenfv Xen Fully-virtualized PC (default) xenpv Xen Para-virtualized PC - this renders any tries to use HVM fail. -- System Information:

Hello everybody! Still struggeling with my latest Samba setup, I've just run accross another problem which I can't figure out on my own. Samba is supposed to act as a WINS server (among other things) on a multihomed machine. (The Samba version is 3.5.1 as part of Debian Squeeze) Here's the [global] part of the samba setup: ----------------------------------- 8<

On a train ride to Bruxelles, brought out my axe and directly attacked run_init(8). run_init(8) is dead, long live switch_root(8). The next run on switch_root(8) involves fdopendir, so another push for the upcoming stdio 1.6 branch. The following is boot tested with initramfs-tools, kinit(8) tests would very much be appreciated!? Michal Suchanek (1): [klibc] switch_root: Fix single file