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] RESOLVED: Broadcom NetXtreme II (DELL 1950)

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] RESOLVED: Broadcom NetXtreme II (DELL 1950)
From: "Fajar A. Nugraha" <fajar@xxxxxxxxxxxxx>
Date: Wed, 10 Oct 2007 14:27:44 +0700
Delivery-date: Wed, 10 Oct 2007 00:28:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071010090735.V76706-100000@xxxxxxxxxxxxx>
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: <20071010090735.V76706-100000@xxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20070728)
Stefan de Konink wrote:
> When I put a tcpdump on the interface the only thing data came out was
> tap0. What is vif0.1 doing for Xen?
tap interface is created for HVM domains. A PV domain will only create

x -> domain ID
y -> interface index

vif0.1 is the netback for dom0's veth1
vif1.0 is the netback for domU's (domain ID 1) eth0

vethy and vif0.y is only created (in RH's case) after netloop driver is
loaded (which is the case after starting xend). Don't know about gentoo

In the default xend network-bridge script,
1. a bridge is created
xenbr0 -- vif0.0, eth0
2. transfer mac, ip, and routes to veth0
3. eth0 is renamed into peth0, veth0 renamed into eth0

The order is not excactly like that (see
/etc/xen/script/network-bridge), but you get the idea.
I think the purpose is compatibility, to allow applications that uses
eth0 continue to do so.

In practice the ip/route transfer and interface-renaming might cause
some problems for scripts that start before xend (early relsease of
RHEL5's cluster comes to mind), which is part of the reason why disabled
the default network-bridge and setup bridge/ip address using standard RH
config files.



Xen-users mailing list