The existing threads for VS2005 (R2) all say that any performance bottlenecks are solved by install the VSAdditions, *after* the guest OS has been installed. The problem is that doesn't help me reduce the time taken to install the guest OS in the first place.
I'm new to VS, and my first install took 6 hours to copy the bloody setup files!! Then another day (a day???!!!) or so to do the actual OS install. All the time the disk subsystem was madly thrashing about like a shark attack victim. Hardware specs:
HP ML350 3Gb RAM, host OS working set is less than available physical RAM including 1Gb VS
RAID 5 on non-write caching smartarray 532 controller, 10k disks
VHD is autoexpanding and sits on the host boot drive (hey, I'm only testing at this stage)
Windows SBS2003 SP1 Host
Windows Server 2003 R2 Guest (that's what I had lying around)
Are there any useful tips for deploying Win2003 SP1 on a VS2005 R2 host that reduces the initial setup time?
Does a write-caching controller *significantly* improve this?
Does placement of the VHD file or using static VHD's *significantly* improve this?
After the VSAdditions were installed I am so far quite happy with the overall performance of both the Host and Guest.