Have a look at the vmprofessional website.
You can find the information on how to create a boot CD which contains a list of different esx host details. You can modify it to suit your specific requirements.
Hope this will help you.
1 person found this helpful
If installing 400 esx server you may want to consider installing over PXE (network), and serve the ks.cfg file from a web-server.... You can also do the cdrom-installation you're using alread and serve the ks-files on a web-server. You'll need to specify an ip-adress then (ks=http://184.108.40.206/ks.cfg) You can even generate a kickstart files on the fly based on the ip-adress the http request is coming from.
But to answer your question: Check out this page:
You probably want to use the following:
ks=hd: in that file system (for example,
Note: The second colon is a syntax change for Red Hat Linux 9.
As far as I know ESX is based on RHEL7, so you may want to skip the second colon... This guy seems to agree with me:
I have managed to work out how to get the ks.cfg to run from the hard disk partition (hardware being HP DL380 G5) with the syntax being ks=hd:cciss/c0d0p1:/ks.cfg
Now I'm trying to figure out how to load the files in to the RAMDISK and access them from the kickstart file.
I am using PXE to push out an image to the HP servers (pre ESX install) , but the image will be over written by the ESX install so I am needing to load things in to the RAM DISK and access them from there. I am also trying to minimise the dependency of other services on the build process. I currently have the CD-ROM files and post install files being transferred from an ftp server, but this is not always reliable. If I can remove the ftp dependency, the build process will go lot smoother.
1 person found this helpful
The RAMDISK is your / filesystem during install. In your %pre, you'll need to create a mount point for your PE partition, copy the files to another location, and umount.
In %post, you'll need to run in a nochroot'd environment to access the ramdisk.
I've run into lots of problems with anaconda by staging the installation files on a HD, be prepared to spend some time on this if you are deadset on this method. Network-based installs are much, much easier.
I'm not sure why you're focused on the ramdrive.
If you have the files on a harddrive already, you may want to use the files directly from that partition:
You probably need something in your kickstart file like:
harddrive --partition=cciss/c0d0p1 --dir=/install-tree
(make sure you have two separate lines)
Older versions of redhat only accepted CDrom iso files, i'm not sure what ESX expects though. For files that you have added manually you may need to mount the harddrive agan in the post-script. Try something like:
mount -t vfat /dev/cciss/c0d0p1 /tmp/cdrive