Using a kickstart file that stops with a curses dialog "You have multiple network devices on this system. Which one do you want to install through?"
The machine being configured with PXEboot has two ethernet interfaces. What's missing from the network entries below? I'd like this install to proceed without asking which ethernet interface.
PXE begins the install with DHCP, so Kickstart should already know which of eth0, eth1, etc. to use.
Here is the ethernet line in the ks.cfg file:
network --device eth0 --bootproto dhcp
Any ideas appreciated.
=======Keith
On Tue, 2008-02-05 at 12:51 -0800, Keith Christian wrote:
Using a kickstart file that stops with a curses dialog "You have multiple network devices on this system. Which one do you want to install through?"
The machine being configured with PXEboot has two ethernet interfaces. What's missing from the network entries below? I'd like this install to proceed without asking which ethernet interface.
PXE begins the install with DHCP, so Kickstart should already know which of eth0, eth1, etc. to use.
Here is the ethernet line in the ks.cfg file:
network --device eth0 --bootproto dhcpAny ideas appreciated.
=======Keith
On the boot line (i.e. where you'd put ks=http://....), add DEVICE=ethX where X=interfaceNumber. We've also noticed that adding noipv6 speeds up some network auto-detection stuff too.
--Tim ________________________________________________________________________ < It isn't easy being a Friday kind of person in a Monday kind of world. > ------------------------------------------------------------------------ \ \ \ \ /\ ( ) .( o ).
Keith Christian wrote:
PXE begins the install with DHCP, so Kickstart should already know which of eth0, eth1, etc. to use.
add ksdevice=eth0 to your kernel parameters, or eth1 if you want to use eth1. This works for me anyways.
nate
yeah, it can be a bit daunting at first, but the below info is right. also consider down the road if you are using PXE/DHCP that there can be conflicts, so PXE to eth0, kickstart to eth1, that sort of thing.
-krb
nate wrote:
Keith Christian wrote:
PXE begins the install with DHCP, so Kickstart should already know which of eth0, eth1, etc. to use.
add ksdevice=eth0 to your kernel parameters, or eth1 if you want to use eth1. This works for me anyways.
nate
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
In your pxelinux config file:
add ksdevice=bootif
also add "IPAPPEND 2" to the end of the file
In your kickstart file, don't specify a device: "network --bootproto dhcp"
-Jay
Karl R. Balsmeier wrote:
yeah, it can be a bit daunting at first, but the below info is right. also consider down the road if you are using PXE/DHCP that there can be conflicts, so PXE to eth0, kickstart to eth1, that sort of thing.
-krb
nate wrote:
Keith Christian wrote:
PXE begins the install with DHCP, so Kickstart should already know which of eth0, eth1, etc. to use.
add ksdevice=eth0 to your kernel parameters, or eth1 if you want to use eth1. This works for me anyways.
nate
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Jay Hilliard wrote:
In your pxelinux config file:
add ksdevice=bootif
also add "IPAPPEND 2" to the end of the file
In your kickstart file, don't specify a device: "network --bootproto dhcp"
-Jay
Karl R. Balsmeier wrote:
yeah, it can be a bit daunting at first, but the below info is right. also consider down the road if you are using PXE/DHCP that there can be conflicts, so PXE to eth0, kickstart to eth1, that sort of thing. -krb
nate wrote:
Keith Christian wrote:
PXE begins the install with DHCP, so Kickstart should already know which of eth0, eth1, etc. to use.
add ksdevice=eth0 to your kernel parameters, or eth1 if you want to use eth1. This works for me anyways.
nate
There is some handy information here too if you need it.
http://fedoraproject.org/wiki/Anaconda/Kickstart http://fedoraproject.org/wiki/Anaconda/Options
-Ross-
Jay Hilliard wrote:
In your pxelinux config file:
add ksdevice=bootif
also add "IPAPPEND 2" to the end of the file
In your kickstart file, don't specify a device: "network --bootproto dhcp"
-Jay
Karl R. Balsmeier wrote:
yeah, it can be a bit daunting at first, but the below info is right. also consider down the road if you are using PXE/DHCP that there can be conflicts, so PXE to eth0, kickstart to eth1, that sort of thing. -krb
nate wrote:
Keith Christian wrote:
PXE begins the install with DHCP, so Kickstart should already know which of eth0, eth1, etc. to use.
add ksdevice=eth0 to your kernel parameters, or eth1 if you want to use eth1. This works for me anyways.
nate
--device=
Used to select a specific Ethernet device for installation.
Note that using --device= will not be effective unless the kickstart file is a local file (such as ks=floppy), since the installation program will configure the network to find the kickstart file. For example:
network --bootproto=dhcp --device=eth0
Extracted from one of the pages I sent earlier.
-Ross-
Hello all,
I have something strange... And I'm not sure this is the best form... so suggest another if you prefer.
I have a CentOS (and a Fedora) box with 100+ vlan's. When I boot to run level 3 and startx, X gives a stack trace, pauses for a few seconds and I can use my computer again.
I can have 84 vlans and from run level 3, startx. 85 or more and I cannot startx. Assuming that it has something to do with the number of interfaces, there are 2 nics, 1 lo and the vlans.
I can have all vlans on and boot to run level 5 successfully.
Obviously I have a work around for this, so this is mostly a curiosity thing.
Any thoughts?
--- Keith Christian keithchristian@yahoo.com wrote:
Using a kickstart file that stops with a curses dialog "You have multiple network devices on this system. Which one do you want to install through?"
I'll check them out for my next server build, and I'll reply to this thread.
I appreciate the replies.
=====Keith
-
Jay Hilliard -
Karl R. Balsmeier -
Keith Christian -
Milton Calnek -
nate -
Ross Cavanagh -
Timothy Selivanow