Lately I’ve been testing scripted builds of ESX hosts and several other tools like RDA. Because of this I had to reinstall my ESX hosts several times. Sometimes I actually had to completely delete them before I could start over again. You can consider this blog posting as a note to myself, this way I can do a simple search on my own blog when everything is screwed up again:
- Create Virtual Machine, Custom
- WS 6.5 Compatibility
- Linux Kernel, other
- Number of processors: 2
- Memory: 1024
- Bridged Networking (change to team later on)
- LSI Logic
- New disc, SCSI
- 6GB, pre-allocated, single file
- Customize hardware, remove: soundcard, usb, floppy
set execution mode to: Intel VT-x - Edit .vmx and add the following:
ethernet0.virtualDev = "e1000"
monitor_control.restrict_backdoor = "true" - Install ESX
- Add VM to Team and select “LAN 1″ for networking(keep the test vm’s completely isolated)
vSphere 4.0 Quick Start Guide
Hi Duncan – Would you mind advising what are the specs of your home lab for your ESX environment (that runs within Workstation)?
What would you recommend for a home lab that runs within workstation? Something that will allow a few test VM’s… test SRM etc
I did this a while back so that I could play around with ESX within VMware Fusion. I talked about it here: http://www.brianmadden.com/forums/t/30171.aspx#111942
I run a X61 Lenovo DualCore laptop(with VT) with 4GB memory. I guess memory is the most important part of running all the esx hosts and VT technology is also important. I guess any whitebox with 4GB and a decent processor should be fine to run at least 2 hosts and virtualcenter!
Duncan,
Thanks for posting, this is something I have not yet tried, and I linked to this on my blog because of that.
Roger L
http://rogerlunditblog.blogspot.com/
http://www.vmadmin.co.uk/index.php/resources/35-esxserver/88-esxinworkstation