Surely this awesome product is not this brain-dead?
I am trying to set up CentOS 6 VM's and if I do the easy or the custom, it still generates and runs the autoinst.iso to do an easy install. This would be fine except no matter what size of disk I create I end up with a 48 MEGABYTE /boot - and of course when I try to do my first update to CentOS, there is a kernel update that bombs because there is not enough space on /boot FOR EVEN ONE MORE KERNEL!
48 Megs - are you kidding me?????
Yes, I know I can just remove the easy install files (autoinst.iso and autoinst.flp) and then do a manual install and do the partitioning correctly, but I like the easy set up - It's nice and consistent if I am creating VM's for production or customers.
What I need to do is fix the script that creates the kickstart file that does the partitioning and increase it to 256 Megs - I know I can edit the created autoinst.iso after the VM is created, but if I can fix the template, then no editing is necessary and I can use the easy install.
I have searched for two hours on Google and in the install directory and I can't find anyplace where the parameters are defined - Surely this is not hard-coded into the Executable?
How can I (Permanently) fix this?
I would just skip the whole autoinst.iso process. I have never used it myself.
When creating a new VM, select "Custom" and then select "I will install the operating system later". You will get full control over the installation process and can make your /boot partition any size you want.
Surely this is not hard-coded into the Executable?
Unfortunately it is hard coded! The file it's hard coded in is: vmwarebase.dll
My guess would be that it was probably supposed to be coded as "part /boot --size 500" but ended up "part /boot --size 50" and was probably a typo.