Sie sind auf Seite 1von 60

Hyper-V Release Notes

Applies To: Windows Server 2008

These release notes address known issues about Hyper-V. For other information, see Hyper-V.

Known Issues

The following are the known issues for the release of Hyper-V distributed as Hyper-V Update for Windows Server 2008 x64 Edition(KB950050) (http://go.microsoft.com/fwlink/? LinkId=139066). For known issues related to subsequent releases of Hyper-V, see the release notes for Windows Server.

Backup

The data on the physical disk attached to a virtual machine, or on the Internet SCSI (iSCSI) disk attached to the guest operating system will not be included in backup when a virtual machine has either a physical disk or an iSCSI disk attached. To fix this issue, utilize backup agents inside the virtual machine and individually back up each virtual machine as if it is a physical computer.

Virtual machines that have dynamic volumes inside the guest operating system are supported for offline backup only when the guest operating system is configured to use dynamic disks in Disk Manager. When attempting a backup of such a virtual machine, it is saved and subsequently resumed, during the backup process. Even if the virtual machine is running, only an offline backup is taken. To avoid this issue, when using online backup, one should only use a basic disk. To fix this, either use offline backups or convert the dynamic disk to a basic disk.

If you restore a Volume Shadow Copy Service (VSS) based backup of a virtual machine while it is running, the virtual machine may end up in an inconsistent state. To avoid this issue, ensure that the running virtual machine is not selected in the backup application before starting the VSS restore operation, ensure that the virtual machine is turned off prior to starting the VSS restore operation or, if doing a system-wide restore, ensure that all of the virtual machines are turned off.

Security

If the Hyper-V authorization store is located in Active Directory, then the removal of a user from a role does not take immediate effect. Either the server running Hyper-V (the computer that runs the Virtual Machine Management Service (VMMS)) or Active Directory needs to be rebooted to apply the changes. To avoid this issue, use an XML file as the store type. To fix this issue, reboot the Hyper-V server hosting VMMS, restart VMMS and Network Virtual Service Provider Windows Management Instrumentation (NVSPWMI) services or reboot Active Directory.

Operations

If you try to restart or reset a virtual machine when the physical computer is low on available memory, the virtual machine may be turned off instead of restarted. To avoid this issue, retain at least 512 MB of memory for use only on the physical computer. To fix this issue, you can try to start the virtual machine. If this does not work, you can modify the virtual machine settings to reduce the amount of memory assigned to the virtual machine.

While connecting through Virtual Machine Connection under a Remote Desktop session, the use of CTRL+ALT+DEL will not work. To avoid this, use CTRL+ALT+END, avoid using Virtual Machine Connection under Remote Desktop or use the CTRL+ALT+DEL options found on both the toolbar and Action menu.

You may encounter issues when attempting to attach virtual hard disks (VHDs) and ISOs to a virtual machine from a network share. To avoid this issue, ensure that both the Hyper-V server and the network server are members of the same domain. The network share requires read access for ISOs and read/write access for VHDs for both the user and computer account of the server running Hyper-V. If you are attempting this from a third computer (not utilizing the user interface on the server running Hyper-V), constrained delegation for Server Message Block (SMB) between the server running Hyper-V and the network file server must be enabled.

o

Storage

Hyper-V Getting Started Guide

Updated: July 1, 2009

Applies To: Windows Server 2008

Hyper-V™ is a role in Windows Server® 2008 that provides you with the tools and services you can use to create a virtualized server computing environment. This type of environment is useful because you can create and manage virtual machines, which allows you to run multiple operating systems on one physical computer and isolate the operating systems from each other. This guide introduces Hyper-V by providing instructions for installing this role and configuring a virtual machine.

In this guide

Requirements for Hyper-V

Hyper-V has specific requirements. Hyper-V requires an x64-based processor, hardware-assisted virtualization, and hardware data execution prevention (DEP). Hyper-V is available in x64-based versions of Windows Server 2008—specifically, the x64-based versions of Windows Server 2008 Standard, Windows Server 2008 Enterprise, and Windows Server 2008 Datacenter. For more information about the requirements, see the Hyper-V installation prerequisites

Known issues

Known issues are described in the release notes. We recommend that you review the release notes before you install Hyper-V.

To download the Hyper-V release notes, see http://go.microsoft.com/fwlink/?LinkId=98821. The release notes are also available in the Windows Server 2008 Technical Library

Step 1: Install Hyper-V

) . Step 1: Install Hyper-V Note Before you install Hyper-V, verify that your computer

