Microsoft KB Archive/930217

From BetaArchive Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


You experience slow performance when you use Windows Server 2003 with Service Pack 1 as a guest operating system in Virtual Server 2005

Article ID: 930217

Article Last Modified on 12/4/2007



APPLIES TO

  • Microsoft Virtual Server 2005 Standard Edition



Beta Information

This article discusses a Beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this Beta product. For information about how to obtain support for a Beta release, see the documentation that is included with the Beta product files, or check the Web location where you downloaded the release.

SYMPTOMS

In Microsoft Virtual Server 2005, you experience slow performance when you use Microsoft Windows Server 2003 with Service Pack 1 (SP1) as a guest operating system.

CAUSE

Windows Server 2003 SP1 is not a fully supported guest operating system in Virtual Server 2005. Virtual Server 2005 R2 SP1 will add support for guest operating systems that are running Windows Server 2003 with SP1.

RESOLUTION

We do not recommend that you use Windows Server 2003 with SP1 as a guest operating system in the original release version of Virtual Server 2005. This issue will be fixed in Virtual Server 2005 R2 SP1.

The Beta 2 version of Virtual Server 2005 R2 SP1 is available on the following Microsoft Web site:

To resolve this problem, apply Virtual Server 2005 R2 SP1, and then reinstall Virtual Machine Additions in each guest operating system that is running in Virtual Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

833139 How to install Virtual Machine Additions on a virtual machine


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Keywords: kbtshoot kbprb kbexpertiseinter KB930217