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] Howto start domU's network (gentoo-specific)?

To: matze.wolf@xxxxxxx
Subject: Re: [Xen-users] Howto start domU's network (gentoo-specific)?
From: Hans de Hartog <dehartog@xxxxxxxxxx>
Date: Thu, 07 Sep 2006 17:13:26 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 07 Sep 2006 08:14:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <450028DB.3050406@xxxxxxx>
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: <4500220B.8050002@xxxxxxxxxx> <450028DB.3050406@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060813
Matthias Wolf wrote:

> You don't have to do this!
> The vif interfaces will be automatically started and added
> to the xenbr0 if you start a domU if you have configured xend-config.sxp
> with (standard) bridging:
> (network-script network-bridge)

Again, this is Gentoo specific. The network-bridge script tries to
figure out what netdev is by "ip route list default scope global"
and take the last word. On gentoo, the output of the command ends
with "... eth0 metric 2000". Therefore I use explicitly
(network-script 'network-bridge netdev=eth0').
If I don't make the links to net.vifN.0, I see in /var/log/messages
(on dom0) net.agent[pid]: add event not handled
and the vifN.0 is not brought up (but IS added to the bridge) and
it won't try dhcp.
> What does your dhcpd.conf in the dom0 and thru /etc/conf.d/net in the domU
> look like?
On dom0, /etc/conf.d/dhcpd contains DHCPD_IFACE="eth0"
and the relevant part in /etc/dhcp/dhcpd.conf:

host CARDHU {
        hardware ethernet 00:16:3e:00:00:03;

There is no specific configuration for net.vifN.0 (not on dom0 and not
on domU) and therefore it defaults to dhcp.
It also makes no difference if I include dhcp="dhcp" in the domU
configuration file om dom0, or not.


Xen-users mailing list