similar to: Processed: Traffic forwarding issue between Xen domU/dom0

retitle Traffic forwarding issue between Xen domU/dom0 thanks This week again this bug occurred again so we are trying to create some kind of reproduce algorithm. First we've created two virtual machines named koekiemonster.bofh.hq.mendix.net and netappsim.bofh.hq.mendix.net. We've added 29 vifs to koekiemonster.bofh.hq.mendix.net. During this tests we've always had a ping

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-5.2 Hi, We're seeing weird behaviour regarding network traffic between a Xen dom0 and domU. I reported this issue yesterday to the openvswitch-discuss mailing list, but it seems this could also be a (regression?) bug in the xen hypervisor or the linux kernel... (we've upgraded xen-hypervisor-4.0-amd64 4.0.1-4 -> 4.0.1-5.2 and

Processing commands for control at bugs.debian.org: > retitle 773561 /etc/init.d/xen fails when run in a nested L1 hypervisor dom0 (Xen on Xen) Bug #773561 [xen-utils-common] /etc/init.d/xen fails when run in a guest, causing postinst to fail. Changed Bug title to '/etc/init.d/xen fails when run in a nested L1 hypervisor dom0 (Xen on Xen)' from '/etc/init.d/xen fails when run in a

Obviously i meant hyperthreading. Probably need more coffee:) -- Frank Baalbergen - System / Network Administrator T +31 (0)10 2760434 | frank.baalbergen at mendix.com | www.mendix.com

Hi list, We, an OSS advocacy group, setup a Xen 3.1 machine composed of : . a 64 bits dom0 running Debian stable amd64 . 2 hvm domUs running OpenBSD amd64 . 2 hvm domUs running NetBSD i386 This machine is to be hosted and reachable from the Internet, but it will only have one public IP. Naturally, our first tought was to port-forward using iptables / netfilter. We didn''t really

Processing commands for control at bugs.debian.org: > reassign 603727 linux-2.6 Bug #603727 [xen-hypervisor-4.0-amd64] xen-hypervisor-4.0-amd64: i386 Dom0 crashes after doing some I/O on local storage (software Raid1 on SAS-drives with mpt2sas driver) Bug reassigned from package 'xen-hypervisor-4.0-amd64' to 'linux-2.6'. No longer marked as found in versions xen/4.0.1-1.

Processing control commands: > reassign -1 src:linux Bug #577788 [src:xen] dom0 kernels should suggest irqbalance Bug reassigned from package 'src:xen' to 'src:linux'. Ignoring request to alter found versions of bug #577788 to the same values previously set Ignoring request to alter fixed versions of bug #577788 to the same values previously set > retitle -1 SMP kernels

Processing commands for control at bugs.debian.org: > found 602378 4.0.1-1 Bug #602378 [src:xen] xen-hypervisor-4.0-amd64: Live migration of Guests crashes and reboots Marked as found in versions xen/4.0.1-1. > found 679533 4.0.1-5.2 Bug #679533 [src:xen] Traffic forwarding issue between Xen domU/dom0 Marked as found in versions xen/4.0.1-5.2. > found 660882 4.0.1-4 Bug #660882 [src:xen]

Hi, I am using xen 3.1.3 on a Celeron, a netbsd 4.0 dom0, and netbsd 4.0 and slackware 11 (with 2.6.18.8-xen kernel) domU''s, and a bridge to communicate between those. I noticed traffic between (both ways) netbsd dom0/domU is rather slow (4Mb/s max), and traffic from the linux domU to dom0 is about 18Mb/s, while traffic from dom0 to the linux domU is rather slow again (4Mb/s max). Any

Processing commands for control at bugs.debian.org: > reassign 679533 src:xen Bug #679533 [xen-hypervisor-4.0-amd64] Traffic forwarding issue between Xen domU/dom0 Bug reassigned from package 'xen-hypervisor-4.0-amd64' to 'src:xen'. No longer marked as found in versions 4.0.1-5.2. Ignoring request to alter fixed versions of bug #679533 to the same values previously set >

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 Severity: normal Xen Networking[1] works by creating a new pair of virtual ethernet interfaces (vifN.M in dom0 and ethM in domU with id N) and connecting then by an internal "crossover ethernet cable". My understanding of the "internal crossover" thing is that networking statistics should be the same no matter if you measure

Processing commands for control at bugs.debian.org: > forcemerge 369042 503287 Bug #369042 [src:xen] xen-utils-3.0: does not work with 32.bit userspace and 64-bit kernel Bug #369042 [src:xen] xen-utils-3.0: does not work with 32.bit userspace and 64-bit kernel Marked as found in versions xen/4.3.0-3. Added tag(s) upstream and moreinfo. Bug #503287 [src:xen] xen-3: domU's wont start when

Processing commands for control at bugs.debian.org: > retitle 674137 Please make bind port configurable Bug #674137 [xcp-xapi] xcp-xapi: default ports in xapi Changed Bug title to 'Please make bind port configurable' from 'xcp-xapi: default ports in xapi' > severity 674137 wishlist Bug #674137 [xcp-xapi] Please make bind port configurable Ignoring request to change severity

Processing commands for control at bugs.debian.org: > retitle 519149 xen-3: only loads bzImage domU kernels, not dom0 Bug#519149: xen-3: does not really load bzImage kernels. Changed Bug title to `xen-3: only loads bzImage domU kernels, not dom0' from `xen-3: does not really load bzImage kernels.'. > thanks Stopping processing here. Please contact me if you need assistance.

Hello all, I''m in the process of installing my first Xen server. I have a dom0 installed (CentOS 5) with public & private IPs. I created a domU (RHEL 4). I left the networking setup at defaults, so I believe it''s using bridging; I have a virbr0 device in dom0 with an private IP on a new subnet, and domU has an IP on that private subnet. From the domU, I can ping dom0,

Hello, I''m a new user to Xen, so please be patient with me. I just installed a dom0 on my root-server and I also got a xenU to work with routed network. I can access from both sides and I can access both machines from any other computer too. So far - so good.. (gentoo on both ends by the way) My plan was to use a mounted NFS-directory from dom0 on my domU to place /home (and later

How do I assign a public ip address for Dom0 and then a separate one for DomU? I wanna do this so I can get some practice using ssh from dom0 to DomU. I wanted to interact between the two to get some good networking experience using all sorts of protocols between the two. Anyhow, I have eth0 on dom0 as dhcp. So when peth0 comes up during the network-bridge script, which then turns into eth0 on

Hi list, following my last mail I added a small jpg to clarify my request... How do I have to configure my dumm0 to enable communication between my firewall domU and my dom0. As mentioned I can ping/ssh from outside to domU (FW), I can ping ssh from there to domU(2.1) and domU(2.2). But I can''t get through to dom0. As most of the basic understanding is missing on my side even a

Hopefully I summed up the jist of the problem in the subject line. ;) I have a GFS cluster with ten Xen 3.0 dom0s sharing an iSCSI LUN. There are on average 8 domUs running on each Xen server. The dom0 on each server is hard-coded to 2 CPUs and 2GB of RAM with no ballooning, and has 2GB of partition-based swap. When creating a new domU on any of the Xen servers, just after the completion of

Hello. Is it available a communication interface between Dom0 and DomU to get some parameteres about DomU without connection via ssh? For example i need to get information about IP addresses that are allocated in DomU. I found following mail-thread: http://xen.1045712.n5.nabble.com/How-to-get-domU-IP-address-td2510278.html Keir Fraser said about xenstore, but as i understand to use xenstore