Xen users - Sep 2006 - Howto start domU''s network (gentoo-specific)?

Dom0 comes up fine (Linux 2.6.16.26 + Xen 3.02).
xenbr0 is ok (peth0 and vif0.0 attached).
On dom0 I made links net.vif1.0 thru net.vif7.0
to /etc/init.d/net.l0 (otherwise the hotplug stuff
does not start the vif-interface).
On dom0 I run dhcpd on eth0 (can not make him
listen on peth0, vif0.0 or xenbr0 because no
ip-address).
DomU-config contains vif = [ ''mac=00:16:3e:00:00:03'' ]
and dhcpd is prepared to give a fixed ip-address to
that mac-address.
When I start domU, xend is sending dhcp-requests
on behalf of vif1.0 (or vif2.0, etc.) but does
not get an offer from dhcpd. So the domU network
does not come up (the vifn.0 IS attached to xenbr0).

What am I missing?
TIA, Hans.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hans de Hartog wrote:
> Dom0 comes up fine (Linux 2.6.16.26 + Xen 3.02).
> xenbr0 is ok (peth0 and vif0.0 attached).
> On dom0 I made links net.vif1.0 thru net.vif7.0
> to /etc/init.d/net.l0 (otherwise the hotplug stuff
> does not start the vif-interface).
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)
> On dom0 I run dhcpd on eth0 (can not make him
> listen on peth0, vif0.0 or xenbr0 because no
> ip-address).
That is ok, peth0 is a fork of eth0.
> DomU-config contains vif = [ ''mac=00:16:3e:00:00:03'' ]
> and dhcpd is prepared to give a fixed ip-address to
> that mac-address.
> When I start domU, xend is sending dhcp-requests
> on behalf of vif1.0 (or vif2.0, etc.) but does
> not get an offer from dhcpd. So the domU network
> does not come up (the vifn.0 IS attached to xenbr0).
What does your dhcpd.conf in the dom0 and thru /etc/conf.d/net in the domU
look like?

MfG
Matthias


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

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;
	fixed-address 10.0.0.3;
}

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.

Hans.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hans de Hartog wrote:
> 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.
I use Gentoo and don''t have to ''ln -s'' my
vif''s to net.lo, and on all my
machines i don''t get something behind the device name.

What is your configuration for eth0?
>>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;
> 	fixed-address 10.0.0.3;
> }
> 
> 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.
I haven''t recognized that you use Kernel 2.6.16.26, which i also tried
but with
no success.

Could you try Kernel 2.6.16.16 ? This works for me.

I haven''t figured out why i can''t get run my xen config with
2.6.16.26 but with
2.6.16.16. Same kernel configs, same xen configs, only another kernel and
*bummm*, non working dom0 and non working domU''s.

Regards
Matthias


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Matthias Wolf wrote:
> I use Gentoo and don''t have to ''ln -s'' my
vif''s to net.lo, and on all my
> machines i don''t get something behind the device name.
>   
I am using gentoo + xen, and I can confirm that this is not
needed
> I haven''t recognized that you use Kernel 2.6.16.26, which i also
tried but with
> no success.
>   
running 2.6.16.26 (xen 3.0.2) and 2.6.12.6 (xen 3.0.0) and never had
to do anything extra ordinary.

One notethough, don''t start your network with /etc/init.d/net.eth0
bring
only the lo up, when xend start it will bring up the interface.

Ming-Wei

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users