Do a custom installation of ESX and make your swap partition 1024 MB instead of the default 542 MB. Later you will need the room when you have to increase your service console memory from 272 MB to 512 (800 MB Max) to keep your systems from crashing when you access them from within a service console window.
If you have a VMware best practice that will help someone, please post it in our best practice forum! Thanks!
Revised on 1-3-09:
The above is only for ESX 3.0.x. VMware has redesigned the volume structure for ESX 3.5.x to include the larger volumes. The large SWAP volume is only standard on clean installs of 3.5.x, upgrades of previous versions will have the smaller volumes. Best practice for upgrading ESX is to do a clean install to remove old version limitations.
Then when running the installation make the following changes and additons to the default volumes:
- /boot | ext3 | 250 MB
- /swap | swap | 2000 MB (largest accessible size) Once this is changed you must increase service console memory in VirtualCenter 2:1 (swap:ram)
- / | ext3 | 5120 MB
- /var | ext3 | 1024 MB (core files)
- /var/log | ext 3 | 1024 MB (logfiles)
- /tmp | ext3 | 1024 MB (where updates get downloaded to)
- /opt | ext3 | 2048 MB (where HA log go)
- / home | ext3 | 1024 MB (user files)
Originally posted 2008-05-23 17:26:22. Republished by Blog Post Promoter
Recent Comments