Skip navigation

Category Archives: VMware Server

Another addition to my home lab is the HP DL360 G5. The specs are following:

2x Quad Core 3.0 Ghz CPUs

8Gb Ram

3x 146Gb SAS drives

1x Dual PCI-e NIC card.

2x PSUs

HP DL360  G5 (front)

HP DL360 G5 (rear)

I already installed ESXi5 on it,  conveniently the hardware is fully supported. It will probably used to host Check Point SPLAT firewall setups including a basic LDAP server.  I will then trunk the NICs to the Cisco switches to expand the environment. Fun stuff! 🙂

Recently i noticed that SAS and SATA are in fact compatible. SATA drives can be used to replace SAS drives but not vice versa. In fact, i decided to replaced one of the HP 146GB drives with a 300GB SATA Samsung i had running around. I can confirm it worked perfectly. What is important to note though, is the difference in rps the drives support. The SAS/HP drives are 10,000 while the ordinary 2.5′ drivers come in 5,400 or 7,200 which could make a significant performance difference in a production environment. However, in my case a 5400 rpm drive was enough for my lab, so long i increased the disk to a 300G. I haven’t tried the SATA drives with the HP smart array though –  this might introduce some issues.


Finally… the long awaiting VMware server 2 has been released and i have upgraded in under 20mins (this time!) All works like a charm, apart from one weird issue… ctrl-alt-del will not work in the console, since as soon as you press clt-alt, the cursor is released! WTF !!! Anyway. thanks God, the del key of the numeric pad works . .  pheewww.. i was already panicing… ! 🙂

Finally RC 2 has been released and i can say it finally fixes one major bug ie VMware console in firefox 3.0.* and fully compatible with IE7. 🙂 Another bug which has cropped up, is renaming the bridged interfaces does not seem to be possible. The default name seems to remain even though i specify the interface name manually. Before my interfaces were called –  Management, Vlan 1 and DMZ, now they seem to remain Bridge, Bridge (2) and Bridge (3) . . neah… i can live with it… but in RC1 this issue was not present!

I wanted to mount my windows Shares onto my VMware Sever (linux ubuntu) so that i can use it as an NFS and boot by VMs from the Windows Sever (since my windows server has a Raid Array) I tried several samba combinations but none seemed to work. CIFS seemed to do the trick.

Install smbfs

sudo aptitude install smbfs

Use the below command

mount.cifs //<ip address> </win_share> /mount/in/linux -o username=<username>,password=<password>


mount.cifs //$ /media/sdc1/ -o username=xxxxxxx,password=xxxxxxxxxxxx

To unmount use:


To mount it permanently:

vi /etc/fstab

add this entry:

//Server_ip>/share_name /path_to/mount_in_linux username=server_user,password=server_password,netdev 0 0

This is something i added onto my VMware Server, but obviously it can be used for any Debian distribution. I was not the one which came up with bash scripts, so below you may find the source.

I had installed previous versions of VMware Server but version 2 is the best in my opinion.

  1. Install Ubuntu Server (i am using a 64bit so my ubuntu and my vmware installations are all 64bit versions)
  2. run: sudo apt-get dis-upgrade
  3. run: sudo aptitude install build-essential xinetd
  4. run: uname -r
  5. take note of the value of the “uname-r”
  6. run: apt-get install linux-headers-“uname-r”
  7. Download Vmware Sever from   VMware-server-2.0.0-101586.x86_64.tar.gz VMware-vix-e.x.p-101586.x86_64.tar.gz
  8. Untar them with tar -zxvf <filename.tar.gz>
  9. run: cd vmware-server-distrib/
  10. run: ./  (this is will install the vmware core installation. It is pretty straight forward to follow)
  11. once done exit and move out of the folder, run: cd ..
  12. run: cd vmware-vix-distrib/
  13. run: ./ (this will install the vmware GUI web management interface)
  14. once done, Vmware is installed, but obviously some tweaking is required. run: /usr/sbin/ to run again the configuration wizard.

I decided to use 3 network cards (Nic1 –  management web , Nic2 – DMZ, Nic3 – Local Lan)

It is required to map vmnet”x” to the physical interface eth “y”) for such a setup,  since i am using bridging not NAT.

Once done, you can log into the vmware console via https://<ip address>:8333 (if port was left default)

This is more or less it. I also installed and configured the below, but these are optional:

  • NTP client (via ntpq daemon)
  • Samba to share between MS Windows (to move distributions iso files easily via file sharing and no CDs required)
  • Added Datastores (via VM Management Interface)
  • Automatic restart of Virtual Clients once VM Server starts up.

I also installed: open-ssh, vim tools, htop on the host (linux) since they are handy tools.