| Ok, today i migrated one of my old Virtual PC Images (VPC) (VHD File) to Hyper-V. I booted the Virtual PC virtual machine and removed the old virtual machine additions. Then i created a new virtual machine in Hyper-V and specified the VHD as Disk. |  |
| Hyper-V introduces the concept of virtual machine snapshots – which is to say point in time images of a virtual machine that you can return to at any stage. These snapshots are implemented in the virtualization layer – and can be taken at any time with any guest operating system (even during an operating system installation). Snapshots can be taken whether the virtual machine is running or stopped. If the virtual machine is running when the snapshot is taken there is no downtime involved to create the snapshot. |  |
| HVRemote reduces the manual configuration steps needed for Hyper-V Remote Management down to a few simple commands. |  |
|
The Hardware-assisted virtualization (HAV) detection tool checks if the computer processor supports HAV and if this setting is enabled. Windows Virtual PC requires processors capable of hardware-assisted virtualization with AMD-V™, Intel® VT or VIA® VT turned on in the BIOS. |
 |
Disk2vhd is a utility that creates VHD (Virtual Hard Disk – Microsoft’s Virtual Machine disk format) versions of physical disks for use in Microsoft Virtual PC or Microsoft Hyper-V virtual machines (VMs).
Absolutely cool and awesome, a Management Library for PowerShell to manage your Hyper-V Virtual Machines and Hosts using Microsoft PowerShell.
Get it / read more here: PowerShell Management Library for Hyper-V
It is published on Codeplex
The Hyper-V role in Windows Server 2008 R2 provides you with the tools and services you can use to create a virtualized server computing environment. This virtualized environment can be used to address a variety of business goals aimed at improving efficiency and reducing costs. 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.
According the the release notes of Microsoft Windows Server 2008 R2, the Hyper-V role now fully supports Live Migration of Virtual Machines using the failover clustering role, added and configured on the servers running Hyper-V.
It’s not the first time i got this error message and since i’ve solved it, i thought i’ll share this with the rest of the world.
a quote from an Microsoft Blog Post on Technet:
For those of you who’ve enabled the Hyper-V role in WS08. It has been determined that a certificate error can occur resulting in the inability to start or connect to virtual machines running on Windows Server 2008 or Microsoft Hyper-V Server 2008. The Hyper-V virtualization host and the existing virtual machines will continue to operate without disruption. A hotfix designed to prevent/resolve this error has been created and is available for download starting today. The following is a brief description of the issue as well as a link to the KB Article that provides the resolution. Even if you are not currently experiencing this issue, we recommend you download and install this update.
Symptoms and Resolution
§ You may be unable to start or connect to virtual machines running on Windows Server 2008 or Microsoft Hyper-V Server 2008. This occurs when connecting using vmconnect. Connections made using remote desktop won’t be affected.§ KB Article 967902 has been created that details the symptoms and resolution. This KB article provides a direct link to download the quickfix to resolve this error.
if you get one of these error messages:
apply this (KB967902) MS Hotfix to solve this issue.
