[Knowledge Sharing] Hyper-V FAQ
Hi All,
This thread is a summary of the Frequently Asked Questions on Windows Server forums; we consolidate them and post it here for your reference. If you have any further questions, please kindly start a new thread in that other community members and we can easily attend to your question and reply. Thanks for your cooperation.How to Questions
Q1: How can I check if my machine is compatible with Hyper-V?
Q3: How can I move a virtual machine from one Hyper-V server to another?
Q4: How can I enable Windows Server Backup support for the Hyper-V VSS Writer?
Q5: Can I back up an individual running virtual machine?
Q6: How can I configure Hyper-V on a failover cluster?
Q7: Can I grant a specific user the access permission only to a specific virtual machine?
Q8: Are there any documents that can help me understand how Hyper-V virtual networking works better?
Common Issues:
Q3: The NLB host does not converge as expected on Windows Server Hyper-V virtual machines
Q4: Failed to create partition: Unspecified error (0x80004005)
Q7: "Microsoft Hyper-V VSS Writer" is not listed when you run the “vssadmin list writers” command.
Q8: Some virtual machines go to the “Saved” state when you try to backup them.
Q11: Negative ping times in virtual machines running on Hyper-V.
NOTE: Microsoft does not offer formal support for the communities you'll find here. Instead, our role is to provide a platform for people who want to take advantage of the global community of Microsoft customers and product experts. Microsoft may monitor content to ensure the accuracy of the information you'll find, but any information provided by Microsoft staff is offered "AS IS" with no warranties, and no rights are conferred. You assume all risk for your use.
Laura Zhang - MSFT- ИзмененоLaura Zhang - MSFTMSFT, Модератор2 апреля 2009 г. 7:09
- ИзмененоLaura Zhang - MSFTMSFT, Модератор3 июня 2009 г. 3:27
- ИзмененоLaura Zhang - MSFTMSFT, Модератор2 апреля 2009 г. 3:25
- ИзмененоLaura Zhang - MSFTMSFT, Модератор2 апреля 2009 г. 3:27
- ИзмененоLaura Zhang - MSFTMSFT, Модератор2 апреля 2009 г. 5:32
Все ответы
Recent Hot fixes
Hyper-V Update for Windows Server 2008 x64 Edition (KB950050):
Update for Windows Server 2008 x64 Edition (KB956697):
Update for Windows Server 2008 x64 Edition (KB956774):
Hyper-V Update for Windows Server 2008 x64 Edition (KB956589):
Update for Windows Server 2008 x64 Edition (KB956710):
A computer that is running an x86-based version of Windows Server 2008 or an x86-based version of Windows Vista may use fewer processors than expected if the number of cores on a socket is not a power of 2:
http://support.microsoft.com/kb/950182/en-us
Error message when you try to start a Hyper-V virtual machine on a Windows Server 2008-based or Windows Vista-based computer that uses the NUMA architecture: "An error occurred while attempting to change the state of virtual machine VMNAME":
http://support.microsoft.com/kb/953585/en-us
The NLB host does not converge as expected on Windows Server 2008 Hyper-V virtual machines:
http://support.microsoft.com/kb/953828/en-us
Increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V role:
http://support.microsoft.com/kb/951308
You cannot configure a Hyper-V virtual machine by using Windows Server 2008 Failover Clustering when the virtual machine uses a storage device that is managed by a third-party clustered file system or a third-party replication solution:
http://support.microsoft.com/kb/958065
Stop error message on a Windows Server 2008-based computer that has the Hyper-V role installed: "STOP 0x0000001A":
http://support.microsoft.com/default.aspx?scid=kb;EN-US;957967
Laura Zhang - MSFTRecent KBs
Virtual machines that were created on the beta version of the Hyper-V role do not start after the Hyper-V role is updated to a later version
http://support.microsoft.com/kb/949222
Increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V role
http://support.microsoft.com/kb/951308
Description of the Windows Vista Service Pack 1 Management Tools update for the release version of Hyper-V
http://support.microsoft.com/kb/952627
Error message when you try to start a Hyper-V virtual machine on a Windows Server 2008-based or Windows Vista-based computer that uses the NUMA architecture: "An error occurred while attempting to change the state of virtual machine VMNAME"
http://support.microsoft.com/kb/953585
A Hyper-V update is available to increase the number of logical processors and virtual machines on a Windows Server 2008 x64-based computer
http://support.microsoft.com/kb/956710
Sleep and hibernate power features are not available when you enable Hyper-V technology on a Windows Server 2008-based portable computer
http://support.microsoft.com/kb/954418
A Windows Vista Service Pack 1-based guest virtual machine restarts without warning after you uninstall the RC1 integration services on a Windows Server 2008-based computer
http://support.microsoft.com/kb/954424
Windows Server 2008 Hyper-V VSS writer is not used during a backup job because of corrupted or invalid virtual machine configuration files
http://support.microsoft.com/kb/956697
Description of the Hyper-V update for issues that may occur when you manage the Hyper-V role on the 64-bit editions of Windows Server 2008 by using SCVMM
http://support.microsoft.com/kb/956589
Windows Server system software that is not supported in a Hyper-V virtual machine environment
http://support.microsoft.com/kb/958664
Error message when you add a SCSI controller to a Windows 2000 SP4-based virtual machine in Hyper-V Manager on server that is running Windows Server 2008: "STOP c0000263"
http://support.microsoft.com/kb/958667
Event ID 12 is logged in the System log when you back up or compact a Hyper-V virtual hard disk on a Windows Server 2008-based computer
http://support.microsoft.com/kb/958669
Offline Policy tab for a Virtual Machine Cluster resource is labeled with “...”
http://support.microsoft.com/kb/959075
Stop error message on a Windows Server 2008-based computer that has the Hyper-V role installed: "STOP 0x0000001A"
http://support.microsoft.com/kb/957967
NOTE: This post contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.
Laura Zhang - MSFTHow To - Q1: How can I check if my machine is compatible with Hyper-V?
A1: Here are some utilities that will tell you if your hardware supports Hyper-V:1. AMD Hyper-V capability tester
http://www.amd.com/us-en/assets/content_type/utilities/AMD-V_Hyper-V_Compatibility_Check_Utility.zip
2. Intel processor identification utility
http://www.intel.com/support/processors/tools/piu/sb/CS-014921.htm
3. Free third-party utility’s to show if a machine is Hyper-V capable:
http://www.grc.com/securable.htm
Additionally, you have to ensure that all your devices and device drivers are compatible with 64-bit versions of Windows Server 2008. You can check this in Windows Server Catalog (http://www.windowsservercatalog.com/).
Laura Zhang - MSFT- ИзмененоLaura Zhang - MSFTMSFT, Модератор2 апреля 2009 г. 10:38
How To - Q2: How can I move a virtual machine that is running on Microsoft Virtual Server to a Windows Server 2008 Hyper-V environment?
A: To do so, please refer to the following Microsoft Knowledge Base article:http://support.microsoft.com/kb/958663/en-us
Laura Zhang - MSFT- ИзмененоLaura Zhang - MSFTMSFT, Модератор2 апреля 2009 г. 3:53
How To - Q3: How can I move a virtual machine from one Hyper-V server to another?
A: You can do this either by exporting the virtual machine from one Hyper-V server and then importing it to another one, or by using the System Center Virtual Machine Manager. However, you cannot do this by just copying the VHD files and XML files to another Hyper-V server and directly using them there.For exporting and importing scenario, you can perform the following steps:
On the Source Hyper-V Server
=========================
1. Open the Hyper-V Manager console, right-click the virtual machine which you want to export, and click Export….
2. Specify the location where you want to store the Export files. Note that this can be a network share.
3. After the Export process completes, copy all the export files to the target Hyper-V server.
On the Target Hyper-V Server
=========================
1. On the target Hyper-V server, open the Hyper-V Manager console, right-click the Hyper-V server node and click Import Virtual Machine….
2. Browse to the root folder containing all the Export files and click Select.
Please also note that once the Importing process completes, all the snapshots and VHD files are stored at the location where you put the Export files. Be careful of this if you want to keep all the snapshots and VHD files in a different location.
Laura Zhang - MSFTHow To - Q4: How can I enable Windows Server Backup support for the Hyper-V VSS Writer?
A: Before you can restore the Hyper-V server, you need to register the Hyper-V VSS Writer with Windows Server Backup. For more information, please refer to the following Windows Server Core Team blog:
Laura Zhang - MSFTHow To - Q5: Can I back up an individual running virtual machine?
A: System Center Data Protection Manager (DPM) 2007 SP1 extends DPM support to Microsoft Hyper-V. DPM now supports both host-based protections for Hyper-V where the agent is installed on the host computer, and guest-based where the agent is installed directly on the virtual machine. If you have DPM 2007 installed, you may download and install DPM 2007 SP1 to backup the individual guest machine.System Center Data Protection Manager (DPM) 2007 Service Pack 1
http://technet.microsoft.com/en-us/dpm/dd296757.aspx
Meanwhile, you may try Symantec Backup Exec 12.5 Agent for this situation. With the release of Backup Exec 12.5, Symantec has added fully support for backing up Hyper-V and Hyper-V virtual machines. For more information, please refer to the following Ben Armstrong’s blog:
NOTE: Windows Server Backup cannot be used to back up an individual virtual machine. Windows Server Backup only supports volume based backups. When backing up virtual machines, you need to backup all volumes where VM related files are present.
Laura Zhang - MSFTHow To - Q6: How can I configure Hyper-V on a failover cluster?
A: To configure Hyper-V on a failover cluster (host cluster), please refer to the following Step-by-Step guide:Hyper-V Step-by-Step Guide: Hyper-V and Failover Clustering
http://technet.microsoft.com/en-us/library/cc732181.aspx
Laura Zhang - MSFT- ИзмененоLaura Zhang - MSFTMSFT, Модератор2 апреля 2009 г. 3:54
How To - Q7: Can I grant a specific user the access permission only to a specific virtual machine?
For example, if I have two virtual machines VMA and VMB. Two users UserA and UserB need to access the Hyper-V server remotely to perform their own tasks. I want to grant UserA only the access permissions to VMA, while grant UserB only the access permissions to VMB. How can I do this?
A: Currently, there is no user interface to achieve this goal easily. However, you can do this by using PowerShell scripts.
The general steps are:
1. Create two new scopes for UserA and UserB in Authorization Manager (AzMan).
2. Configure these two scopes so that UserA and UserB have the proper permissions to perform their tasks (e.g. shutdown virtual machines).
3. Use a PowerShell script to change the virtual machines' (VMA and VMB) attributes.
Dung has given the detailed steps and information on this in his blog:
Laura Zhang - MSFT- ИзмененоLaura Zhang - MSFTMSFT, Модератор2 апреля 2009 г. 3:56
How To - Q8: Are there any documents that can help me understand how Hyper-V virtual networking works better?
A: Yes, Ben Armstrong and John Howard have given useful information on this topic in their blogs:Ben Armstrong's blog:
http://blogs.msdn.com/virtual_pc_guy/archive/2008/01/08/understanding-networking-with-hyper-v.aspx
John Howard's blog:
http://blogs.technet.com/jhoward/archive/2008/06/16/how-does-basic-networking-work-in-hyper-v.aspx
Laura Zhang - MSFT- ИзмененоLaura Zhang - MSFTMSFT, Модератор2 апреля 2009 г. 3:57
How To - Q9: Are there any documents or resources that I can refer to if I want to learn how to manipulate Hyper-V via PowerShell?
A: All Hyper-V related WMI classes can be found in the following MSDN library:http://msdn.microsoft.com/en-us/library/aa155190.aspx
For PowerShell, you can start with a Windows PowerShell book:
The following blogs have many sample scripts for your reference:
Ben Armstrong' blog (VBScripts and PowerShell script):
http://blogs.msdn.com/Virtual_PC_Guy/
Taylor Brown's blog:
http://blogs.msdn.com/taylorb/
Dung's blog:
http://dungkhoang.spaces.live.com/Blog/cns!31A50D02D661C816!128.entry
Laura Zhang - MSFTHow To - Q1: After a Windows 2000 SP4 VM is migrated to Hyper-V, Windows 2000 SP4 VM which uses Multiprocessor HAL may show high CPU in the Hyper-V Manager console.
Symptom
=======
After you move a Windows 2000 SP4 VM which uses Multiprocessor HAL from Virtual Server to Hyper-V, you notice that the CPU usage of the virtual machine is consistently high in the Hyper-V Manager console. However, when you check the CPU usage in the virtual machine, it is rather low.
Possible Cause
===========
This problem may occur when the HAL of the Windows 2000 virtual machine is Multiprocessor instead of Uniprocessor. The HAL mismatch may cause this problem.
Currently, virtual machines running Windows 2000 support only one virtual processor. Please refer to the following Microsoft Knowledge Base article for more information:
Guest operating systems that are supported on a Hyper-V virtual machine:
http://support.microsoft.com/kb/954958/en-us
Resolution
========
Please perform the following steps to ensure that you have configured the virtual machine to use only one virtual processor; in addition, the Windows 2000 SP4 guest is using Uniprocessor HAL.
1. Ensure that the virtual machine is configured to use only one virtual processor. To do so, please perform the following steps:
1) In the Hyper-V Manager console, right-click the virtual machine and click Settings.
2) Locate to the Processor, and then check the "Number of logical processors" option under Processor area.
2. Check which HAL the Windows 2000 virtual machine is using. To do so, please perform the following steps on the guest system:
3) Click Start, right-click My Computer and click Manage.
4) Locate to Device Manager. In the right hand pane, expand the Computer branch and see what it shows underneath the Computer node.
3. If it is Multiprocessor, please perform the following steps to change the computer type to Uniprocessor:
NOTE: Please backup your virtual machine before you change the HAL.
5) Open the Device Manager console. In the right hand pane, expand the Computer branch.
6) Right click on the value listed under Computer (either ACPI multiprocessor or MPS multiprocessor) and select Properties.
7) Click the Driver tab and then Update Driver.
8) Follow the wizard by selecting Next, choosing "Display a list of known drivers for this device" under "What do you want the Wizard to do?", and then clicking NEXT.
1) Here is the important step: if you currently have an ACPI Multiprocessor PC, choose ACPI Uniprocessor PC. If you have MPS Multiprocessor PC, choose MPS Uniprocessor PC. This is critical, make certain you choose it correctly.
2) After selecting the correct HAL, follow the rest of the wizard to install the driver. When you are prompted to reboot, shut the machine completely down.
3) Reboot the computer. Go into Device Manager and see if the correct HAL is loaded.
Laura Zhang - MSFTQuestion - Q2: Virtual machine settings that are changed on one node in a Failover Cluster are not present when the VM is moved to another node.
Symptom=======
Virtual machine settings that are changed on one node in a Failover Cluster are not present when the VM is moved to another node.
Possible Cause
===========
The cluster resources for a virtual machine (VM) store configuration information about the VM. This information is used to configure the virtual machine on the other nodes of the cluster if the VM is moved to a different node. If you do not refresh this information for a clustered VM after you modified the settings of that VM via the Hyper-V manager, the Hyper-V Failover Cluster is not able to correctly record the change and configure the VM when it is moved to another node.
Resolution
==========
When virtual machine settings are changed on a VM that’s on a Failover Cluster, you must select the Refresh virtual machine configuration option before the VM is moved to another node. To do so, please perform the following steps:
1. In Failover Cluster Manager, select the virtual machine. There will be an item in the Action pane “Refresh virtual machine configuration”.
2. Click “Refresh virtual machine configuration”.
Laura Zhang - MSFTProblem - Q3: The NLB host does not converge as expected on Windows Server Hyper-V virtual machines
Symptom
========
Consider the following scenario:
- You are running a Windows Server 2003/2008 virtual machine in the Hyper-V environment on a Windows Server 2008 host computer.
- You try to create a new Network Load Balancing (NLB) cluster on this virtual machine. Or, you try to add this virtual machine to an existing NLB cluster.
In this scenario, the NLB host on the virtual machine does not converge as expected.
On Windows Server 2003 virtual machines, if you try to ping the DNS name or the IP address of the NLB cluster, you receive the error saying that "Request timed out".
On Windows Server 2008 virtual machines, if a large volume of traffic occurs in the NLB cluster, the guest system on the virtual machine may restart unexpectedly, and you may receive the following Stop error message:
STOP: 0x000000E1 (parameter1, parameter2, parameter3, parameter4)
Possible Cause
============
Hyper-V Synthetic NIC does not work with dynamic MAC address and you may need to manually set the NLB MAC for the related virtual machine if you are using Unicast mode.
For Windows Server 2008, the unexpected virtual machine restart occurs because of a deadlock condition in the Nlb.sys driver.
Resolution
=========
Please perform the following steps to configure Hyper-V to use the NLB cluster MAC address:
1. Get the existing cluster MAC address. To do so, please perform the following steps:
1) Run the command line below and write down the Unicast MAC address:
nlb.exe ip2mac <clusterIP>
Or
2) Perform the following steps
- Click Start, point to Administrative Tools, and then click Network Load Balancing Manager.
- In the console tree, right-click Network Load Balancing Clusters, and then click Connect to Existing.
- In the Host box, type the computer name of the virtual machine that is part of the existing NLB cluster, and then click Connect.
- Right-click the cluster, click Cluster Parameters, record the MAC address in the Network Address property, and then click Cancel.
2. Configure the virtual machine to use the corresponding NLB MAC address
1) On the host computer, open Hyper-V Manager.
2) In the details pane, under Virtual Machines, right-click the virtual machine that you want to configure, and then shutdown.
3) In the details pane, under Virtual Machines, right-click the virtual machine that you want to configure, and then click Settings.
4) In the navigation pane, click the network adapter that you use for the NLB cluster.
5) In the details pane, click Static under Mac Address, and then specify the MAC address that you noted in above steps.
6) Start the virtual machines to test this issue again.
For Windows Server 2008, please also download and install the hot fix described in the following Microsoft Knowledge Base article on the virtual machine; meanwhile, please perform the steps Post-Installation steps in the article.
The NLB host does not converge as expected on Windows Server 2008 Hyper-V virtual machines:
http://support.microsoft.com/kb/953828
Laura Zhang - MSFTProblem - Q4: Failed to create partition: Unspecified error (0x80004005)
Symptom
========
You have installed Hyper-V role. When you try to create a new virtual machine, you receive the following error:
Failed to create partition: Unspecified error (0x80004005)
Possible Cause
============
This error may happen if you haven't enabled Data Execution Protection (DEP) in BIOS or the hardware doesn't support Data Execution Protection (DEP).
Resolution
=========
Make sure that you have enabled both Hardware Assisted Virtualization and Data Execution Protection (DEP) in the BIOS.
If you cannot find the Data Execution Protection (DEP) in BIOS, you may need to contact manufacturers to see if the motherboard supports Data Execution Protection (DEP) and if the last BIOS version supports it.
Laura Zhang - MSFTProblem - Q5: Why cannot I use mouse when connecting to my Hyper-V server via a Remote Desktop Connection and clicking into a virtual machine?
A. First of all, please ensure that the guest operating system is supported and integration services are available for the operating system. If Integration Services is not installed, please install it to improve mouse integration. If the guest operating system is not supported, you can use a key combination to move the mouse out of the virtual machine window. The default key combination is Ctrl+Alt+Left arrow.For now, the Integrated Mouse support for Linux is not released yet. Please see Mike Sterling's blog for this information:
http://blogs.msdn.com/mikester/archive/2008/09/10/linux-integration-components-now-posted.aspx
If you want to manage a Linux virtual machine remotely, you can try the Hyper-V management tools:
Packages for Windows Vista SP1 (X86):
http://www.microsoft.com/downloads/details.aspx?FamilyId=BF909242-2125-4D06-A968-C8A3D75FF2AA
Packages for Windows Vista SP1 (X64):
http://www.microsoft.com/downloads/details.aspx?FamilyId=88208468-0AD6-47DE-8580-085CBA42C0C2
Packages for Windows Server 2008 (X86):
http://www.microsoft.com/downloads/details.aspx?FamilyId=6F69D661-5B91-4E5E-A6C0-210E629E1C42
Laura Zhang - MSFTProblem - Q6: When you try to manage Hyper-V server by using the Hyper-V Manager console, you receive the error message saying that “Msvm_VirtualSystemManagementService object was not found”.
Symptom
=======
When you try to remotely manage the Hyper-V server by using the Hyper-V Manager console, you may encounter an error saying that "Msvm_VirtualSystemManagementService object was not found".
Possible Cause
============
The problem may occur when the version of the Hyper-V server and the remote Hyper-V Manager console does not match.
Resolution
=========
1. Check the version of Hyper-V server and ensure that it is RTM version. To do so, please perform the following steps:
In the Hyper-V Manager console, on the menu bar, click Help and select "About Hyper-V Manager…". RTM version of Hyper-V will show the number version "6.0.6001.18016".
2. On the management client, refer to the following links to download and install the appropriate Hyper-V Remote Management Update:
Windows Vista SP1 (X86
http://www.microsoft.com/downloads/details.aspx?FamilyId=BF909242-2125-4D06-A968-C8A3D75FF2AA
Windows Vista SP1 (X64)
http://www.microsoft.com/downloads/details.aspx?FamilyId=88208468-0AD6-47DE-8580-085CBA42C0C2
Windows Server 2008 (X86)
http://www.microsoft.com/downloads/details.aspx?FamilyId=6F69D661-5B91-4E5E-A6C0-210E629E1C42
Windows Server 2008 (X64
http://www.microsoft.com/downloads/details.aspx?FamilyId=F3AB3D4B-63C8-4424-A738-BADED34D24ED
Laura Zhang - MSFTProblem - Q7: "Microsoft Hyper-V VSS Writer" is not listed when you run the “vssadmin list writers” command
Symptom
========
When you try to back up a Hyper-V server, the backup failed. The following event is logged in the Hyper-V-VMMS event log:
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Event ID: 10107
Description:
An error occurred while identifying the Hyper-V VSS writer. Check for any corrupt or invalid configuration files and try again.
When you try to list the VSS writers by using either "vssadmin list writers" or "diskshadow" then "list writers", "Microsoft Hyper-V VSS Writer" is not listed in the output list.
Possible Cause
============
This problem occurs because of corrupted or invalid virtual machine configuration file or orphaned symbolic links.
Resolution
=========
· Refer to the following KB article to check and fix corrupted or invalid virtual machine configuration files:
Windows Server 2008 Hyper-V VSS writer is not used during a backup job because of corrupted or invalid virtual machine configuration files
http://support.microsoft.com/kb/956697
· Browse to the “%systemdrive%\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines\” folder to see if there are any orphaned symbolic links. To check it, you can double-click each symbolic link file. If any link is orphaned, an error will occur. Please delete the corrupted symbolic link and test this problem again.
Laura Zhang - MSFTProblem - Q8: Some virtual machines go to the “Saved” state when you try to backup them.
Symptom
========
When you try to back up the Hyper-V server with all the running virtual machines by using Windows Server Backup, you find that some of the virtual machines go into “Saved” state while others not.
Or, when you run "diskshadow" command and then type "list writers" switch, you may find that some Components under "Microsoft Hyper-V VSS Writer" are described as "Caption: Backup Using Saved State\<VM name>".
Possible Cause
=============
This problem may occur if one or more of the following conditions are true:
· The guest operating system doesn't support VSS, such as Microsoft Windows 2000 or Windows XP..
· You haven't installed the Integration Services in the virtual machine or you haven’t enabled it.
· The guest operating system has some Dynamic Disks
Resolution
=========
1. Check if the guest operating system can support VSS. Virtual machines that are running operating systems that do not support VSS, such as Microsoft Windows 2000 or Windows XP, will be put in a saved state while the VSS snapshot is created. .
2. Check if the guest operating system can support Integration Services and if you have installed Integration Services in the virtual machine. If so, please perform the following steps to ensure the “Backup (volume snapshot)” Integration Service option is checked.
1) Open the “Settings” dialog box for the virtual machine.
2) Select the Integration Services under Management area. In the right hand of panel, please ensure that the "Backup (volume snapshot)" option is checked.
3) Start the virtual machine. In the virtual machine, open the Services console and ensure the "Hyper-V Volume Shadow Copy Service" is started.
3. Check if the guest operating system contains any Dynamic Disks. According to the following Hyper-V Release Note, 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.
http://download.microsoft.com/download/2/e/7/2e7387d3-1391-4176-abe8-44e481100694/relnotes.htm
Laura Zhang - MSFTProblem - Q9: A virtual machine cannot be created or started properly with the error saying that “The requested operation cannot be performed on a file with a user-mapped section open. (0x800704C8)”
Symptom
========
When you attempt to create or start a virtual machine, you receive the following error:
The requested operation cannot be performed on a file with a user-mapped section open. (0x800704C8)
Possible Cause
=============
Antivirus software that is installed in the parent partition may cause this issue. The real-time scanning component may be configured to monitor the Hyper-V virtual machine files.
Resolution
=========
Configure the real-time scanning component within the antivirus software to exclude the following files and directories:
• Default virtual machine configuration directory (C:\ProgramData\Microsoft\Windows\Hyper-V)
• Custom virtual machine configuration directories
• Default virtual hard disk directory (C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks)
• Custom virtual hard disk directories• Snapshot directories
• Vmms.exe
• Vmwp.exe
Laura Zhang - MSFTProblem - Q10: You receive the error message "General access denied error (0x80070005)" when you try to configure VMs to use files located on a network share.
Symptom========
Consider the following scenario:
You have three physical machines, one running as the Hyper-V server, one running as a file server (for network share) and one running as the client (specifically, Windows Vista machine with SP1). They reside on the same network.
You may receive the following error message when you try to configure Hyper-V with some files (e.g. ISO files) located on a network share of the file server.
General access denied error (0x80070005)
Possible Cause
=============
There are several possible causes for this issue:
1. The network share folder permission is not configured properly.
2. If you are managing VM configuration remotely via Hyper-V Manager, the constrained delegation is not configured to authorize the impersonation required in this scenario.
Resolution
=========
1. To access network share properly, you should give share and NTFS permissions to both the Hyper-V computer account and the user who is logging on the Hyper-V server currently. For more information, please refer to the following blog by Jose Barreto :
2. If you use Hyper-V Manager on the Windows Vista machine to manage the Hyper-V server, the client typically does not have the permission to communicate with the file server on behalf of the Hyper-V server. You may enable constrained delegation on the Hyper-V server to authorize the impersonation. For more information, please refer to the following blog of Jose:
Laura Zhang - MSFTProblem - Q11: Negative ping times in virtual machines running on Hyper-V.
Symptom========
When you set virtual machines to run on multi-processors (e.g. two virtual processors), you may notice negative ping times in virtual machines that run on Hyper-V.
The output of the ping command may be:
Reply from <IP address>: bytes=32 time=-1ms TTL=128
Possible Cause
=============
This problem occurs because of the Win32 QueryPerformanceCounter function. By default it uses a time source called the TSC. This is a CPU time source that essentially counts CPU cycles. The TSC for each (virtual) processor can be different so there is no guarantee that reading TSC on one processor has anything to do with reading TSC on another processor. This means back to back reads of TSC on different VP's can actually go backwards. Hyper-V guarantees that TSC will not go backwards on a single VP.
Resolution
=========
You can add the /usepmtimer flag in boot.ini to change the time source for QueryPerformanceCounter from TSC to the PM timer which is a global time source.
For more details, please refer to the following blog article:
Tony Voellm's blog:
http://blogs.msdn.com/tvoellm/archive/2008/06/05/negative-ping-times-in-windows-vm-s-whats-up.aspx
Laura Zhang - MSFTProblem - Q12: You receive the error saying that “You do not have the required permission to complete this task.” when you try to manage the Hyper-V server remotely via the Hyper-V Manger console.
Symptom========
Consider the following scenario:
You have configured a Hyper-V server. You have another physical machine running either Windows Vista SP1 or Windows Server 2008.
You then want to manage the Hyper-V server remotely by using the Hyper-V management tools and encounter the following error message:
You do not have the required permission to complete this task. Contact the administrator of the authorization policy for the computer '<Hyper-V_server_name>'.
Resolution
=========
John Howard has described the cause and the detailed steps to resolve the problem in his blog. He also developed a tool (HVRemote) to automate the configuration. The following blog introduced this tool in detail:
Meanwhile, the following blogs describe how to configure these settings manually:
Part one and part two are for workgroup environment:
Part three is the server configuration for a server core installation in a workgroup environment:
Part four is for domain environment:
Part five is for the environment that domain client to workgroup server and, you are not using an administrative user account:
Laura Zhang - MSFT- Re Q1: To scan your entire IT environment, and get a report of machines supporting virtualization, use the Microsoft Assessment and Planning Toolkit solution accelerator at: http://technet.microsoft.com/en-us/library/bb977556.aspx
tony soper - RE Q 2: You can also find advice in the Virtual Machine Migration Guide: How To Migrate from Virtual Server to Hyper-V at: http://technet.microsoft.com/en-us/library/dd296684(WS.10).aspx
tony soper - RE Q 3: You can also find important blog posts explaining import/export at
http://blogs.technet.com/tonyso/archive/2009/08/04/hyper-v-r2-how-to-move-a-vm-storage-snapshots.aspx
tony soper - RE Q 4: If you use SCVMM to manage your Hyper-V hosts, the situation changes. Read the team blog post to understand the diffs:
http://blogs.technet.com/m2/archive/2009/01/12/azman-permissions-for-vmm-managed-hyper-v-hosts.aspx
tony soper
