Now i booted the migrated virtual pc image in Hyper-V, inserted the integration services image and installed it in the virtual machine. An information pop-up said:

A previous installation of Hyper-V integration services has been detected. Click OK to upgrade tor repair this installation.

Easy i thought, maybe the installer of the integration services has an upgrade product code in one of his MSI tables .. i decided to click OK. Another information:

The Hyper-V integration services have been successfully installed.

Then i rebooted the system and realized, that there is no mouse integration. Only Ctrl-Alt-Left released my captured mouse. Also no network card (NIC) was detected. i added a legacy adapter, this one got recognized. I ended up booting, adding and removing Network Adapters and Legacy Network Adapter.. until i found a post on social.technet.microsoft.com. The solution is:

1. start msconfig
2. go to the Boot tab
3. Click the Advanced options button.
4. Check the Detect HAL checkbox.
5. Click OK.
6. Click OK.
7. Reboot the vm.
8. Install Integration Services.

next time you boot, the virtual machine will detect the new Hyper-V HAL (Hardware Abstraction Layer) and it will pick the right drivers for it.

Another good note which helped me to diagnose this:

Open up a cmd:

set devmgr_show_nonpresent_devices=1

devmgmt.msc

now in Device Manager choose View – Show hidden devices

Now under Network Adapter, you’ll see a lot of old orphaned devices. You can clean them out – but don’t ask me which of them – that’s what you have to figure out yourself ..

Snapshots can be created in the Hyper-V Manager (by selecting a virtual machine and selecting Snapshot from the Action menu or panel) and in the Virtual Machine Connection window (by clicking on the snapshot button in the toolbar or by opening the Action menu and selecting Snapshot…).

Selecting to create a snapshot from the Virtual Machine Connection window will result in a dialog that allows you to enter a custom name for the snapshot (e.g. "Before applying Patches" or "Just before I do something stupid and ruin the virtual machine").  If you want you can dismiss this dialog and have the snapshot use an auto-generated name.  This auto-generated name will consist of the name of the virtual machine followed by the date and time when the snapshot was taken.

If you select to create a snapshot from the Hyper-V Manager the snapshot will be created with an auto-generated name.

Once you have created a snapshot you can view it in the Snapshots pane of the Hyper-V Manager by selecting the virtual machine that the snapshot is associated with.  Snapshots are displayed in the Snapshots pane in a hierarchal manner that describes the order in which the snapshots where taken.  One snapshot will have a green arrow head on top of it – this indicates that this snapshot was the last one to be taken or applied to the virtual machine.  When you select a snapshot there are a couple of options that are provided to you in the Action menu / panel:

fig. Hyper-V Actions Pane

fig. Apply, Rename, Delete Snapshot (Subtree)

• Settings…
  Selecting this will allow you to open the Virtual Machine Settings dialog with the settings that the virtual machine had when the snapshot was taken.  All the settings will be disabled – because a snapshot is essentially read only.  The only settings that you can change here are the snapshot name and the notes associated with the snapshot.
• Apply…
  Applying a snapshot to a virtual machine basically means copying the complete virtual machine state from the selected snapshot to the active virtual machine.  This process means that any unsaved data in the currently active virtual machine will be lost – and you will be asked if you want to create a snapshot of your current active virtual machine before the selected snapshot is applied.
  Once the snapshot is applied the virtual machine will either be in a saved state or stopped (depending on if the snapshot was taken of a running or stopped virtual machine).  If there are any settings that you need to change before starting the virtual machine you can now select the virtual machine, open the Virtual Machine Settings, and change them.
• Rename…
  This is a quick shortcut that allows you to rename a snapshot without having to open the Virtual Machine Settings.
• Delete Snapshot…
  Deleting a snapshot means that you can no longer restore the virtual machine to that point in time.  It is important to understand that deleting a snapshot will never effect any other snapshots, nor will it affect the current state of the virtual machine.  The only thing that will disappear is the selected snapshot.
  Sometimes in order to delete a snapshot we will need to merge the differencing disk that we created for the snapshot (this differencing disk is hidden from the user under most circumstances – I will talk more about the actual plumbing involved with snapshots another day).  This merging will happen automatically the next time that the virtual machine is not running.
• Delete Snapshot Subtree…
  Will delete the selected snapshot and any snapshots that are hierarchically underneath it.

Once you have snapshots associated with a virtual machine you can use the Revert option.  This will take a virtual machine back to the last snapshot that was taken or applied (indicated in the Snapshots pane by the green arrow head) and delete any changes that have been made since that snapshot.

http://code.msdn.microsoft.com/HVRemote

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.
The HAV detection tool helps you check if the computer processor supports hardware virtualization. The tool also checks if this feature is enabled on the processor.

Links

Download the Microsoft Hardware-Assisted Virtualization Detection Tool

The difference between Disk2vhd and other physical-to-virtual tools is that you can run Disk2vhd on a system that’s online. Disk2vhd uses Windows’ Volume Snapshot capability, introduced in Windows XP, to create consistent point-in-time snapshots of the volumes you want to include in a conversion. You can even have Disk2vhd create the VHDs on local volumes, even ones being converted (though performance is better when the VHD is on a disk different than ones being converted).

