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


Re: [Xen-users] Network problem: packets are lost in domU

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Network problem: packets are lost in domU
From: Marduk <xen@xxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 22 Feb 2007 08:24:23 -0600
Delivery-date: Thu, 22 Feb 2007 06:23:49 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070222140906.GA9640@xxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20070222140906.GA9640@xxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2007-02-22 at 15:09 +0100, Jacek Konieczny wrote:
> My system configuration:
> in domain config file:
>         vif = [ 'ip=' ]
> in xend-config.sxp:
>         (network-script 'network-route netdev=dummy0')
>         (vif-script     'vif-route netdev=dummy0')
> dom0 interface setup:
> # ip addr show dev dummy0
> 10: dummy0: <BROADCAST,NOARP,UP> mtu 1500 qdisc noqueue
>     link/ether 1a:aa:f1:3f:c5:4e brd ff:ff:ff:ff:ff:ff
>     inet scope global dummy0 

I'm not sure if the config you shows is supposed to be for bridging or
PtP, but this response assumes bridging.  If that's not the case then
just ignore.

For bridging your network-script should be 'network-bridge' instead of

Also for bridging dummy0 should be in promiscuous mode.

I really don't know how the Xen networking scripts work, I usually set
up the host-side networking manually (using the host OS's networking
tools) and let Xen handle the domU side.

Probably doesn't help but maybe this provides some clues.


Xen-users mailing list

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