Feature #313

Linux Integration Components for Hyper-V

Added by Duane Hughes almost 2 years ago. Updated over 1 year ago.

Status:Closed Start date:03/08/2010
Priority:Normal Due date:
Assignee:Natanael Copa % Done:

100%
Category:Aports
Target version:Alpine 2.0.0

Description

Please see if it is possible to port the Linux ICs for Hyper-V to Alpine. The ICs are here: http://www.microsoft.com/downloads/details.aspx?FamilyID=c299d675-bb9f-41cf-b5eb-74d0595ccc5c&displaylang=en

Taking a look, it seems the setup.pl script needs adjustment for Alpine (as it refers to rpm package manager, for example), but not sure if more needs to be done.

History

#1
Updated by Natanael Copa almost 2 years ago

  • Target version changed from Alpine 1.10.0 to Alpine 2.0.0

#3
Updated by Duane Hughes over 1 year ago

RTM released: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=eee39325-898b-4522-9b4c-f4b5b9b64551

Hopefully this'll be put into linux kernel. Any more chance to test this coming up soon?

#4
Updated by Jeff Bilyk over 1 year ago

Downloaded V2.1, looking over readme, then makefile. Looks like there's a bunch of udev rules - which I think isn't yet implemented (question not statement)... Might need to wait until changeover to udev to get this running. Other problem is that I don't have a Hyper-V box to test this with...

#5
Updated by Duane Hughes over 1 year ago

I have a testing environment available if you would like to try your hand at it.

#6
Updated by Jeff Bilyk over 1 year ago

Mounted iso, and tried to run make. Multiple errors encountered. First was about INIT_WORK being passed too many arguments, so "fixed" osd.c so that it stopped running an if statement that was breaking things. Next, blkvsc_drv.c is encountering errors: 'struct device' has no member name 'bus_id', 'driver_data', etc. It looks like as of 2.6.26 there were some kernel changes that turned those into warnings, then they died in 2.6.30, turning into errors since the member doesn't exist anymore. I'm not sure how simple or complicated it would be to get this working with 2.6.32, I don't know enough about this level of programming to really fix this properly.

#7
Updated by Natanael Copa over 1 year ago

  • Category set to Aports

there are som hv drivers in staging area in kernel tree. we should try use those rather than build kernel modules from the iso. iirc those modules did some nasty things that made PAX/grsecurity barf. Once we have the kernel modules working we can start look at the userspace utilities. Not really sure what kind of userspace utils we need.

unless we get this working soon I'll reschedule it for 2.1.

#8
Updated by Natanael Copa over 1 year ago

there was some really nice breakthrough here

The kernel modules shipped with kernel work! Now the only remaining question is if we need any userspace tools from the MS integratinos tools ISO image?

Otherwise we can just close this.

#9
Updated by Natanael Copa over 1 year ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

I looked at the userspace tools on the iso from MS. We dont really need anything of it.

There was a vmbus init.d script that basically only did some modprobes, there was a modprobe.d/noatapiix that basically just disabled ata_piix kernel module, (this is better done with blacklist btw), there was some udev scripts that seemed to workaround some issues and seemed to autoconfigure the network interface (rehat style) and there was some grub and initrd update scripts that we really dont need.

I think we can make this work just by documenting what modules to add to /etc/modules and if needed, how to blacklist the ata_piix.

All drivers needed are in mainline kernel (in staging) and we dont need the userspace stuff (which is for suse/redhat anyways). I think we can just close this.

Thanks!

Also available in: Atom PDF