The Disk2vhd user interface lists the volumes present on the system:

It will create one VHD for each disk on which selected volumes reside. It preserves the partitioning information of the disk, but only copies the data contents for volumes on the disk that are selected. This enables you to capture just system volumes and exclude data volumes, for example.

    Note: Virtual PC supports a maximum virtual disk size of 127GB. If you create a VHD from a larger disk it will not be accessible from a Virtual PC VM.

To use VHDs produced by Disk2vhd, create a VM with the desired characteristics and add the VHDs to the VM’s configuration as IDE disks. On first boot, a VM booting a captured copy of Windows will detect the VM’s hardware and automatically install drivers, if present in the image. If the required drivers are not present, install them via the Virtual PC or Hyper-V integration components. You can also attach to VHDs using the Windows 7 or Windows Server 2008 R2 Disk Management or Diskpart utilities.

    Note: do not attach to VHDs on the same system on which you created them if you plan on booting from them. If you do so, Windows will assign the VHD a new disk signature to avoid a collision with the signature of the VHD’s source disk. Windows references disks in the boot configuration database (BCD) by disk signature, so when that happens Windows booted in a VM will fail to locate the boot disk.

Disk2vhd runs Windows XP SP2, Windows Server 2003 SP1, and higher, including x64 systems.

Here’s a screenshot of a copy of a Windows Server 2008 R2 Hyper-V system running in a virtual machine on top of the system it was made from:

Links

Download Disk2vhd (704 KB)

Run Disk2vhd now from Live.Sysinternals.com

Get it / read more here: PowerShell Management Library for Hyper-V

It is published on Codeplex

Finding a VM
Get-VM, Choose-VM , Get-VMHost

Connecting to a VM
New-VMConnectSession

Discovering and manipulating Machine states
Get-VMState , Set-VMState , Convert-VmState,
Ping-VM , Test-VMHeartBeat, Shutdown-VM , Start-VM, Stop-VM, Suspend-VM
Get-VMKVP, Add-KVP, Remove-KVP, Get-VMJPEG

Backing up, exporting and snapshotting VMs
Export-VM , Import-VM, Get-VMSnapshot, Choose-VMSnapshot , Apply-VMSnapshot , New-VMSnapshot ,Remove-VMSnapshot, Rename-VMSnapShot, Update-VMSnapshot, Get-VMSnapshotTree, Get-VmBackupScript

Adding and removing VMs, configuring motherboard settings.
New-VM , Remove-VM , Set-VM , Get-VMCPUCount, Set-VMCPUCount, Get-VMMemory, Set-VMMemory, Set-VMSerialPort

Manipulating Disk controllers, drives and disk images
Get-VMDiskController
Add-VMSCSIController , Remove-VMSCSIcontroller
Get-VMDriveByController , Add-VMDRIVE , Remove-VMdrive
Get-VMDiskByDrive, Add-VMDISK , Set-VMDisk, Get-VMDisk
Get-VMFloppyDisk , Add-VMFloppyDisk
Add-VMNewHardDisk

Manipluating Network Interface Cards
Get-VMNic , List-VMNic , Choose-VMNIC, Add-VMNIC, Remove-VMNIC , Set-VMNICAddress , Set-VMNICConnection , Get-VMNicport ,
Get-VMnicSwitch, Choose-VMSwitch, New-VMSwitchPort, Get-VMByMACaddress, Choose-VMExternalEthernet,
New-VMExternalSwitch, New-VMInternalSwitch,New-VmPrivateSwitch

Working with VHD files
Get-VHDDefaultPath, Get-VHDInfo, New-VHD, Compact-VHD, Test-VHD,Convert-VHD,Merge-VHD,Mount-VHD, Unmount-VHD

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.

Live migration

Live migration allows you to transparently move running virtual machines from one node of the failover cluster to another node in the same cluster without a dropped network connection or perceived downtime. Live migration requires the failover clustering role to be added and configured on the servers running Hyper-V. In addition, failover clustering requires shared storage for the cluster nodes. This can include an iSCSI or Fiber-Channel Storage Area Network (SAN). All virtual machines are stored in the shared storage area, and the running virtual machine state is managed by one of the nodes.

On a given server running Hyper-V, only one live migration (to or from the server) can be in progress at a given time. This means that you cannot use live migration to move multiple virtual machines simultaneously.

We recommend using the new Cluster Shared Volumes (CSV) feature of Failover Clustering in Windows Server 2008 R2 with live migration. CSV provides increased reliability when used with live migration and virtual machines, and also provides a single, consistent file namespace so that all servers running Windows Server 2008 R2 see the same storage.

Why is this change important?

Live migration does the following to facilitate greater flexibility and value:

• Provides better agility. Datacenters with multiple servers running Hyper-V can move running virtual machines to the best physical computer for performance, scaling, or optimal consolidation without affecting users.
• Reduces costs. Datacenters with multiple servers running Hyper-V can service their servers without causing virtual machine downtime or the need to schedule a maintenance window. Datacenters will also be able to reduce power consumption by dynamically increasing consolidation ratios and turning off unused servers during times of lower demand.
• Increases productivity. It is possible to keep virtual machines online, even during maintenance, which increases productivity for both users and server administrators.

read on here

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.