Hyper-V synthetic network driver



  • Hyper-V synthetic network driver. Compiled it in amd64 freebsd8.3 pulled source from freebsd git. Not a clue if it works. Haven't tested it yet as I have a different virtual environment running currently. If you want to load it and see if it works at all I have attached it below

    
    1\. rename hv_vmbys.ko
    2\. add to /boot/modules
    3\. edit /boot/loader.conf.local and add hv_vmbus_load="YES" to load on start
    4\. kldload hv_vmbus.ko to load it once if you dont want to load on start
    4\. use kldstat to see if it has actually loaded or not. 
    
    
    
    1\. rename hv_netvsc.ko
    2\. add to /boot/modules
    3\. edit /boot/loader.conf.local and add hv_netvsc_load="YES" to load on start
    4\. kldload hv_netvsc.ko to load it once if you dont want to load on start
    4\. use kldstat to see if it has actually loaded or not. 
    
    

    Added the required module hv_vmbus
    hv_netvsc.ko.amd64.txt
    hv_vmbus.ko.amd64.txt



  • I gave these modules a try with a VM based on 2.1 release (I haven't tried with 2.1.1). They load (you can see them with kldstat and can see the hnX interfaces when running ifconfig). However, when you try and assign the interfaces, the VM reboots after displaying some errors quickly. I got the same behavior (reboot when assigning interfaces) when I tried downloading and installing the pre-compiled port for 8.3-amd64. I guess I'll have to figure out if the messages get saved in some log (any pointers?).

    As an alternative, I've been trying to add the port to a pfBuilder VM. I've tried adding the port to the build process, and while I got it to compile (after adding some destination directores to the Makefile), I still need to get the builder scripts to copy the files to the ISO and to enable the modules (ie, get the builder scripts to add the modules to the loader.conf on the CD?).

    I've also tried to create a patch from the source code and have the build scripts apply it as a patch to the pfSense source base. Albeit I'm not sure if that will make a difference (after all, it will still generate ko files): maybe there is a change in the pfSense source (maybe a pfSense modified include used by the hyperv-ic source) that would allow the ko modules to operate w/o crashing the VM? The problem I have on this process right now when I try and add hyperv-ic related changes is that the patch fails to apply changes to existing Makefiles (they seem to be read-only and get reset by the builder each time it runs?). Any ideas?



  • @zootie:

    I gave these modules a try with a VM based on 2.1 release (I haven't tried with 2.1.1). They load (you can see them with kldstat and can see the hnX interfaces when running ifconfig). However, when you try and assign the interfaces, the VM reboots after displaying some errors quickly. I got the same behavior (reboot when assigning interfaces) when I tried downloading and installing the pre-compiled port for 8.3-amd64. I guess I'll have to figure out if the messages get saved in some log (any pointers?).

    As an alternative, I've been trying to add the port to a pfBuilder VM. I've tried adding the port to the build process, and while I got it to compile (after adding some destination directores to the Makefile), I still need to get the builder scripts to copy the files to the ISO and to enable the modules (ie, get the builder scripts to add the modules to the loader.conf on the CD?).

    I've also tried to create a patch from the source code and have the build scripts apply it as a patch to the pfSense source base. Albeit I'm not sure if that will make a difference (after all, it will still generate ko files): maybe there is a change in the pfSense source (maybe a pfSense modified include used by the hyperv-ic source) that would allow the ko modules to operate w/o crashing the VM? The problem I have on this process right now when I try and add hyperv-ic related changes is that the patch fails to apply changes to existing Makefiles (they seem to be read-only and get reset by the builder each time it runs?). Any ideas?

    Hey unforunately there must be more work done to backport them then I have done. There are some 2.1 ISOs floating around on this forum that already have it all together. There are also some alpha 2.2 development images made in the developers forum on here have a look.



  • The unofficial aplha 2.2 images have now been removed!  :'(