[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] [SOLVED] domU PXE boot with bridge

  • To: xen-users@xxxxxxxxxxxxx
  • From: Alexandre Kouznetsov <alk@xxxxxxxxxx>
  • Date: Mon, 13 Aug 2012 10:22:43 -0500
  • Delivery-date: Mon, 13 Aug 2012 15:24:41 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>


El 11/08/12 22:48, Raj Mathur (ààà ààààà) escribiÃ:
Is there a better way, e.g. by somehow forcing gPXE to sleep for some
time before it tries the DHCP?

In any case, now our automated Debian install is working for bridged
domU VMs.  Hope this is useful to others with the same problem.

By default, at least in Debian, when you attach a network interface (vif, in this case) to a bridge, there is delay before the packets are forwarded to the newly attached interface. The delay time is configurable via interfaces file or brctl utility.

There was a thread about this 2012-04-03 08:42. I quote the relevant part:
> Other thing you should have in mind if you use bridged network,
> is gPXE's timeout vs bridge forward delay. In short, by default
> gPXE get desperate of not getting DHCP answer before the bridge
>  become operation, and fails to boot. Can be fixed manually with
>  "brctl setfd $BRIDGENAME 5" or in your network configuration file.
> I don't use network-bridge script, my Debian's
>  /etc/network/interfaces looks like this (note that Dom0 has no
> IP on that interface in my setup):
> iface xenbr22 inet manual
>   bridge_ports eth1.22
>   bridge_stp off
>   bridge_fd 5

Alexandre Kouznetsov

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.