Bug#661318: linux-image-3.2.0-1-amd64: Possibility integrating newer Hyper-V paravirt drivers in squeeze?
Package: linux-2.6
Version: 3.2.4-1
Severity: wishlist
Dear Maintainer,
Thank you for enabling the Hyper-V drivers in the 3.2 builds, the
squeeze backport allowed me to test and confirm that they are not
as broken as they once were. (in fact: far more stable than they used to be)
Unfortunately the 3.2 kernel only contains the paravirt bus (hv_vmbus)
utility (hv_utils) drivers out of staging. While mouse, networking
block device drivers do work, it's only with Linux 3.3 that hv_mousevsc
(later: hid-hyperv), hv_netvsc have left staging.
linux-next also contains has hv_storvsc out of staging.
All 3 driver modules got a number of patches before they were accepted
to move out of staging. - Bug and feature fixes.
I for myself have tried and tested these drivers on a vanilla 3.2.x kernel
with success. Ubuntu will also base their LTS releas on the 3.2 kernel
- and they imported the changesets to their 3.2-based tree.
(See: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/929545)
My question is: I'd really like to see a well working Kernel for wheezy on Hyper-V,
and therefore would like to elaborate the possibility to integrate the changes
from 3.3/linux-next into the wheezy kernel branch.
Although no big kernel hacking experience, I would be willing to prepare patches
for wheezy if the kernel team would see that this backport would not hamper other
efforts in stabilizing wheezy.
Let me know if there is an interested and I'd be happy to prepare and test patches
on this platform.
-- Mathieu
*** End of the template - remove these lines ***
-- Package-specific info:
** Version:
Linux version 3.2.0-1-amd64 (Debian 3.2.4-1) (waldi@debian.org) (gcc version 4.6.2 (Debian 4.6.2-12) ) #1 SMP Sun Feb 5 15:17:15 UTC 2012
<snipped irrelevant info>
** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-1-amd64 root=UUID=4769ae1d-f6aa-4aea-89b9-69e1ac376533 ro quiet
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-3.2.0-1-amd64 depends on:
ii debconf [debconf-2.0] 1.5.41
ii initramfs-tools [linux-initramfs-tool] 0.100
ii linux-base 3.4
ii module-init-tools 3.16-1
Versions of packages linux-image-3.2.0-1-amd64 recommends:
ii firmware-linux-free 3
Versions of packages linux-image-3.2.0-1-amd64 suggests:
pn extlinux 2:4.05+dfsg-2
pn grub-pc 1.99-14
pn linux-doc-3.2 <none>
Versions of packages linux-image-3.2.0-1-amd64 is related to:
pn firmware-atheros <none>
pn firmware-bnx2 <none>
pn firmware-bnx2x <none>
pn firmware-brcm80211 <none>
pn firmware-intelwimax <none>
pn firmware-ipw2x00 <none>
pn firmware-ivtv <none>
pn firmware-iwlwifi <none>
pn firmware-libertas <none>
pn firmware-linux <none>
pn firmware-linux-nonfree <none>
pn firmware-myricom <none>
pn firmware-netxen <none>
pn firmware-qlogic 0.35
pn firmware-ralink <none>
pn firmware-realtek <none>
pn xen-hypervisor <none>
-- debconf information excluded
Reply to: