This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Network Problems

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Network Problems
From: Christian Bleicher <c.bleicher@xxxxxxxxxxxx>
Date: Fri, 10 Dec 2010 12:06:44 +0100
Delivery-date: Fri, 10 Dec 2010 13:44:59 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Die Lobby
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I'm new to XEN and have the following Problem:
If I shutdown my domU the network of the dom0 leaks. A ping from another
server to my xen dom0 shows a Packetloss > 80%. Then if I restart the
domU after some seconds the ping show a loss from 0%. I retryed that 3
times but it is really hard to go to the dom0 via ssh and recreate the
domU if the packetloss is that high.

I used google to search for that Problem, but couldn't find a really
matching result. Probably its a mistakte in the xen configuration, or a
bug in my xen version. I use a debian lenny dom0 with a debian lenny
dom0. The Network setup is brige. There are two domU on the system. My
dom0 is Kernel initrd.img-2.6.26-2-xen-amd64.

I installed xen via aptitude and my network/interfaces looks like:
# device: eth0
auto  eth0
iface eth0 inet static
#  post-up /sbin/ifconfig eth0 inet6 add 2a01:4f8:121:4302:0:0:0:1/64
#  pre-down /sbin/ifconfig eth0 inet6 del 2a01:4f8:121:4302:0:0:0:1/64

# default route to access subnet
# up route add -net netmask gw eth0
up route add -host gw
up route add -host gw
up route add -host gw

xm info:
serv01:~# xm info
host                   : serv01.xxx.de
release                : 2.6.26-2-xen-amd64
version                : #1 SMP Tue Aug 31 11:17:26 UTC 2010
machine                : x86_64
nr_cpus                : 8
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 2
cpu_mhz                : 2673
hw_caps                :
total_memory           : 8183
free_memory            : 3440
node_to_cpu            : node0:0-7
xen_major              : 3
xen_minor              : 2
xen_extra              : -1
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64 
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.3.1 (Debian 4.3.1-2) 
cc_compile_by          : waldi
cc_compile_domain      : debian.org
cc_compile_date        : Sat Jun 28 09:32:18 UTC 2008
xend_config_format     : 4

Had someone else that Problem, too? Do you need more information?

Thank you in advance. 



Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>