similar to: Bug#624334: xen-qemu-dm-4.0 - source-less binaries

Hi, I believe the package is ready: http://ftparchive.gplhost.com/debian/pool/lenny/main/x/xen-qemu-dm-3.4/xen-qemu-dm-3.4_3.4.2-1.dsc I asked Ian Jackson to sponsor it (he works for Citrix and is a DD), but it's been 2 weeks, and he seems busy with work. I'd be glad if someone was sponsoring the upload of this package in Debian SID, soon enough so that people will be able to test it

Hi, I believe the package is ready: http://ftparchive.gplhost.com/debian/pool/lenny/main/x/xen-qemu-dm-3.4/xen-qemu-dm-3.4_3.4.2-1.dsc I asked Ian Jackson to sponsor it (he works for Citrix and is a DD), but it's been 2 weeks, and he seems busy with work. I'd be glad if someone was sponsoring the upload of this package in Debian SID, soon enough so that people will be able to test it

On 04/27/2011 04:23 AM, Niccol? Belli wrote: > Hi, I backported xen-4.1-2 to Squeeze, but when I try to build > xen-qemu-dm-4.0 against it, it doesn't build. > Can you please help me? I attached log file. > > Niccol? Hi, To me, this looks like an issue with libxen-dev. The file /usr/include/xenctrl.h is the one to blame in your build log... Please write to the pkg-xen list

Hi, When I first built my Debian package, I needed to depend on qemu-system | qemu, since there was no other ways to pull needed BIOS files. It seems the situation changed, and that I could depend on less stuff from the qemu package. Maybe only the package named "etherboot" and "vgabios". To do that, my plan is to simply package a folder named: /usr/share/xen/qemu with in

Hi, When I first built my Debian package, I needed to depend on qemu-system | qemu, since there was no other ways to pull needed BIOS files. It seems the situation changed, and that I could depend on less stuff from the qemu package. Maybe only the package named "etherboot" and "vgabios". To do that, my plan is to simply package a folder named: /usr/share/xen/qemu with in

On Wed, Jun 26, 2013 at 01:48:03PM -0400, Alexandre Rebert wrote: > 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. xen-utils-4.1 is not in unstable, so this is not really helpful. > The bug report that will be submitted to the bug tracker is available at the > following

Hi, I'm trying to solve this one: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615797 As much as I can tell, and unless I have missed something, the issue is a missing -lpulse in the Makefile.target (see attached diff file that fixes the issue). While my patch makes it compile again, I fear that I'm not doing well, and that there must be a better way to fix, that would take care of

Hi, I'm trying to solve this one: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615797 As much as I can tell, and unless I have missed something, the issue is a missing -lpulse in the Makefile.target (see attached diff file that fixes the issue). While my patch makes it compile again, I fear that I'm not doing well, and that there must be a better way to fix, that would take care of

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:

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

Il 27/04/2011 14:37, Ian Campbell ha scritto: > Which specific revision of qemu-xen-4.1 are you using? I'm using a tarball from http://bits.xensource.com/oss-xen/release/4.1.0/xen-4.1.0.tar.gz It seems Thomas used the tools/ioemu-qemu-xen subdirectory as source for xen-qemu-dm. At a first glance I didn't notice debian/mypatches/add-rules.patch: it adds Rules.mk from the tools

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

Hi, I''m trying to build a xen-qemu-dm-4.0 package to support the HVM part of the Xen 4.0 package that will be soon in Debian experimental. When I start an HVM domain, I have the following subject line of this thread in my /var/log/xen/qemu-dm-XXXX.log file, and then it stops here. Any idea what I should do to fix? Thomas P.S: my build is using a clone of

[message cross posted to the pkg-xen and xen-devel list] Dear everyone, Bastian Blank - which is the person (among others, but mainly him) that is packaging Xen in Debian -, has decided last summer that he doesn't want to deal with the qemu-dm of Xen, thus removing Xen Qemu and support for HVM in Debian. Here is what he wrote:

[message cross posted to the pkg-xen and xen-devel list] Dear everyone, Bastian Blank - which is the person (among others, but mainly him) that is packaging Xen in Debian -, has decided last summer that he doesn't want to deal with the qemu-dm of Xen, thus removing Xen Qemu and support for HVM in Debian. Here is what he wrote:

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

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:

Hi, Me and another sysadmin has independently been researching a problem where DomU randomly locks (Can’t reach it via xl console, no ping / SSH connection, shown as stuck in running-state in xentop) on two of our separate machines (installed completely independently): Dom0: Debian 7.0 with Xen version: 4.1.4 and xen-utils 4.1.4-3+deb7u1 Debian 7.1 with Xen version: 4.1 DomU: 7.0 7.1(.3)

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-2 This is related to Bug#699237: Huawei E220 does not work under Debian Wheezy Mainboard Gigabyte Z77X-D3H, 32GB RAM Xen dom0: Debian Wheezy 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux - affected 3.2.0-4-amd64 #1 SMP Debian 3.2.39-2 x86_64 GNU/Linux - affected Bus 001 Device 004: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA

Hi everyone at the security team, I'd like to upload an update of xen-qemu-dm-4.0 in Squeeze. Below is the Xen Security Advisory as I received it, attached is the patch that they provided. Both the debdiff and the updated packages are available in here: http://archive.gplhost.com/pub/security/xen-qemu-dm-4.0/ Please allow me to upload this fix. If you wish, I can prepare a DSA as well (but