Moins, just for clarification:
"network NFS DHCP boot fails on multiple NIC machine" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/182940 "initramfs-tools: Network configuration can't work with multiple interfaces" http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467078 Regards, \sh On Mon, 23 Nov 2009 15:30:40 +0100 Steffen Grunewald <steffen.grunew...@aei.mpg.de> wrote: > On Mon, Nov 23, 2009 at 03:22:30PM +0100, Michael Goetze wrote: > > Toomas Tamm wrote: > > > On Sun, Nov 22, 2009 at 01:38:16PM +0100, Thomas Lange wrote: > > > > > >> * bootoption ethdevice: use specified network device for network > > >> booting (PXE) instead of default (being eth0). Feature > > >> contributed by Helge Wagner. Usage example: ethdevice=eth1 > > > > > > Does anyone know/remember, why the problem cannot be fixed > > > properly, i.e. make live-initramfs try all interfaces and use the > > > first one where a DHCP reply is obtained? > > > > > > This used to be possible with fai-kernels under etch, so why is > > > it not possible with live-initramfs? > > > > Red Hat's Kickstart also does this, I agree it would definitely be > > much nicer. > > > > However, lacking that, the ethdevice boot option would at least be > > better than what we have now... > > I suppose there is no chance to find out which interface had been > used for the actual PXE booting? > For IPMI reasons, eth0 of multi-homed machines may be a public > interface and eth1 the "private" one which is connected to the > installation network. In such a case, the first DHCP response might > be returned from the public network even if PXE booting took place on > eth1. (which has preference in the BIOS boot order, btw) > > I still don't understand why we can't have back ip=::::::eth1 > > Cheers, > Steffen -- | Stephan '\sh' Hermann | OSS Dev / SysAdmin | | JID: s...@linux-server.org | http://www.sourcecode.de/ | | GPG ID: 0xC098EFA8 | http://leonov.tv/ | | FP: 3D8B 5138 0852 DA7A B83F DCCB C189 E733 C098 EFA8 |
