Forum Replies Created
I didn’t do a rebuilt, I used the kernel Fulvio released at Oct, 12 to do the tests.
The last statement of Fulvio lets me hope that in the next kernel release the problem with the initrd is solved and the missing kernel module for native HV-networking is available. We’re also waiting for it. 🙂
Still new to this, trying to build a layered network (Client, Server, Hyper-v, External). I’m having a hard time understanding the firewall rules..
I keep locking myself out or allowing al servers to freely go surfing…..
Care to help me out and get up to speed…..
So to be sure:
Running Zeroshell in Hyper-v
Legacy Nic’s, VLAN not supported within zeroshell so you need to set it at NIC level. therefor basically limiting your zeroshell to max 4 networks?
At least that way it is working for me…..
Something else, is it me or is zeroshell capped at 100Mb/s, When I try to deploy a new VM from my serverlan to the Hyper-v host it will not go waster then 100 🙂
Ok, I understand.
What I did was quite simple, here a short summary:
- Extract the initrd.img to a temporary directory
- Edit the file init so that a shell is called before the boot process continues (almost at the end of the file).
- Copy the missing kernel module hv_vmbus.ko to the modules directory.
- Create a new newinitrd.img
- Boot with the new created newinitrd.img: While seeing the grub-menu press ‘e’ to edit the menu-entry and change the filename. Boot with pressing F10.
- The initrd will start a shell. Now you can load the kernel module hv_vmbus.ko manually and all the magic happens.
- Continue booting through exiting the shell (Strg+D)
As a native Microsoft guy, do you mind sharing the rebuild?
About the hyper-v support:
Do I understand these will be in the new kernel? does this include the drivers needed to support the native Hyper-v Nics?