Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VMware on Solaris
- Thread starter djr111
- Start date
I have three Solaris VMware sessions in production right now.
Overall I like it. Being a virtual session, some system statistics are no longer consistently accurate, but I suppose you can expect that. For instance, after I reboot a session it is not uncommon to see the load average at 200 - 300. The system is still very responsive and this only lasts for a few minutes, but still odd.
I'm running one wiki server for internal customers and two mail servers. As you can probably guess, they are all small sessions. It's nice to not have to support three physical machines though. Also the functionality of VMotion really makes these sessions highly available.
There are a couple of gotchas. I'd recommend a minimum of 1 GB of RAM for each session. I tried 256 MB and couldn't get WMware tools to run well. Among other things, VMware tools is necessary to get trending statistics on the VMware server side. I then tried 512 MB and updatemanager would fail during large patching processes. Now that I'm at 1 GB, I don't see either of these issues.
Also, the GUI updatemanager doesn't load on the system console if you have patch 121119-10 or above loaded and VMware tools installed. You can get around this by exporting your display to another system, uninstalling VMware tools, or just sticking with patch 121119-09.
Overall I like it. Being a virtual session, some system statistics are no longer consistently accurate, but I suppose you can expect that. For instance, after I reboot a session it is not uncommon to see the load average at 200 - 300. The system is still very responsive and this only lasts for a few minutes, but still odd.
I'm running one wiki server for internal customers and two mail servers. As you can probably guess, they are all small sessions. It's nice to not have to support three physical machines though. Also the functionality of VMotion really makes these sessions highly available.
There are a couple of gotchas. I'd recommend a minimum of 1 GB of RAM for each session. I tried 256 MB and couldn't get WMware tools to run well. Among other things, VMware tools is necessary to get trending statistics on the VMware server side. I then tried 512 MB and updatemanager would fail during large patching processes. Now that I'm at 1 GB, I don't see either of these issues.
Also, the GUI updatemanager doesn't load on the system console if you have patch 121119-10 or above loaded and VMware tools installed. You can get around this by exporting your display to another system, uninstalling VMware tools, or just sticking with patch 121119-09.
- Thread starter
- #3
- Status
Similar threads
- Locked
- Question