Update: This whitepaper is now available on Microsot.com at http://download.microsoft.com/download/1/4/d/14d17804-1659-435d-bc11-657a6da308c0/VSvsVPC.doc. Thanks to those of you who gave me comments on the draft.
Here's a draft of a whitepaper I'm working on that will ultimately be posted on Microsoft.com. Comments and suggestions would be appreciated. Thanks!
** This information is provided as-is with no warranties. **
This whitepaper explains the difference between Virtual PC and Virtual Server, and discusses when you would use one versus the other. Virtual PC is Microsoft's virtual machine solution for desktop applications, and Virtual Server is its solution for server applications. While they share many features in common, because of their different usage scenarios, a number of their features are different.
Virtual PC provides an optimal experience for a desktop user who wants to run one or more additional desktop operating systems on his or her PC. The user interface is fairly simple and there is extensive integration between the host operating system running on the physical computer and the guest operating systems running in virtual machines. For example, users can easily drag and drop data between virtual machines and their host. In addition, the sound and display features of virtual machines are much the same as physical computers. On the other hand, Virtual Server provides features to support the requirements of enterprise server applications and administration. For example, due to more stringent security requirements, there is less integration between the host and guest operating systems. Virtual Server also provides a number of features to support greater manageability, scalability, and extensibility.
The fundamental difference between Virtual PC and Virtual Server is that Virtual PC is designed for desktop (or "client" or "PC") operating systems and Virtual Server is designed for server operating systems.
While the two products have many features in common, they serve different needs, so there are crucial differences between them as well. For example, because it supports desktop applications, the Virtual PC user interface is designed with the typical desktop user in mind. The configuration options are relatively simple and easy for the average computer user to understand and use. On the other hand, Virtual Server is designed for running enterprise server operating systems and applications. It provides the configuration and management options that are required for server management, and these necessarily make the user interface more complex. As a result, making effective use of Virtual Server requires some degree of knowledge of server technologies.
As already mentioned, Virtual PC is designed for running desktop operating systems and applications. Some primary usage scenarios for Virtual PC are:
These scenarios are described in detail in the Microsoft Virtual PC 2004 Technical Overview white paper, available the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkId=45404. The uses that you can find for Virtual PC are limited only by your resourcefulness, though. For example, you might set up Virtual PC for your family to use for browsing the Internet. That way you don’t have to worry about anything they download because it won’t affect the host operating system. If the virtual machine becomes corrupted or infected with a virus, you can simply delete it and start over.
Virtual Server is designed for running enterprise server operating systems and applications. Some primary usage scenarios for Virtual Server are:
Virtual Server and Virtual PC have a number of features in common, such as:
While they share many features in common, due to the different usage scenarios there are also a number of differences between Virtual Server and Virtual PC, which are described in this topic.
To support the requirements of desktop users, Virtual PC provides the following features that are not available in Virtual Server:
To support the requirements of an enterprise environment, Virtual Server provides the following features that are not available (or needed) in Virtual PC:
For Virtual Server, supported host and guest operating systems are server operating systems, except for Windows XP Professional, which is supported as a host operating system. Supported host operating systems are Windows Server 2003 (Standard, Enterprise, and Datacenter Editions), Windows Small Business Server (Standard and Premium Editions), and Windows XP Professional. Supported guest operating systems include these plus Windows 2000 Server, all editions except Enterprise as well as Windows NT Server 4.0 Enterprise Edition SP6a. See the Virtual Server documentation for more information.
RAM. Support for up to 3.6 GB RAM per virtual machine.
Two-node clustering. Virtual Server provides simple two-node failover from one virtual machine to another for testing and development.
The following are references to additional information and resources for using Virtual PC and Virtual Server.
nice article - informative and direct.
good work. This will be really useful for customers approaching Microsoft virtualization.
I reported the paper on my blog.
Correction: Need to change "Software Management Services" to "Systems Management Server 2003 SP1"
Clarification: Need to change "Multi Processor Support" to "Host Multi Processor Support"
Got it. Thanks Jules!
Very helpful paper. Looks good!
My only suggestion would be to expand a little on the part about Virtual Server's only being able to utilize one processor on the host machine. Does this apply to physical processors or virtual processors or both? What kind of impact does this have on virtual machines. Does this same limitation exist for Virtual PC?
Virtual Server can take advantage of up to 32 physical processors on the host. Each running virtual machine can use up to one CPU. So, for example, you could have 31 running virtual machines, each using one CPU, with the host operating system using one CPU. Virtual PC can take advantage of only one physical processor (which makes sense, given that it's rare to find a multi-processor desktop machine).
Does this clear things up?
I am currently updating my&nbsp;slidedeck for the webcast I'm doing this Friday on Virtual Server bringing...
Great paper - I'm going to add it to the TAM Newsletter for May 2005 :)
Great article (*)! Need to raise a couple of points for clarification:
1. this paper was published officially May 2005 (per article) but did not include any key VPC 2004 SP1 info released in Oct 2004 (e.g. Win Server 2003 Standard as host, improved Win XP SP2 support as guest): http://www.microsoft.com/windows/virtualpc/downloads/sp1.mspx
2. Win 2000 Server and Win Server 2003 are not explicitly listed as supported guest OS under VPC 2004 (Pg 8 in this paper), neither in this paper nor online (last update November 10, 2003) at http://www.microsoft.com/windows/virtualpc/evaluation/overview2004.mspx and http://www.microsoft.com/windows/virtualpc/evaluation/sysreqs.mspx
W2k3 as guest has been a feature in several MS Learning "Instructor-lead" MOC courses (VPC 2004) for sometime now.
3. same as #2 above but for Windows Small Business Server 2003 (SP1 as well?).
4. in this paper section 'Shared Features' on Pg 7, can the 'certain limitations' be expanded on?
Thanks a lot!
Please visit above URL for comments / further inquiry to this feedback, if any (select 'Feedback', do not forget to supply your contactable Email). Note: no option to specify commentator's Email address as non public field here.