Windows 2008 r2 hyper-v certification

Cross says about it:. Over the past 10 years, Microsoft has continued to demonstrate leadership in certifying our operating systems and applications, in order to provide customers with the additional confidence of independent validation of our design and security engineering.

Similar to our previous operating system evaluations and the independent Windows Server Hyper-V evaluation, we used the Windows Server R2 evaluation to demonstrate how Hyper-V is methodically designed, tested, and reviewed from a security perspective. The Hyper-V evaluation focused on isolation between the host partition and guest partitions, isolation between guest partitions and the Live Migration capability, which was added in Windows Server R2.

We encourage customers to explore and build on the evaluated Hyper-V platform to meet your needs for the next generation applications and services! MicroServer Gen8. BLc Gen8 1. DL G6. DLe Gen8 1. DLe Gen8 v2 1. DLp Gen8 1. MLe Gen8 1. MLe Gen8 v2 1. MLp Gen8 1. SLs Gen8 1. SL Gen8 1, 2.

BLc G5. BLc G6. DL G7. DLh G6. DL2xh G6. DL4xh G6. DL G5p. ML G6. ML G7. ML G5p. DLse G6. EL Converged Edge System 3. WSc Gen9. MicroServer Gen8 1. BLc G7. BLc Gen8 1,2. WSc Gen8 1. DL Gen8 1. DLe G6. DL Gen8 1,2. MLe Gen8 v2 1,2,3. SLs Gen8 1,2. SLs G7. SL Gen8 1,2. BL2xc G7. BL2xc G5. BL2xc G6. BL20p G4. BL25p G2. BL45p G2. DL G5. Issue 4 Consider the following scenario:. This call has a default time-out of 60 seconds. Therefore, the backup operation fails.

Issue 2 When the virtual machines VMs on different nodes are backed up in parallel, every node waits to become the cluster shared volume owner to create the snapshots. However, the Cluster service moves the volume owner from one node to another node immediately after a snapshot is created without waiting for post-snapshot tasks to be completed.

If another node requests the same shared volume for a backup operation before the post-snapshot tasks are completed, the Cluster service changes the volume to another node. Therefore, the VSS writer that is in the previous node cannot find the cluster shared volume locally when it performs post-snapshot tasks.

This behavior causes the VM backup operation to fail. Issue 3 The application backup operation in the virtual machine VM is incorrectly affected by the VM backup operation on the server that is running Hyper-V.

Issue 4 The snapshot files are not restored successfully when you restore the virtual machine VM. Important This section, method, or task contains steps that tell you how to modify the registry.

However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:.

You can apply the following registry entry in a virtual machine to fix issue 3 for that virtual machine:. If this registry entry does not exist, or if its value is 0, issue 3 occurs.

After you install this hotfix on the Hyper-V server, you must update the Integration Components in the virtual machines. A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing.