Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is it possible to run VMWare Server v2 on Windows Home Server? Is this the best virtualization product for a home environment that wants a 24x7 virtual development OS/Server?


locked by HopelessN00b Dec 5 '14 at 3:55

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

closed as off topic by Bryan, MDMarra, Magellan, mdpc, Dennis Kaarsemaker Jun 8 '13 at 15:38

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

Yeah, but you'd be better off running ESXi on the hardware and WHS on top of that.

I am not familiar with ESXi - does it allow me to "dedicate" one or more physical drives for WHS (as AFAIK WHS needs to manage the entire drive - not a virtual drive). – Brad Leach Apr 30 '09 at 12:59
ESXi is very picky when it comes to what hardware is supported. – Edmund Tay May 2 '09 at 14:51
Unless you have a 64-bit machine listed on the HCL it's a real crap shoot (it has to be 64-bit though). – Scott Keck-Warren Feb 15 '11 at 18:54

If you haven't used virtualization, VMWare Server v2 is a good starting point. If learning and ease of use is your goal, then stick with Server v2. If performance is your goal, ESXi will give you more as it does not have the overhead of the Windows OS having to load into memory and CPU calls having to be translated though the OS.

If your WHS uses RAID, you will likely lose it on ESXi as it is unlikely that ESXi will support your setup. I could be wrong on this, so it is best to check on VMWare forums.

Considering that WHS explicitly disrecommends use of RAID, the last shouldn't be a problem. – Orihara May 15 '09 at 17:25

I'd recommend VirtualBox over VMWare Server 2.x for what you're trying to do (ie, virtualization ontop of a Host OS, rather than bare-metal virtualization).

The VMWare Server product will be hitting it's EndOfLife fairly soon (mid-2011 if I remember correctly, if it hasn't been already). This is the reason I'm converting my development/home VMs away from Server 2.x.

Another good reason is that VirtualBox does away with that bastard of a web-based UI that you're stuck with for Server 2.x.

If you have access to MSDN/Technet, you might want to consider running a Hyper-V server and virtualize your WHS instead. This is the way that I'm solving the home virtualization problem. I went with Hyper-V because I know it's stable, solid and with the amounts of money Microsoft is spending on it, it'll be around for quite a while. VirtualBox looks decent, and I'm sure it's fully functional, but I'm just more confident in the Hyper-V solution.


The newest type 2 (hosted) hypervisor solutions offered by VMware, which I would use instead of VMware Server, are VMware workstation or VMware Player.

Workstation is a pay solution and closer to an enterprise level solution.

Player is more so the replacement, I think, of VMware Server.

Both of these solutions do away with the web browser interface that Peter isn't a fan of... and of course neither was I. Both of them are solid solutions for personal use. Also as stated above, if you are trying to run a home business and/or get great performance ESXi might be a better solution.


Only just spotted your 24x7 requirement, only one VMWare product can offer that sort of reliability and that's ESX/ESXi - try that instead.


Not the answer you're looking for? Browse other questions tagged or ask your own question.