Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a fresh Debian 6.0.0 (Squeeze) server running on Hyper-V and I'm trying to get the synthetic drivers loaded into the kernel (2.6.32-5-amd64). The research I've done says that the Linux Integration Drivers should have been mereged into the .32 and greater kernel tree but I can't seem to find them in the normal /lib/modules/ directory. A modprobe also fails to locate and load the modules into the kernelspace.

I'm looking for the following kernel modules:

  • hv_vmbus
  • hv_blkvscb
  • hv_netvsc
  • hv_storvsc

Does anyone know where I can find the kernel moduels for the Hyper-V Linux Intergration Drivers? Have they been moved to their own package? Do I need to recomplile the kernel and manually build them?

share|improve this question
up vote 5 down vote accepted

A grep CONFIG_HYPERV /boot/config-2.6.32-5-amd64 shows CONFIG_HYPERV is not set. It appears that Debian has chosen not to build those modules. I am reading about it, several articles mention hv not being well supported by MS, and some people want to drop it.

I looked and the hv source is present in the 2.6.32 kernel source package (drivers/staging/hv). One thing you could do is install the kernel source package and the kernel-package tool. (apt-get install apt-get install linux-source-2.6 libncurses-dev kernel-package) Extract the source, copy /boot/config-2.6.32-5-amd64 to .config, use make menuconfig and enable the hyperv drivers. Then compile your kernel with make-kpkg.

For kernels with version >3.0 the drivers are no more located in staging. The new locations a described here:

share|improve this answer
Thanks for the answer. It does look like the Hyper-V modules are unfortunately not compiled in the default Debian Squeeze kernel. While I'm no strange to rebuilding the kernel, I'd rather not do it on a production machine unless the benefits outweigh the costs (and in this case they may not). – kce Feb 25 '11 at 23:09
It seems like it should be possible to recompile the modules without recompiling the entire kernel. I know both virtual box and vmware does permit you to compile the modules without rebuilding the kernel. I am not sure how to do that though. – Zoredache Feb 25 '11 at 23:24
For me, I get a kernel panic after each reboot unless I always remove the entry for the synthetic network card from /etc/udev/rules.d/70-persistent-net.rules – Kimvais Apr 8 '11 at 18:29
I get kernel error during startup using 2.6.36 with HV modules, anyone solved this trouble? Thank you. – Tobia Aug 24 '12 at 9:52

In order to get Hyper-V modules install on fresh Debian 6 in Hyper-V you need to compile your own kernel. This is how i did it

I think it is also applicable to Debian 5 and bunch of Ubuntu systems.

share|improve this answer

I've been able to have some moderate success with network drivers, but only when the vm was created on a hyperv console, not scvmm. In HyperV, selecting "Legacy Adapter" for network adapter type works.. I was able to get tcp connectivity to my vm. I did not stress the connectivity, or test it's stability, but it worked out of the box. I found a link on the web that gave me this method (currently uncited, but I'm sure you can find it..)

My version of scvmm does not list "Legacy Adapter" as a network cary type, however, so I can't get it to work without sideloading a driver after install.

Just for your notes..

share|improve this answer

Just as reminder: I have been playing with the Hyper-V modules for linux starting 2.6.33 and had freakingly bad results with hv module back these days. If you are using a mainline kernel, you get better results starting 2.6.39 where lots of changes whent in to get them quite stable.

I discourage anyone using hyper-v modules from mainline kernel in older kernels. The notable exception are the MS-provided ones for RHEL and SLES which are backports of later versions and work quite well.

share|improve this answer

more simple ;)

share|improve this answer
It's generally considered very poor form to post link-only answers on ServerFault. Please provide an explanation why you think your answer is appropriate and/or a summary of the information within the link. Answers that remain link-only may be removed by the moderators at their discretion. – Magellan Oct 12 '12 at 19:52

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.