Kickstarting VMWare ESX 4.1 (Error: No NIC with name bootif)

Posted by William on Server Fault See other posts from Server Fault or by William
Published on 2010-11-16T20:52:32Z Indexed on 2011/01/02 17:55 UTC
Read the original article Hit count: 506

Filed under:
|
|
|
|

I'm having an issue kickstarting an installation of VMWaare ESX Classic 4.1. I've stripped down my kickstart a bit to just:

accepteula

keyboard us

auth

clearpart --firstdisk --overwritevmfs

url --url=10.16.0.1/cblr/ks_mirror/esx-classic-4.1.0-260247

rootpw --iscrypted $1$zZJa3g7g$mD8d.6QgbPku1QovQTAps/

timezone 'US/Pacific'

network --addvmportgroup=true --device=vmnic0 --bootproto=dhcp

part '/boot'  --fstype=ext3 --size=1100  --onfirstdisk
part 'none'  --fstype=vmkcore --size=110  --onfirstdisk
part 'datastore1'  --fstype=vmfs3 --size=8920 --grow  --onfirstdisk

virtualdisk 'esxconsole' --size=7920 --onvmfs='datastore1'

part 'swap'  --fstype=swap --size=916 --onvirtualdisk='esxconsole'
part '/var/log'  --fstype=ext3 --size=2000 --onvirtualdisk='esxconsole'
part '/'  --fstype=ext3 --size=5000 --grow --onvirtualdisk='esxconsole'

%post --interpreter=bash

However, when I attempt to use this kickstart during a PXE install with no additional kernel options, I get the following error:

There was a problem with the Network Device specified on the command line.
Error: No NIC found with name bootif

If I comment out the network line in the kickstart, the error changes to:

There was a problem with the Network Device specified on the command line.
Error: No NIC found with name eth0

How can I fix this? Thanks.

© Server Fault or respective owner

Related posts about networking

Related posts about vmware