CBruyland
October 27th, 2010, 01:12 PM
I'm in the process of automating the installation of Lucid on our Hyper-V guest machines.
The Hyper-V guest components kernel modules are not available in the initrd.gz,
I extracted the initrd.gz using:
gunzip -dc ../initrd.gz | cpio -imvd --no-absolute-filenamesDownloaded the full kernel package (linux-image-2.6.32-25-generic_2.6.32-25.45_amd64.deb), extracted the Hyper-V modules (hv_vmbus.ko, hv_storvsc.ko, hv_netvsc.ko and hv_blkvsc.ko).
I copied these files to the extracted initrd.gz:
/lib/modules/2.6.32-25-generic/kernel/drivers/staging/hv/and I recreated the initrd.gz using:
find . | cpio -o -H newc | gzip > ../initrd.gzNow when I boot using the custom initrd.gz, and change to another console, I can load these modules by hand; and the synthetic components are detected.
How can I change this, so these additional modules will be loaded during booting?
The Hyper-V guest components kernel modules are not available in the initrd.gz,
I extracted the initrd.gz using:
gunzip -dc ../initrd.gz | cpio -imvd --no-absolute-filenamesDownloaded the full kernel package (linux-image-2.6.32-25-generic_2.6.32-25.45_amd64.deb), extracted the Hyper-V modules (hv_vmbus.ko, hv_storvsc.ko, hv_netvsc.ko and hv_blkvsc.ko).
I copied these files to the extracted initrd.gz:
/lib/modules/2.6.32-25-generic/kernel/drivers/staging/hv/and I recreated the initrd.gz using:
find . | cpio -o -H newc | gzip > ../initrd.gzNow when I boot using the custom initrd.gz, and change to another console, I can load these modules by hand; and the synthetic components are detected.
How can I change this, so these additional modules will be loaded during booting?