The following wiki – http://social.technet.microsoft.com/wiki/contents/articles/365.aspx – lists the top gotchas when using HyperV.
- Using Hyper-V snapshots
- Backing up and restoring virtual machines
- On Windows Server 2008 R2, virtual machines lose network connectivity under a heavy load
- Hyper-V Hotfix for “0x00000101 – CLOCK_WATCHDOG_TIMEOUT” on Nehalem systems
- On a Windows Server 2008 or 2008 R2 system that has the Hyper-V role installed, the startup time increases after backing up Hyper-V virtual machines
- VM unable to access the network after it has been configured to use a VLAN ID
- NIC driver issues using NIC Teaming on Broadcom NICs on Windows Server 2008 R2
- BIOS errors enabling Hyper-V
- Errors enabling Hyper-V
- Creating or starting a virtual machine fails with the error: ‘General access denied error’ (0x80070005)
- VM Export/Import permissions issues
- NIC listed as an unknown device in device manager
- Trying to run Hyper-V on a laptop
- Trying to run Hyper-V on a AMD E-350 motherboard
- Disk I/O trouble
- Running un-needed software, such as anti-virus on the parent partition (also called virtualization server and management partition)
- Slow system logon, sluggish keyboard and mouse
- Misconfiguration
- Active Directory Domain Controllers in VMs
- Backup and restore Domain Controllers the right way
- Beware of pending snapshot merges
