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] Re: NIC and domU - direct attach

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: NIC and domU - direct attach
From: Christian Tramnitz <chris.ace@xxxxxxx>
Date: Mon, 05 Oct 2009 16:51:46 +0200
Delivery-date: Mon, 05 Oct 2009 07:52:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4ACA03E4.4080506@xxxxxxxxxx>
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>
References: <4AC63FF3.40009@xxxxxxxxxx> <90eb1dc70910021155i326a5088k48889965b81d54a8@xxxxxxxxxxxxxx> <4ACA03E4.4080506@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Windows/20090812)
William wrote:

 > you can simply not give a public IP to the Dom0.  it doesn't need IP
 > to do the bridging.

Can you explain me this ?
I have two network cards in my domO and I used this command to create a new bridge for for dom1 :
/etc/xen/scripts/network-bridge start vifnum=10 netdev=eth2 bridge=eth2

But it doesn't work, if the host interface isn't configured.


You have to "up" the interface in dom0 to make it available for the bridge script, but there is no need to assign an IP to that bridge in dom0. Depending on the distribution you are using this may work out of the box or you may have to setup a manual "ifconfig eth2 up" somewhere...

Best regards,

Xen-users mailing list