Both Microsoft Virtual Server 2003 and Vmware Server are free virtual server hosts offering very similar features.
I have recently had the (mis)fortune of attempting to configure one of my personal servers as a Virtual Machine host in an attempt to consolidate all my servers and reduce my IT spend.
I currently have (separate) servers that fulfill the following roles:
- Mail (Microsoft Exchange) Server
- Web Server
- Inbound/Outbound Mail Exchange
Whilst having these applications on separate physical machines increases redundancy, it creates a rather large monthly IT spend.
What I intend to do is to convert my Mail Server (Running Windows 2003) into a Virtual Machine host and then migrate all roles onto separate Virtual Machines. This also includes migrating the Exchange Server from the Host onto a Virtual Machine so as to minimize downtime.
My initial thought was to run Vmware as the Virtual Host platform, however this had some rather significant drawbacks:
- Creating a new Virtual Machine disk locked the server up for 10 to 15 minutes.
- The Linux installer would hang if any other Virtual Machine was running at the time of install.
- Virtual Machine Guests were noticeably latent.
- The Virtual Console requires a client to be installed.
In an attempt to resolve these problems, I tried Microsoft Virtual Server 2003.
The Virtual Server 2003 installer was faster, and Virtual Machines significantly more responsive. Creating a new Virtual Machine takes a matter of seconds with no noticeable adverse effects on the Virtual Machine Host.
Microsoft Virtual Server 2003 also comes with a rather nice web interface where you have full console access.
I admit that the latency problems may be partially caused by the fact that the Host has not yet had a RAM upgrade! It is currently running with 1GB DDRII instead of the 3GB it will have before being commissioned properly.
It appears that Microsoft win this one! Their Virtual Server platform appears to be rather awesome.
It has been suggested that I should use xen instead, however the constraint of running on a Windows 2003 Server Host Operating System has resulted in this being impossible.