Hyper-V known Bug fixes

Backup

◆ If a VM is connected to a physical disk or iSCSI disk, the backup does not contain data on the physical disk connected to the VM or on the Internet SCSI (iSCSI) disk connected to the guest operating system. To solve this problem, use the backup proxy in the Virtual Machine and back up each virtual machine separately as a physical computer.

◆ Offline backup is supported only when the guest operating system is configured as a dynamic disk in the disk manager. During the backup process, if you try to back up this virtual machine, save it, and then start the backup again. Even if the VM is running, only offline backup can be performed. To avoid this problem, only one of the basic disks can be used for online backup. To solve this problem, Use offline backup or convert a dynamic disk to a basic disk.

◆ If you restore a backup Based on the Volume Shadow Copy Service (VSS) when the VM is running, the virtual opportunity ends in an inconsistent state. To avoid this problem, make sure that you select a running Virtual Machine in the backup application and then start the VSS restore operation. Make sure that the virtual machine is disabled before the VSS restore operation is started, and if the restoration is performed within the system, make sure that all virtual machines are disabled.

Security

◆ If Hyper-V authorized storage is in Active Directory, deleting a user from the role will not take effect immediately. Servers running Hyper-V [machines running VMMS] or Active Directory must be restarted before these changes can be applied. To avoid this problem, use the XML file as the storage type. To resolve this issue, restart the Hyper-V server, VMMS, and Windows Management Specification (NVSPWMI) service or Active Directory that hosts VMMS.

Operation

◆ If you try to restart or reset the VM when the memory of the physical computer is insufficient, the VM may be shut down rather than restarted. To avoid this problem, keep at least 512 MB of memory on the physical computer. To solve this problem, 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 allocated to the virtual machine.

◆ Ctrl + Alt + Del cannot be used for connection through "virtual machine connection" under "Remote Desktop" session. To avoid this problem, use Ctrl + Alt + End, avoid using "virtual machine connection" under "Remote Desktop" or using the Ctrl + Alt + Del option in the toolbar and the "operation" menu.

◆ Problems may occur when you try to connect a virtual hard disk (VHD) or ISO to a virtual machine from a network share. To avoid this problem, make sure that the Hyper-V server and the network server are members of the same domain. For users and computer accounts running Hyper-V servers, network sharing requires read access to ISO and read/write access to VHD. If you try not to use the user interface on the server running Hyper-V from the third computer ), you must enable the constraint delegation for the Server Message Block (SMB) between the server running Hyper-V and the network file server.

Related Articles]

• Tutorial: create and manage a Hyper-V virtual hard disk

• Integrate Hyper-V into Windows Server 2008 installation Source

• Create Microsoft Hyper-V Virtual Machine on windows server 2008