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.
1 person found this helpful
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.
Hmmm...thanks for the pointer to the file - A Hacking-I-Will-Go...
Will report back with success or failure.
Solution:1) Download a Hex editor - Here is a free one: http://www.hhdsoftware.com/free-hex-editor2) You will need to stop the background vmware-processes before you can save your changes - terminate the processes before you try to edit the file!3) Make a backup copy of the file C:\Program Files (x86)\VMware\VMware Workstation\vmwarebase.dll4) Open the file with the hex editor: C:\Program Files (x86)\VMware\VMware Workstation\vmwarebase.dll5) This is a DLL - Dynamic Link Library, so the file size and entry-point locations matter - do NOT insert or remove bytes or you will break it!6) You can however alter the file as long as you don't make it bigger or smaller.7) Do a find (Ctrl-F) and look for /boot - what we want is the 6th occurance (F3 to move ahead) - It will look like this:.part /boot--size 50.partswap --recommended.part / --size3000 --grow --maxsize 4000.part/home --size 1000 --grow.A couple of notes here - this is the section we have to work with - If you only want to increase the size of the /boot partition, you canincrease it to 99 here safely - that is still a pretty small boot, but at least you can fit a couple of kernels in it - however the /partition is also constrained to minimum of 3 gigs and a maximum of 4 gigs - Weird defaults!Here is what I did to fix it - I switched it to autopart so that the OS would set up the partitions based on the size of the disk. Here is whatit looks like fixed:.autopart.The periods are ASCII Code 0a - make sure you replace everything between the two .'s with plain old spaces - and again, make sure that you don'tchange the file size. Save the file and then open up the VMware Workstation console and if it starts up, you probably did it right.Here is a sample of the auto-partitioning schemes that CentOS came up for various Virtual Disk Sizes:/boot / /home20Gig 524Meg 19Gig N/A64Gig 524Meg 33Gig 33Gig128Gig 524Meg 54Gig 81Gig256Gig 524Meg 54Gig 219Gig512Gig 524Meg 54Gig 493Gig1TB 524Meg 54Gig 1.1TBI actually put in 20, 64, 128, 256, 512, and 1024 in the Disk Size box - It looks like VMware adds about 10% additional on to the number you specify.It also looks like CentOS thinks that 54Gig is all you will ever need for / - I wonder what the other Linux Distro's will do...Enjoy - I will update this post if I find other patches to be made to the file for other Distro's.Greg