Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I seem to be unable to perform a kickstart installation of centos5.8 with a netinstall. It correctly gets into the text installer, but keeps sending out a request for the dhcp server and failing. I have tried to manually set the IP everywhere. Here is my pxelinux.cfg file


LABEL centos5.8-net
        kernel /images/centos5.8-net/vmlinuz
        MENU LABEL centos5.8-net
        append initrd=/images/centos5.8-net/initrd.img ip= netmask= hostname=client101 gateway= ksdevice=eth0 dns= ks=

MENU end

and here is my kickstart file:

# Kickstart file for a very basic Centos 5.8 system
# Assigns the server ip:
# DNS,
# London TZ

url --url http://mirror.centos.org/centos-5/5.8/os/i386
lang en_US.UTF-8
keyboard us
network --device=eth0 --bootproto=static --ip= --netmask= --gateway= --nameserver=, --hostname=client1-server --onboot=on
rootpw --iscrypted $1$Snrd2bB6$CuD/07AX2r/lHgVTPZyAz/
firewall --enabled --port=22:tcp
authconfig --enableshadow --enablemd5
selinux --enforcing
timezone --utc Europe/London
bootloader --location=mbr --driveorder=xvda --append="console=xvc0"
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
part /boot --fstype ext3 --size=100 --ondisk=xvda
part pv.2 --size=0 --grow --ondisk=xvda
volgroup VolGroup00 --pesize=32768 pv.2
logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=528 --grow --maxsize=1056
logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow


Here is my dhcp file:

ddns-update-style interim;

allow booting;
allow bootp;

ignore client-updates;
set vendorclass = option vendor-class-identifier;

subnet netmask {
        host tower {
                hardware ethernet          50:E5:49:18:D5:C6;
                fixed-address    ;
                option routers   ;
                option domain-name-servers,;
                option subnet-mask;
                filename                   "/pxelinux.0";
                default-lease-time         21600;
                max-lease-time             43200;
                next-server      ;

Is it impossible to prevent it asking for a dynamic ip before trying to install from the net? Perhaps there is an error in of my files?

My dhcp server is set to ignore client-updates, and is set to only works with one mac address whilst testing.

share|improve this question
Once the centos installer is running, do you have the option to drop to a shell and test if eth0 exists? It's possible the installer doesn't support your NIC. –  1.618 Dec 14 '12 at 16:09
Sorry 1.618 I didn't see your comment earlier it was hidden. You were on the right track. It turns out that my server had two ethernet cards, and one of them would not be 'recognized' by Centos. I get the message 'unable to find any devices of the type needed for this installation' when I tried to manually do it with http install, however it was able to pxe boot to that. I am going to try again with using the other card, and changing the MAC to match. I will have to probably change some eth0s to eth1s. –  Programster Dec 14 '12 at 16:32

1 Answer 1

try pinging the ip you are setting, you can also set ksdevice=eth0 (if that's where the appropriate network cable is plugged) try switching them, they might be coming up in a different order.

As far as I know you can't explicitly disable DHCP, DHCP will fallback if for some reason the static setup fails. If it can't reach the kickstart file, it will assume the interface isn't up, it'll fallback.

share|improve this answer
Thanks Ben, it did turn out to be the fact that the network device was not recognized in centos 5.8 (see my earlier comment under the question) but was pxe booted from into the installer. Strangest issue ever for me. Unfortunately the other NIC is not pxe bootable. Is there a way to mark this question as 'solved'? I apologize for the fact that it turned out to just be a hardware issue and not a software configuration. –  Programster Dec 15 '12 at 15:54

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.