Op 12-10-2013 0:19, Brian C. Lane schreef:
On Fri, Oct 11, 2013 at 02:59:02PM -0400, Jeremy Eder wrote:
Hi all,
The servers I have have a large number of NICs. Anaconda is waiting 120 seconds on each NIC for DHCP, even if there is no link. Only one NIC, em1, has a cable attached. This is on a lab network and em1 gets a DHCP address just fine.
So far we've tried:
ip=em2:off ip=em3:off etc...but anaconda bails on this to emergency dracut shell despite what's on this page https://fedoraproject.org/wiki/Anaconda_Boot_Options?rd=Anaconda/Options
Then we tried dhcptimeout=10 ... but that only seems to apply to the first NIC. subsequent NICs take 120s.
Also tried ksdevice=em1 ... worth a shot even though we're not kickstarting.
Then someone showed me this: http://wwoods.fedorapeople.org/doc/boot-options.html#_ip
So I tried adding this:
ip=:::::em1:dhcp ip=:::::em2:off ip=:::::em3:off ip=:::::em4:off bootdev=em1
But no luck, em2,em3,em4 still waiting 120sec on each. I understand the ip:::::em1:dhcp might conflict with the "only one interface" thing on the page above.
But...we need one interface to be dhcp in order to install. So, what's the correct way to have the install commence immediately when dhcp succeeds on the first NIC ? Thanks.
Could you file a bug with logs? add rd.debug to the cmdline and capture
the output. I'm guess this is probably an issue with dracut.
Isn't bug #1008076 also related to this?
Koos.
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list