similar to: Bug#554805: patch to enable routed networking in HVM+ioemu

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

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

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:

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:

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

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-utils-common Version: 4.1.3-8 Severity: important When antispoof is set to 'on', the vif-common script does not create an ALLOW firewall rule for the emulated vif devices. This means that HVM nodes, unless a Xen PV driver is installed and running, cannot access the external network. The vif-common script creates an ACCEPT entry for the normal vif device (e.g. vif4.0) but not

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

Hello all I am setting up a Centos 6 machine with one network card & one onboard network port. Both are recognized & work. Onboard Network port is unused yet, but is required for dedicated access to LTSP LAN, which would allow older PIII machines to boot from this system. I have installed LTSP but again Networking seems to be the problem area, as the clients won't boot from this

Hi, I am unable to build libxl from the tools. I am getting always the following error. Disabling Werror did not solve the problem: === PCI passthrough capability has been enabled === === PCI passthrough capability has been enabled === make[4]: Entering directory `/usr/src/xen-unstable.hg/tools/ioemu-remote/i386-dm'' /usr/src/xen-unstable.hg//tools/cross-install -d -m0755 -p

At present IA64 Xen doesn''t support MSI for passthrough, so let''s not expose MSI/MSI-X capabilities to IA64 HVM guest for now. Thanks, -- Dexuan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Package: xen-utils-common Version: 4.0.0-1 Severity: important Tags: patch --- Please enter the report below this line. --- when you use "hardware" virtual machine (with qemu) with xen configured for bridging the network script treates a tap interface and then /etc/xen/scripts/qemu-ifup adds it to the bridge. That would be ok but tap interfaces have a random mac address and the bridge

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

On this system I have two nics If I look at the network connection There is nothing there. If I do ifconfig -a the two nics are there If I do ifup eth0 I get device doesn't seem to be present If I do ifup eth1 the system search to determine the IP information for this device. Do somebody have an idea to bring them up? --- Michel Donais

Hi,   I just upgraded the xen-hypervisor-3.2-1 package in Debian etch from the backports (3.2.1-2~bpo4+1) and now my HVM instance won''t boot any more. The error message in the log is:   -c config qemu network with xen bridge for tap0 xenbr0 bridge xenbr0 does not exist! /etc/xen/scripts/qemu-ifup: could not launch network script Could not initialize device

Package: xen-utils-common Version: 4.0.0-1 Severity: normal When a qemu hvm with vif=['type=ioemu,bridge=eth0'] is created, xen will successfully create the required vif and tap bridge interfaces, but will create the corresponding iptables filter rules for the vif interface only, not the tap interface. With a FORWARD policy of DROP (e.g. by enabling antispoofing) network traffic from/to

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

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

Hi everyone, as what I''ve learned form this link<http://wiki.xensource.com/xenwiki/blktap>, i know that when i specify tap:aio I’m actually using the blktap driver and finally using "tapdisk" to wirite to raw image file. but the truth is even when i delete /usr/sbin/tapdisk the domU can still boot on my machine with tap:aio protocol after a deeper look into the scene,

Hello, The modern (xkb) way of mapping the AltGr key (113) seems to be using the ISO_Level3_Shift keysym (0xFE03) instead of the obsolete Mode_switch keysym (0xFF7E). This patch let the "keysym to scancode" translator handle the ISO_Level3_Shift correctly, enabling the use of characters like ~#{[|`\^@]} on a french keyboard. Regards, Cédric diff -ur