Using Virtualbox images with Hyper-V

In 2008 i wrote about using vmware images with virtualbox. To migrate a host from virutalbox to Hyper-V, you have to do nearly the same, but you have to convert the hdd:

• Convert your Virtualbox-hdd with VBoxManage.exe clonehd:
  (from vdi to vhd)

C:\Users\schroff>"\Program Files\Oracle\VirtualBox\VBoxManage.exe" clonehd
"c:\Users\schroff\VirtualBox VMs\Debian64-DS\Debian64-DS.vdi"
"c:\Users\schroff\VirtualBox VMs\Debian64-DS-Hyper-V"\Debian-DS.vhd
-format vhd

0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Clone hard disk created in format 'vhd'. UUID: c42129a8-c145-4a50-908c-023c8ed2b711

• Create a new virtual machine with Hyper-V:
• Create a vswitch
• Create a new host and add as existing hdd your cloned vhd-file
• Change the network adapter to legacy network adapter
• Start your new system...

Hyper-V: Compile Linux Kernel with Microsoft device drivers

After knowing, that running a linux inside Hyper-V is only working with the "legacy" network adapter (look here), i was trying to build a kernel with the drivers (Microsoft has added the drivers into the Linux kernel versions >2.6.32).
There is one nice tutorial out there:

• IT FROM ALL ANGLES: Hyper-V Guests: Compile Linux Kernel 2.6.32 on Debian 

But the menus of menuconfig have changed with kernel version 3.0. Microsofts Hyper-V kernel modules are no longer located inside the staging section. They can be found here:

Device Drivers --> Network device support -->

Device Drivers -->  Microsoft Hyper-V guest support -->

Device Drivers --> HID Support --> Special HID Drivers -->

All other steps work like described in IT FROM ALL ANGLES: Hyper-V Guests: Compile Linux Kernel 2.6.32 on Debian.
Microsoft offers a ISO-image for installing the kernel modules for some special kernel version for this linux distributions:

• Red Hat Enterprise Linux 5.7, 5.8, 6.0-6.3 x86 and x64
• CentOS 5.7, 5.8, 6.0-6.3 x86 and x64

The ISO-image can be downloaded from this location.

Note: If you try to build the kernel in you virtual machine, you need at least 6GB in /usr/src for compiling your kernel...

Hyper-V: Installing a debian linux in a virtual machine - trouble with the (non legacy) network adapter

First try with a virtualization solution like Hyper-V is to install a guest. So let's try debian linux.
The installer runs through this points:

1. Name & path of the virtual machine
2. RAM
3. Network (how to configure a virtual switch with internet connectivity or how to configure internet connectivity with NAT)
   at this point you have to choose no connection (i will explain this later)
4. Create a hdd
5. The summary should look like this:

Next step you have to open the configuration of this virtual machine. There you can see a network adapter with the following properties:

Bandwith management? This sounds really good. There are two types of network adapters:

A network adapter requires a virtual machine driver in order to work, but offers better performance. This driver is included with some newer versions of Windows. On all other supported operating systems, install integration services in the guest operating system to install the virtual machine driver. For instructions, see Install a Guest Operating System. For more information about which operating systems are supported and which of those require you to install integration services, see About Virtual Machines and Guest Operating Systems (http://go.microsoft.com/fwlink/?LinkID=128037).

A legacy network adapter works without installing a virtual machine driver. The legacy network adapter emulates a physical network adapter, multiport DEC 21140 10/100TX 100 MB. A legacy network adapter also supports network-based installations because it includes the ability to boot to the Pre-Execution Environment (PXE boot). However, the legacy network adapter is not supported in the 64-bit edition of Windows Server 2003. 

And now think about, for which type of network adapter the standard kernel has a kernel modul (or you can get sources for)... Right. Only the legacy adapter.
So you have to delete the network adapter and add a legacy network adapter. After this step, your virtual machine should look like:

The bandwidth management is gone, but your kernel can use the tulip module and your network is working... Here you have to choose a virtual switch, which you can create like described in these two postings:  how to configure a virtual switch with internet connectivity or how to configure internet connectivity with NAT.

It is not really suprising, that Microsoft adds as default to each new virtual machine a network adapter, which only works on a few linux distributions. You can download drivers from microsoft via this page (scroll down to "integration services"). But to add the default each for every new virtual machine, so that you have to delete this one and add the "legacy" adapter.

But after knowing this, it is no problem to install debian linux (or any other linux) onto your Hyper-V.

Hyper-V: Howto configure NAT for virtual machines

In my last posting i explained how to configure a vEthernet adapter to get connectivity to the internet. But there was one "problem": You had to provide one seperate IP for each virtual host, you want to connect to the internet.
But there is a solution (NAT) for this problem and it is easy to configure this with Hyper-V on Windows:
[If you have not configured the "brigde"-solution i explained the last posting, then skip step 1 and start with step number 2]

1. Unbridge your VSwitchExternal from Wifi
   (select both adapter in network adapters and do a right click an use "remove bridge")
2. Create a new internal virtual switch via Hyper-V's virtual switch manager (look here, how to do this) and name it VSwitchNAT
3. Edit properties of your Wifi adapter
   (right click and then properties)
4. Open the tab "Sharing" and enable both Checkboxes.
   Choose "VSwitchNAT" for Home networking connection
   

And after that your virtual machines are using a private subnet which will be NATted by your laptop. This private subnet can be configured via VSwitchNAT:

• Edit properties of VSwitchNAT vEthernet adpater
• Edit properties of ipv4 and here you can edit the subnet