Vista - Windows Server 2008 Memory Allocation in VPC

I have Virtual PC 2007 SP1 running on a host which runs 32 bit Windows
XP, updated as recommended. The host has 4 GB of main memory, so
there's actually 3+ GB available. I want to run 32 bit Windows Server
2008 Standard so it performs as well as possible. There's not much I
want to run on the host other than the O/S and Virtual PC itself.

How much memory should I allocate to the virtual machine? How much
does XP and Virtual PC need to perform reasonably?

Is there some place where this kind of question has been discussed,
that could provide some general guidelines?

Thanks,

Jim

On Mar 31, 1:02*pm, jp...@xxxxxx wrote:Depends on usage.

For an useable office environment today you want at the bare minimum
512mb for Windows XP.
For heavy usage of Windows XP you want at least 2GB.

For Windows Server 2008 if your actually going to use it as a server,
serving files or whatever else then 2GB at least.
If your just going to play around with it in a VM then 1GB is fine I
suppose.....


So....

Since your running a VM on your computer using Windows XP then your
not the typical office user, so you'll need at least 1-1.5GB for your
host.
Use the remaining amount of memory for Windows 2008.

On Tue, 31 Mar 2009 10:02:11 -0700 (PDT), jpuls@xxxxxx wrote:
If you are going to run Win2008 Server as a virtual machine you should
go for VirtualServer2005R2 rather than VPC2007.

VirtualServer is optimized for server operations and it can start the
server with your host system so there is no need for logging in to the
XP host. Resource usage on the host is lighter, which means that you
get more resources for the virtual machine than you would get with
VPC2007.
Access to the server is easiest with Remote Desktop from any XP-Pro
SP3 machine on your network including the host.

As far as resources go:
- As much RAM as you can spare from your host
- Put the virtual disk (VHD file) on a separate disk drive on your
host. This means to use a physically separate disk drive so the drive
head arm does not have to jump about so much.
- Create a dynamically expanding disk with a *large* size! The VHD
file will only enlarge as you add more data so there is no footprint
problem at start. But you save yourself the hassle of upgrading to a
larger virtual disk later on.

--

Bo Berglund (Sweden)