I'm trying to perform a scripted install of ESX 4. I took the ks.cfg file created during the install, put it on a web server, and made sure I could access it with my browser. I also modified it so it would clear the partitions on install. I then booted from the ESX 4 install CD, pressed F2, and appended the following to the boot options:
ks=http://server.example.com/ks.cfg vlanid=1
Yet when I continue, I eventually receive a cryptic error message that says "No COS NICs have been added by the user." The only mention of this that I can find here on the discussion forums refers to PXE booting which I am not doing. I am booting and installing from the CD.
I also tried:
ks=http://server.example.com/ks.cfg vlanid=1 ip=x.x.x.x netmask=x.x.x.x gateway=x.x.x.x nameserver=x.x.x.x
And receive the same message. Any ideas about what is wrong?
I am having the same problem. Did you figure it out?
Have you tried created a cooked ESX 4 iso, with all the ks.cfg's for all servers in it then when you boot the .iso/cd you simply select the Server to build?
It's crossed my mind but I haven't tried it yet.
Yes, I figured it out. I was able to press ALT-F1 and noticed that there were errors on that console. It stopped because it already saw a VMFS partition. I used fdisk to remove the partitions, rebooted, and tried again. It then worked properly.
You can also add --overwritevmfs to the clearpart line in your kickstart config rather than using fdisk each time.
clearpart --overwritevmfs --initlabel --firstdisk=local
The no COS NICS error is more like a warning, as weasel
will continue with the kickstart and use the first pNIC available.