mv -f /etc/vmware/esx.conf /tmp/esx.conf.bak
sed -e 's/boot\/memsize = \"272\"/boot\/mesize = \"800\"/g' /tmp/esx.conf.bak >> /etc/vmware/esx.conf
mv -f /boot/grub/grub.conf /tmp/grub.conf.bak
sed -e 's/uppermem 277504/uppermem 818176/g' -e 's/mem=272M/mem=800M/g' /tmp/grub.conf.bak >> /boot/grub/grub.conf
uppermem is (RAM * 1024) - 1024 = uppermem
VMware Communities User Moderator
*Virtualization is a journey, not a project.*
Wow. That was quick. I'll retest and get back to you.
VMware recommends running esxcfg-boot as well. I don't have my snippet of code handy will post it tomorrow, but I just wanted to point this out.
Because the method VMware gave us, as the official method per VMware, and it uses esxcfg-boot, which VMware also says should not be called from kickstart, as officially no esxcfg commands should be called from kickstart (cough, some are safe but not all), we do all our customization via custom script/service we wrote, which is invoked on first reboot after OEM load.
Here are the steps VMware explicitly gave us...
sed -i 's/memSize = \"272\"/memSize = \"800\"/g' /etc/vmware/esx.conf
It is similar to what sbeaver noted, but this must be done outside of %post
Just found out this in VC 2.5. VC -> select host->Configuration->Memory->Properties.
Didn't notice if it is in VC 2.0.1.
This begs the question on when the RCLI (Preferred in PowerShell set of course) will do this. If the RCLI does not do this or is not scheduled to do it in GA release, it definitely should. Also, I found what I believe is a bad bug in VC 2.5 or in 3i. See attached screen print. Doing this trick with 3i, I have server showing a NEGATIVE value for memory setting!
Begs the question, will this trick work in RCLI, if not if definitely should. In fact, VMwware should add this to the PowerShell bundle. Also, if you attempt this on 3i, it does not work? At least not on my 3i servers. On 3i, it displays a NEGATIVE value, and the properties interface crashes. Hey, VMware? Bug?
3i or VC 2.5 bug All.PNG 173.6 K
I use this and it works a treat
vimsh -ne "hostsvc/memoryinfo 838860800"
800 * 1024 * 1024