similar to: Bug#393609: xen-ioemu-3.0-unstable: Wrong location of /etc/xen/qemu-ifup prevents HVM domains to boot

Package: xen-ioemu-3.0-unstable Version: 3.0-unstable+hg11561-1 Severity: normal Hi, in #393609 /etc/xen/scripts/qemu-ifup is wrongly placed/referred. This script is missing from the amd64 package, making network enabled HVM domain not startable. Regards, L -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture:

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

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

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

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

Hello people, first of all this is my first mail and I am new to Xen so be nice with me :-) OK, I installed a Centos 5.5 in a system. Used yum groupinstall "Virtualization" to install anything related to Xen. Those packages installed:

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 =

Greetings xen gurus... I''m working with xen-3.0-testing downloaded on July 3, 2006. I have configured an hvm domain and want to use vif-route and network-route to configure the communication. The domU starts up fine. I was able to complete the installation of the OS (RHES3) and can restart the domain repeatedly. However, I cannot ping the network interface from dom0 using the

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

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

Hi All, I sent the patch to allow blktap to be able to booted as system bolume for PV-on-HVM. However, there was a problem that hdN and xvdN were not able to be specified at the same time. I made the patch to correct it as follows. - Whether hdN is defined first is checked. - If hdN is defined, xvdN is not replaced with hdN. Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com>

I assume this commit message was supposed to be "Enable VGA acceleration for VTI" right? We''re not actually accelerating CGA right? Regards, Anthony Liguori Xen patchbot-unstable wrote: > # HG changeset patch > # User kaf24@firebug.cl.cam.ac.uk > # Node ID e67432187b88ee60433779ad0f004b532ed378c8 > # Parent 639ad22eb7c80ac21c3958747b879892680bdaba >

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')

Hi, From cset 10921, ioemu: prefix is removed from disk config in /etc/xen/xmexample.hvm. Now HVM VBD driver is available, this thus raises a question: how would HVM domain know if one disk is a qemu-dm disk or a VBD disk? From current implementation, qemu-dm will recognize disk had, hdb, hdc, hdd, and VBD drive can recognize all disk (had~hdd, hde, hdf ...) . So the result is: qemu-dm will

Hello. I''m trying to set up hvm for linux or windows. I start with a very simple configuration without disks at all. but the virtual machine does boot or even "power up". If i remove the ioemu from the network device and specify type=brige or type=route everything goes fine, the boot process is starting but then I cant get network working in the guest.

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

Here is a patch to the Debian xen-3 3.4.0-1 package that reenables ioemu. I have been using it for the last four weeks. (I understand there are reasons this cannot go into Debian yet, but hopefully it will be useful to people that depend on running HVMs today.) Anders -------------- next part -------------- --- xen-3/debian/changelog +++ xen-3/debian/changelog @@ -1,3 +1,10 @@ +xen-3