similar to: Bug#393727: xen-ioemu-3.0-unstable-1-amd64: Missing /etc/xen/scripts/qemu-ifup

Package: xen-ioemu-3.0-unstable Version: 3.0-unstable+hg11561-1 Severity: normal When trying to create an HVM domain with vif settings enabled (as default) qemu-dm fails to start the virtual machine claiming that the tap device cannot be found. This is because qemu-dm tries to execute /etc/xen/qemu-ifup which is instead located in /etc/xen/scripts/qemu-ifup. As a side note qemu-dm seems to be

Hi folks There are two components, which are currently not included in the main utils package: ioemu, xenfb. ioemu is currently shipped in its own package, xenfb is not shipped at all. Should we fold them into the main utils package for simplicity? ioemu adds 300k to the package and 4300k in one dependency (libsdl1.2debian). xenfb adds another 200k to the package and 200k in one dependency

Processing commands for control at bugs.debian.org: > reassign 442380 xen-utils-3.2-1 Bug#442380: xen-utils-3.1-1: reenabled blktap support unusable Warning: Unknown package 'xen-utils-3.1-1' Bug reassigned from package `xen-utils-3.1-1' to `xen-utils-3.2-1'. > reassign 445243 xen-utils-3.2-1 Bug#445243: xen-utils-3.1: qemu-dm should be built with alsa support to avoid

Package: xen-hypervisor-3.0-unstable-1-amd64 Version: 3.0-unstable+hg11561-1 Severity: important The HVM domU won't start. The following is the config (comments stripped). --------------------begin-------------------- import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' kernel =

Package: xen-unstable Version: 3.0-unstable+hg11561-1 Followup-For: Bug #399700 The included patch overcomes the old build dependency on linux-support-2.6.17-2, and replaces it with linux-support-2.6.22-3. I filed a previous bug #453912 - but I guess it doesn't apply? -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable')

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal Under this Xen setup, (Linux) HVM guests fail to have network active when running with *routed* networking, as some hosting providers require (in my case, OVH). In this scenario: * the host is a described below * the guest runs as HVM. * the guest runs exclusively with ioemu; virtual network drivers are not available (vanilla lenny

Hello, I''m trying to get my first HVM domU installed (another Debian domU is already working under the same dom0). I intend to install the guest OS from a bootable CD-ROM. But when I create the new HVM domU with ''xm create xp1-cd.cfg'' , I don''t get the expected installation-window and find this in /var/log/xen/qemu-dm.6575.log: domid: 6 qemu: the number

Package: xen-hypervisor-3.0-unstable-1-amd64 Version: 3.0-unstable+hg11292-2 Severity: important My server is a dell 2950 server. Before the dom0 rebooting bug ocurred, xen was well even for hvm domU. By now i have tried xen-hypervisor-3.0-amd64 (3.0.2+hg9697-2) and xen-hypervisor-3.0-unstable-1-amd64 (3.0-unstable+hg11292-2), but both of them are unusable for me. for

tag 554805 + patch thanks The problem to solve is that qemu-ifup assumes the world is always bridged, and vif-routed does not know of the concept of TAP devices, and even if it did, it has at this point no way to get at qemu's TAP device anyway. The following set of patches help run in the ioemu-HVM situation: * xend-image.py.diff : modifies the HVM loader so that when running in

Hello, ioemu-qemu-xen directory under xen-unstable.hg/tools/ is missing in Xen Unstable version. Anybody has any idea how to get the ioemu-qemu-xen directory in Xen Unstable version. Thank you, Regards, Prashanth _______________________________________________ Xen-tools mailing list Xen-tools@lists.xensource.com http://lists.xensource.com/xen-tools

Hello, ioemu-qemu-xen directory under xen-unstable.hg/tools/ is missing in Xen Unstable version. Anybody has any idea how to get the ioemu-qemu-xen directory in Xen Unstable version. Thank you, Regards, Prashanth _______________________________________________ Xen-tools mailing list Xen-tools@lists.xensource.com http://lists.xensource.com/xen-tools

Package: xen-utils-3.0-unstable-1 Version: 3.0-unstable+hg11561-1 Severity: grave Justification: renders package unusable with the recent unstable kernel, the evtchn device should be created with major/minor 10, 63. Instead, it's being created with 10, 201. If fixed manually, xenstored will re-create it with the wrong minor number. This causes Xen to be entirely unusable, as xenstored is

Anyone else seeing problems with this combo? I'm running: linux-image-2.6.18-4-xen-686 2.6.18.dfsg.1-9 linux-modules-2.6.18-4-xen-686 2.6.18.dfsg.1-9 xen-hypervisor-3.0-unstable-1-i386-pae 3.0-unstable+hg11561-1 xen-utils-3.0-unstable-1 3.0-unstable+hg11561-1 xen-utils-common 3.0.3-0-2 When I try to fire up xend, it bombs.. doing some

Package: xen-utils-common Version: 3.0.3-0-2 Severity: important I have installed all the packages I can think of to get Xen going and it still fails with the following : /var/log/xen/xend-debug.log: Exception starting xend: (111, 'Connection refused') er.py", line 463, in process_request_thread self.finish_request(request, client_address) File "SocketServer.py",

# xm create -c vm01.cfg Error: Cannot open config file "vm01.cfg" www:/var/log/xen# xm create -c /etc/xen/auto/vm01.cfg Using config file "/etc/xen/auto/vm01.cfg". Error: (22, 'Invalid argument') # xm log [2006-10-24 16:16:30 xend.util.security 29229] INFO (__init__:1072) Resource label file not found. [2006-10-24 16:16:30 xend.util.security 29229] INFO

FYI: The status of the xen-unstable source package in Debian's testing distribution has changed. Previous version: 3.0-unstable+hg11292-2 Current version: 3.0-unstable+hg11561-1 -- This email is automatically generated; henning@makholm.net is responsible. See http://people.debian.org/~henning/trille/ for more information.

Regarding change #194: " Add /etc/xen/qemu-ifup to the ioemu package, which Nate says is useful... Btw should that be into scripts? Should it be a config file at all?" This is required to set up hvm domains - it gets called to set up the network interface. It'd probably make more sense to put it in scripts, but I'm not sure where the config file is that controls where it

Package: xen-hypervisor-3.0-unstable-1-i386 Version: 3.0-unstable+hg11561-1 Severity: important I've installed xen-linux-system-2.6.17-2-xen-k7 (version 2.6.17-9) on a server, and planned to run 3 Xen domUs on it. Creating the domUs was no problem, and running two of them works well. Starting the third one however will crash the dom0 and forces it to reboot. The machine is a Athlon64 3800+

At some point the Cirrus VGA driver was commented out. Probably for debugging. The patch below adds it back in. It works just fine. Signed-Off-By: Leendert van Doorn <leendert@watson.ibm.com> diff -ru xeno-unstable.orig/tools/ioemu/hw/pc.c xeno-unstable.mine/tools/ioemu/hw/pc.c --- xeno-unstable.orig/tools/ioemu/hw/pc.c 2005-05-25 07:48:57.000000000 -0400 +++

ioemu: Slown down refresh interval when SDL is minimized as that saves us the VGA refresh scanning. Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r c6cd384a48bf tools/ioemu/sdl.c --- a/tools/ioemu/sdl.c Tue Mar 04 12:32:31 2008 +0000 +++ b/tools/ioemu/sdl.c Tue Mar 04 15:34:25 2008 +0000 @@ -515,6 +515,15 @@ static void sdl_refresh(DisplayState *ds