Note

Before you install Hyper-V, verify that your computer has been updated with the release version of Hyper-V. The release version (RTM) of Windows Server 2008 included the pre-release version of Hyper-V. The release version of Hyper-V is offered through Windows Update as a recommended update, ‘Hyper-V Update for Windows Server 2008 x64 Edition (KB950050)’. However, you also can obtain the update through the Microsoft Download Center. To download this update, see http://go.microsoft.com/fwlink/?LinkId=123539. To determine whether the update has been applied to your computer, do one of the following:

On a full installation of Windows Server 2008, click Start, click Windows Update, click View update history, and then click Installed Updates.

On a Server Core installation, at the command prompt, type:

wmic qfe list

Look for update number kbid=950050, which indicates that the update for Hyper-V has been installed.

You can install Hyper-V on either a full installation or a Server Core installation. You can use Server Manager to install Hyper-V on a full installation, as described in the following procedure. To install on a Server Core installation, you must perform the installation from a command prompt. Run the following command:

Start /w ocsetup Microsoft-Hyper-V

the following command: Start /w ocsetup Microsoft-Hyper-V Note To manage Hyper-V on a Server Core installation,

Note

To manage Hyper-V on a Server Core installation, you can use the Hyper-V management tools to manage the server remotely. The management tools are available for Windows Server 2008 and Windows Vista Service Pack 1. For more information, see article 950050 (http://go.microsoft.com/fwlink/?LinkId=122188) and article 952627 (http://go.microsoft.com/fwlink/?LinkId=122189) in the Microsoft Knowledge Base.

To install Hyper-V on a full installation of Windows Server 2008

1. Click Start, and then click Server Manager.

2. In the Roles Summary area of the Server Manager main window, click Add Roles.

3. On the Select Server Roles page, click Hyper-V.

4. On the Create Virtual Networks page, click one or more network adapters if you want to make their network connection available to virtual machines.

5. On the Confirm Installation Selections page, click Install.

6. The computer must be restarted to complete the installation. Click Close to finish the wizard, and then click Yes to restart the computer.

7. After you restart the computer, log on with the same account you used to install the role. After the Resume Configuration Wizard completes the installation, click Close to finish the wizard.

Step 2: Create and set up a virtual machine

After you have installed Hyper-V, you can create a virtual machine and set up an operating system on the virtual machine.

Before you create the virtual machine, you may find it helpful to consider the following questions. You can provide answers to the questions when you use the New Virtual Machine Wizard to create the virtual machine.

Is the installation media available for the operating system you want to install on the virtual machine? You can use physical media, a remote image server, or an .ISO file. The method you want to use determines how you should configure the virtual machine.

How much memory will you allocate to the virtual machine?

Where do you want to store the virtual machine and what do you want to name it?

To create and set up a virtual machine

1. Open Hyper-V Manager. Click Start, point to Administrative Tools, and then click Hyper-V Manager.

2. From the Action pane, click New, and then click Virtual Machine.

3. From the New Virtual Machine Wizard, click Next.

4. On the Specify Name and Location page, specify what you want to name the virtual machine and where you want to store it.

5. On the Memory page, specify enough memory to run the guest operating system you want to use on the virtual machine.

6. On the Networking page, connect the network adapter to an existing virtual network if you want to establish network connectivity at this point.

Note

If you want to use a remote image server to install an operating system on your test virtual machine, select the external network.

7. On the Connect Virtual Hard Disk page, specify a name, location, and size to create a virtual hard disk so you can install an operating system on it.

8. On the Installation Options page, choose the method you want to use to install the operating system:

o

Install an operating system from a boot CD/DVD-ROM. You can use either physical media or an image file (.iso file).

o

Install an operating system from a boot floppy disk.

o

Install an operating system from a network-based installation server. To use this option, you must configure the virtual machine with a legacy network adapter connected to an external virtual network. The external virtual network must have access to the same network as the image server.

9. Click Finish.

After you create the virtual machine, you can start the virtual machine and install the operating system.

Step 3: Install the operating system and integration services

In the final step of this process, you connect to the virtual machine to set up the operating system. As part of the setup, you install a software package that improves integration between the virtualization server and the virtual machine.

between the virtualization server and the virtual machine. Note The instructions in this step assume that

Note

The instructions in this step assume that you specified the location of the installation media when you created the virtual machine. The instructions also assume that you are installing an operating system for which integration services are available.

To install the operating system and integration services

1. From the Virtual Machines section of the results pane, right-click the name of the virtual machine you created in step 2 and click Connect. The Virtual Machine Connection tool will open.

2. From the Action menu in the Virtual Machine Connection window, click Start.

3. Proceed through the installation.

Notes

o

When you are at the point where you need to provide input to complete the process, move the mouse cursor over the image of the setup window. After the mouse pointer changes to a small dot, click anywhere in the virtual machine window. This action "captures" the mouse so that keyboard and mouse input is sent to the virtual machine. To return the input to the physical computer, press Ctrl+Alt+Left arrow and then move the mouse pointer outside of the virtual machine window.

o

After the operating system is set up, you are ready to install the integration services. From the Action menu of Virtual Machine Connection, click Insert Integration Services Setup Disk. On Windows operating systems, you must close the New Hardware Wizard to start the installation. If Autorun does not start the installation automatically, you can start it manually. Click anywhere in the guest operating system window and navigate to the CD drive. Use the method that is appropriate for the guest operating system to start the installation package from the CD drive.

After you have completed the setup and integration services are installed, you can begin using the virtual machine. You can view or modify the virtual hardware that is configured for the virtual machine by reviewing the settings of the virtual machine. From the Virtual Machines pane, right-click the name of the virtual machine that you created in step 3 and click Settings. From the Settings window, click the name of the hardware to view or change it. For more

information, see Configuring Virtual Machines (http://go.microsoft.com/fwlink/?

Step 4: Configuring virtual networks

You can create virtual networks on the server running Hyper-V to define various networking topologies for virtual machines and the virtualization server. There are three types of virtual networks: a private network, which provides communication between virtual machines only, an internal network, which provides communication between the virtualization server and virtual machines, and an external network, which provides communication between a virtual machine and a physical network by creating an association to a physical network adapter on the virtualization server.

The following procedures provide the basic instructions for configuring virtual networks. For more information about designing and deploying virtual networks, see the deployment content for Hyper-V at the Windows Server 2008 TechCenter (http://go.microsoft.com/fwlink/?

To create a virtual network

1. Open Hyper-V Manager.

2. From the Actions menu, click Virtual Network Manager.

3. Under Create virtual network, select the type of network you want to create. The types of network are External, Internal, and Private. If the network you want to create is an external network, see “Additional considerations” below.

4. Click Add. The New Virtual Network page appears.

5. Type a name for the new network. Review the other properties and modify them if necessary.

Review the other properties and modify them if necessary. Note You can use virtual LAN identification

Note

You can use virtual LAN identification as a way to isolate network traffic. However, this type of configuration must be supported by the physical network adapter. For information about configuring virtual LAN identification, see the Hyper-V deployment content at the Windows Server 2008 TechCenter

6. Click OK to create the virtual network and close Virtual Network Manager, or click Apply to create the virtual network and continue using Virtual Network Manager.

To add a network adapter to a virtual machine

1. Open Hyper-V Manager. Click Start, point to Administrative Tools, and then click Hyper-V Manager.

2. In the results pane, under Virtual Machines, select the virtual machine that you want to configure.

4.

In the navigation pane, click Add Hardware.

5. On the Add Hardware page, choose a network adapter or a legacy network adapter. Network adapters can only be added to a virtual machine when the machine is turned off. For more information about each type of adapter, see "Additional considerations" below.

6. Click Add. The Network Adapter or Legacy Network Adapter page appears.

7. Under Network, select the virtual network you want to connect to.

8. If you want to configure a static MAC address or virtual LAN identifier, specify the address or identifier you want to use.

9. Click OK.

Additional considerations

By default, membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure. However, an administrator can use Authorization Manager to modify the authorization policy so that a user or group of users can complete this procedure.

A legacy network adapter works without installing a virtual machine driver because the driver is already available on most operating systems. The legacy network adapter emulates a physical network adapter, multiport DEC 21140 10/100TX 100 MB. A legacy network adapter also supports network- based installations because it includes the ability to boot to the Pre-Boot Execution Environment (PXE). The legacy network adapter is not supported in the 64-bit edition of Windows Server 2003 or the Windows XP Professional x64 Edition.

After you install Hyper-V and create an external virtual network, your computer will operate differently. After installation, the parent partition uses a virtual network adapter to connect to the physical network. When you look at Network Connections on the parent partition, you will see the original network adapter and a new virtual network adapter. The original physical network adapter has nothing bound to it except the Microsoft Virtual Network Switch Protocol, and the virtual network adapter now has all of the standard protocols and services bound to it. The virtual network adapter that appears under Network Connections will have the same name as the virtual network switch with which it is associated. It is possible to create an internal virtual network, which will expose a virtual network adapter to the parent partition without the need to have a physical network adapter associated with it. Hyper-V only binds the virtual network service to a physical network adapter when an external virtual network is created. However, networking will get disrupted for a short period of time on the network adapter when a virtual network gets created or deleted.

o

Comprehensive List of Hyper-V Updat

Hyper-V Update List for Windows Server 2008

Updated: September 15, 2010

Applies To: Windows Server 2008

The following table shows the list of software updates and hotfixes for Hyper-V in Windows Server 2008. Updates that are available on Windows Update are indicated, as well as the download location for those that are available at the Microsoft Download Center. These updates and hotfixes can help avoid some known issues and may save you a support call.

Note Some updates are required only under certain circumstances, as noted in the table. The updates for Windows Server 2008 Service Pack 2 (SP2) are applied automatically with the service pack, and do not need to be applied again. Also, you may want to see the list of updates for Hyper-V in Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkId=183395).

2008 R2 (http://go.microsoft.com/fwlink/?LinkId=183395). Comprehensive list of Hyper-V updates Knowl edge Base

Comprehensive list of Hyper-V updates

Knowl

edge

Base

Article

KB950

050

Name

”Hyper-

V

Update

for

Window

s Server

2008

x64

Edition”

(This is

the RTM

version

of

Hyper-

V.)

KB950 “A

182 compute

r that is

Date

6/26/2

008

4/11/2

008

Requir

ed?

Yes.

Yes, if

you

want to

File

Name

Windo

ws6.0-

KB950

050-

x64.ms

u

Windo

ws6.0-

KB950

Applie

s to

Windo

ws

Server

2008

Windo

ws

Server

Integrati

on

Services

Version

6.0.6001.

18016

Not

Applicab

le

Availa

bility

Link

Windo

ws

Update

Downl

oad

Center

KB951

308

running

an x86-

based

version

of

Window

s Server

2008 or

an x86-

based machin

version

of

Window

s Vista

may use

fewer

processo

rs than

expected uses a

if the

number

of cores

on a

socket is

not a

power of

2”

“Increas

ed

function

ality and

virtual

machine

control

in the

Window

s

2008

Failover ng.

Cluster

Manage

ment

console

for the

Hyper-V

role”

008

Failove

start an

x86-

based

virtual

e

running

Windo

ws

Server

2008 on

a

comput

er that

6-core

process

or.

182-

x86.ms

2008

u

Windo

ws6.0-

Windo

KB951

ws

x64.ms

u

2008

Yes, for

9/11/2

Server

r 308-v2- Server

Clusteri

Not

Applicab oad

le

Downl

Center

KB951

636

KB952

627

“Hyper-

V

Languag

e

Update

for

Window

s

2008”

“Descrip

tion of

the

Window

s

Service

Pack 1

Manage

ment

Tools

update

for the

release

version

of

Hyper-

V”

(Install

this to

enable

remote

manage

ment of

a

compute

r

Window

s

Server 2

008 with

the

Hyper-V

role

installed.

)

Pack

Server

Vista

running

KB953 “Error

585

message

6/26/2

008

6/26/2

008

9/4/20

08

Yes, if

you are

using

the

additio

nal

languag

es

offered.

Windo

ws6.0-

KB951

636-

x86.ms

u

Yes, to

enable

remote

manage

ment

using

the

Hyper-

V

Manage Varies

r

Micros

oft

Manage

ment

Consol

e

(MMC)

snap-in.

Yes, if

you are

Windo

ws6.0-

Windo

ws

Server

2008

Windo

ws

Server

2008

Windo

ws

Not

Applicab oad

le

Downl

Center

Not

Applicab oad

le

Downl

Center

Not

Applicab

KB953

828

when

you try to start a

Hyper-V

virtual

machine

on a

Window

s

2008-

based or

Window

Vista-

based

s

Server

compute

r

uses the

NUMA

architect

ure: "An

error

occurred

while

attempti

ng to

change

the state

of virtual

machine

VMNA

ME"”

“The

NLB

host

does not

converge

as

expected

on

Window

s

2008

Hyper-V

virtual

machine

s”

that

Server

6/25/2

008

using a

comput

er

running

Windo

ws

Server

2008

with

Non-

Unifor

m

Memor

y

Access

(NUM

A)

architec

ture.

KB953

585-

x64.ms

u

Yes, if

you are

using

Networ KB953

k Load

Balanci x64.ms

ng

(NLB).

Winow

s6.0-

828-

u

Server

2008

Windo

ws

Server

2008

le

Not

Applicab

le

“Hyper-

V

Update

for

Window

s Server

 

2008

 

x64

Edition”

 

Yes, if

(Install

this to

resolve

KB956 potential 9/23/2

589

issues

008

you are

using

System

Center

VMM 2

008 to

Windo

ws6.0-

KB956

589-

 

when

 

x64.ms

you

 

manage

u

manage

Hyper-V

with

your

environ

ment.

System

 

Center

Virtual

Machine

Manager

(VMM)

2008.)

KB956 “Update

9/8/20

Yes, if

Windo

697

for

08

the

ws6.0-

Window

Volume KB956

s

Server

Shadow 697-

2008

Copy

x64.ms

x64

Service

u

Edition”

(VSS)

(Install

is

this to

utilized

resolve

for

an issue

backup

in which

s.

the

Hyper-V

Volume

Shadow

Copy

Service

(VSS)

does not

Windo

Not

Downl

ws

Server

2008

Applicab oad

le

Center

Windo

Not

Windo

ws

Applicab ws

Server

le

Update

2008

,

Downl

oad

Center

back up

virtual

machine

s

properly.

)

“Update

for

Window

s Server

 

2008

 

Yes, if

the

x64

Edition”

(Install

this to

enable

manage

ment

operati

KB956 the

9/23/0

ng

710

Hyper-V 8

role to

system

has

 

more

 

support

 

up to 24

logical

processo

rs and

 

than 16

logical

process

ors.

192

 

virtual

machine

s.)

KB956 “Update

9/23/0

Yes, if

774

for

8

GUIDs

Window

are

s

Server

used

2008

 

instead

x64

of a

Edition”

drive

(Install

letter or

this to

mount

resolve

point.

the

 

scenario

where a

Backgro

und

Intellige

nt

Transfer

 

Windo

Windo

ws

710-v2- Server

ws6.0-

KB956

x64.ms

u

Windo

ws6.0-

KB956

774-

x64.ms

u

2008

Windo

ws

Server

2008

6.0.6001.

22258

Not

Applicab

le

Downl

oad

Center

Service

(BITS)

client

cannot

handle

files that

have

paths

that

contain

the

volume

GUID in

Window

s Server

2008.)

“Stop

error

message

on a

Window

s Server

2008-

based 10/8/2

KB957

967 compute

008

r that has

the

Hyper-V

role

installed:

"STOP

0x00000

01A"”

KB958 “You

065 cannot

configur

e a

Hyper-V

virtual

machine

by using

Window

s Server

2008

Failover

Clusterin

11/3/2

008

Yes.

Yes, if

you are

using a

non-

Micros

oft

clustere

d file

system

or non-

Micros

oft

replicat

Windo

ws6.0-

KB957

967-

x64.ms

u

Windo

ws

Server

2008

SP2

Windo

ws6.0-

KB958

065-v2- 2008

x64.ms

u

Windo

ws

Server

Not

Applicab

le

Not

Applicab

le

g when

 

the

 

virtual

machine

uses a

storage

device

that is

managed

by a

 

ion

third-

solution

party

s.

clustered

 

file

system

or a

third-

party

replicati

on

solution”

 

“Virtual

machine

backup

operatio

ns fail in

Window

s

Server

Yes,

2008

 

when

when

backing

Windo

Hyper-V

up a

KB958

184

virtual

machine

files are

11/5/2

008

volume

that is

mounte

ws6.0-

KB958

184-

saved on

d using

x64.ms

a

volume

a

u

that is

 

volume

mounted

GUID.

on a

 

failover

cluster

by using

a

volume

GUID”

 

KB960 “The

12/17/ Yes, if

Windo

578

IRET

2008

you

ws6.0-

Windo

ws

Server

2008 le

SP2

Not

Applicab

Windo

ws

Not

Applicab

and

IRETD

instructi

have a

ons do

progra

not

m that

support

uses the

the

IRET

Nested

(interru

Task

pt

KB960

(NT)

return)

578-

flag in

or

x64.ms

protecte

IRETD

u

d mode

(interru

in a

pt

Window return

double)

2008 instruct

s

Server

Hyper-V

environ

ment”

“An

update is

available

for

Window

s Server

 

2008-

based

compute

KB959 rs to

1/16/2

962

address

009

issues

with

backing

up and

restoring

Hyper-V

virtual

machine

s”

KB963 “The

3/03/2

709

AltGr

009

key does

not work

on a

ion.

Yes,

when

backing

up

virtual

machin

es.

Windo

ws6.0-

KB959

962-v3-

x64.ms

u

Yes, if

you are

using a

German 709-

keyboar x64.ms

Windo

ws6.0-

KB963

Server

2008 le

SP2

Windo

ws

Server

2008

SP2

Windo

ws

Server

2008

SP2

6.0.6001. Hotfix http://go.microsoft.com/fwli

22352

KB967

902

virtual

machine

on a

Window

s Server

2008-

based

server

that has

the

Hyper-V

role

enabled”

“You

cannot

connect

to a

virtual

machine

when the

Window

s

2008

Hyper-V

VMMS

certificat

e

expired”

Server

has

KB970 “Hyper-

203

V

Manage

ment

Tools

update

for

Window

s

Service

Vista

Pack 2”

(Install

this for

fixes for

the

Hyper-V

Manage

ment

3/24/2

009

6/23/2

009

Yes.

Windo

ws6.0-

KB967

902-

x64.ms

u

Yes, if

you are

using

the

Hyper-

V

Manage Windo

r

ws6.0-

Windo

ws6.0-

KB970

203-

x86.ms

u

KB970

203-

Manage x64.ms

ment

oft

Micros

u

Consol

e

(MMC)

snap-in.

Windo

ws

Server

2008

SP2

Windo

ws

Vista

SP2

Not

Applicab

le

Windo

ws

Update

,

Downl

oad

Center,

Hotfix

Not

Applicab oad

le

Downl

Center

Tools on

compute

rs that

are

running

Window

s Vista

 

Service

 

Pack 2).

“Slow

system

response

together

with

many

other

performa

nce

issues

 

Windo

 

Windo

ws

 

occur on

 

a

KB972 virtualiz

7/14/2

No.

ws6.0-

KB972

Server

2008,

Windo

045

ation

009

045-

 

ws

 

server

 

x64.ms

that is

u

Server

running

Window

 

2008

SP2

s

Server

2008

and

 

that has

the

Hyper-V

role

installed

KB971 “A

8/5/20

Yes, if

Windo

Windo

677

Hyper-V 09

you

ws6.0-

ws

differenc

 

have

KB971

Server

ing disk

differen 677-

2008,

that you

cing

x64.ms

Windo

create in

disks

u

ws

Window

that

Server

s

Server

were

2008

2008

R2

 

created

SP2

cannot

in

be used

Windo

Not

Applicab

le

Not

Applicab

le

 

ws

Server

2008

 

in

 

R2 and

Window

want to

 

use

 

s

Server

them in

Windo

 

2008”

 
 

ws

Server

2008.

 

“A

 

hotfix is

available

that

addresse

s

the

issues

 

that

occur

 

Yes, if

 

you are

when

you

KB975 perform

925

a

host-

12/1/2

009

running

Hyper-

V on

Windo

ws6.0-

KB975

925-

 

level

backup

the

affected

x64.ms

u

of a

hardwa

Hyper-V

re.

VM on a

 

compute

r

that is

running

 

Window

s

Server

2008”

 

KB977 “MS10-

2/9/20

Yes.

Windo

894

010:

10

ws6.0-

Vulnera

KB977

bility in

894-

Window

x64.ms

s

Server

u

2008

 

Windo

Hyper-V

ws6.1-

could

KB977

allow

894-

denial of

x64.ms

Windo

ws

Server

2008

SP2

Windo

ws

Server

2008,

Windo

ws

Server

2008

SP2,

Windo

ws

6.0.6002. Hotfix http://go.microsoft.com/fwli

22233

Not

Applicab y

le

bulletin

KB981

791

service”

 

u

“"STOP:

 

0x00000

01a"

error

message

on a

compute

r

that has

an Intel

 

Westmer

 

Yes, if

 

you are

e

processo

r

together

with the

Hyper-V

role

4/26/2

010

running

Hyper-

V on

Intel

Westm

ere

n/a

installed

process

 

ors.

on

 

Window

s Server

2008 or

on

Window

s Server

2008

R2”

Server

2008

R2

Windo

ws

Not

Server

Applicab

2008

le

SP2

Hyper-V Update List for Windows Server 2008 R2

Updated: September 15, 2010

Applies To: Windows Server 2008 R2

The following table shows the list of software updates and hotfixes for Hyper-V in Windows Server 2008 R2. Updates that are available on Windows Update are indicated, as well as the download location for those that are available at the Microsoft Download Center. These updates and hotfixes can help avoid some known issues and may save you a support call.

Note Some updates are required only under certain circumstances, as noted in the table. Also, you may want to see the list of updates for Hyper-V in Windows Server 2008 (which includes updates for Windows Server 2008 Service Pack 2)(http://go.microsoft.com/fwlink/?LinkId=183322).

Pack 2)(http://go.microsoft.com/fwlink/?LinkId=183322). Comprehensive list of Hyper-V R2 updates Know ledge

Comprehensive list of Hyper-V R2 updates

Know

ledge

Base

Name

Date

Articl

e

KB97

“You receive a

10/1/

4598

"Stop 0x0000007E" 2009 error on the first

Requ ired? File Name

App

lies

to

Yes, Windows6. Win

if you 1-

dow

encou KB974598 s

restart after you

nter

-x64.msu

Serv

enable Hyper-V on

this

er

a Windows Server

error

2008

2008 R2-based

and

R2

computer”

your

serve

r uses

a “C-

state”

(lowe

r

powe

r

state)

that

is

suppo

rted

by

the

proce

ssor,

but is

not

suppo

rted

by

Integra

tion

Service

s

Versio

n

Not

Applica

ble

Avail

abilit

y

Link

“The network

connection of a running Hyper-V virtual machine is lost under heavy

4909 outgoing network traffic on a Windows Server

KB97

2008 R2-based

computer”

KB97

5354

“A Hyper-V update rollup package is available for a computer that is running Windows Server 2008 R2”

Hype

r-V.

 

Win

 

Windows6. dow

 

10/21

/2009 No.

1-

KB974909

s Not

Serv Applica Hotfix

-v2-

er

ble

x64.msu

2008

 

R2

 

Windows6.

Yes,

1-

11/10

/2009

if you KB975354

are

runni

ng a

backu 1-

p

restor -ia64.msu

e

soluti 1-

on.

KB975354

-v2-

x64.msu

Win

dow

Windows6. s

Serv

or

KB975354 er

2008

Windows6. R2

6.1.760

0.20542 Hotfix wlink/?LinkId=179092

-x86.msu

KB97

5530

KB97

4672

Yes,

if

are

runni

ng

Hype

r-V

on

the

affect

you

“Stop error message on an Intel Xeon

5500 series

processor-based computer that is running Windows

11/20

Server 2008 R2 and /2009 that has the Hyper- V role installed:

"0x00000101 - CLOCK_WATCH DOG_TIMEOUT"

“Virtual machines stop responding (hang) during startup and the Vmms.exe process crashes on a Windows Server

2008 R2 computer

/2009

ed

hard

ware.

10/14 No.

Win

Windows6. dow

1-

KB975530 Serv Applica Cente

-v3-

x64.msu

Down

load

r,

Hotfix

s

Not

ble

er

2008

R2

Windows6. Win

1-

KB974672 s

-x64.msu

dow

Serv

er

2008

R2

Not

Applica

ble

that has the Hyper-

V role installed“

Win

dow

s

Serv

er

2008

,

Win

dow

s Not

Serv Applica

er ble

2008

SP2,

Windows6.

“MS10-010:

0-

Vulnerability in

KB977894

Yes.

-x64.msu

Windows6.

1-

KB977894

-x64.msu

n

KB97 Windows Server

2/9/2

7894

2008

Hyper-V

010

could allow denial

of

service”

“Stop error in

Windows Server

KB98

2008

R2:

3/12/

0856

"0x000000CA

2010

PNP_DETECTED_

FATAL_ERROR"”

“The computer stops responding or

KB98

restarts during the Hyper-V Live

3/27/

1618

Migration process

2010

in

Windows Server

2008

R2” (relates to

AMD Errata 383)

 

KB98

“Network

4/28/

1836

connectivity for a Windows Server 2003-based Hyper-

2010

 

Win

dow

s

Serv

er

2008

R2

Win

Windows6.

dow

1-

KB980856

Yes,

if you

store

VHD

s on

non- -x64.msu

PNP R2

disks.

Yes,

if you

are Win

dow

ng

runni Windows6.

s Not

Serv Applica Hotfix

er ble

2008

1-

s

Not

Hype KB981618

r-V

on 2008

AMD R2

proce

ssors.

Yes, Windows6. Win

dow

if the

serve KB981836 s

r

Serv Applica Hotfix

er

ble

-x64.msu

6.1.760 Hotfix http://go.microsoft.com/f

1-

-

Serv

V virtual machine is

lost temporarily in Windows Server

2008 R2”

“"STOP:

0x0000001a" error message on a

KB98

computer that has an Intel Westmere processor together

1791

with the Hyper-V role installed on Windows Server

2008

or on

Windows Server

2008

R2”

KB22

“The network

 

runni

ng

Hype

r-V

has a

virtua

l

mach

ine

that

is

runni

ng

Wind

ows

Serve

r

2003.

Yes,

if you

are

runni

ng

5/5/2

010

Hype

r-V

 

on

Intel