Running VirtualBox VM host on ReadyNAS Pro

Hello,

I was finally able to compile the VirtualBox 4.1.14 modules on a Pro 4 with FW 4.2.20 by basing my kernel source off the vanilla 2.6.37.6 source from kernel.org and then using the kernel-build-tools that were circulating during the 4.2.20 betas to "netgearize" the source.

As detailed in alias' well-written post for USB sound modules:

http://www.readynas.com/forum/viewtopic.php?f=35&t=61970

For safety's sake, I used the T43 package rather than the T40. So my downloads were:

wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.37.6.tar.bz2
wget http://www.readynas.com/download/GPL/kernel-build-tools-x86-4.2.20-T43.tar.gz

I only did the compile steps listed in the linked post up to "make all," and skipped the

make menuconfig
make modules
make modules_install INSTALL_MOD_PATH=/
depmod -a"

but it probably wouldn't have broken it if I had run those commands...

So, from alias' post (changed "T40" to "T43"):

tar -xjf linux-2.6.37.6.tar.bz2 tar -xzf kernel-build-tools-x86-4.2.20-T43.tar.gz mv linux-2.6.37.6/ kernel-build-tools-x86/2.6.37/ cd kernel-build-tools-x86/2.6.37/linux-2.6.37.6/ ../netgearize_kernel.sh make oldconfig make all

Once "make all" was done for the altered source in my temp directory, I moved the official source out of the way and moved my new fresh source to my now-empty "2.6.37" directory so the system could find it - plus I didn't want to break my symlinks.

Anyway, after that, I was able to run the VirtualBox installer 4.1.14 for amd64, then I started vboxdrv service to confirm:

/etc/init.d/vboxdrv start
Starting VirtualBox kernel modules ...done.

then installed the extensions (uninstalled old ones first):

/usr/bin/VBoxManage extpack uninstall "Oracle VM VirtualBox Extension Pack"
wget http://download.virtualbox.org/virtualbox/4.1.14/Oracle_VM_VirtualBox_Extension_Pack-4.1.14-77440.vbox-extpack
 /usr/bin/VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.1.14-77440.vbox-extpack 

Then went to phpvboxmgr and cranked up my VM to test, and console was lit and worked.

With my particular 4.2.20 system, I had to get some packages from archive.debian.org to fill missing dependencies and to get my beloved aptitude working and a good compiling environment again. Unfortunately I can't trace exactly what I installed when, but hopefully everyone else has a sane build environment.

Thanks all for your informative posts. I was going crazy like everyone else with this broken source for 4.2.20, and thanks ReadyNAS devs for releasing the build tools during the beta--otherwise it could potentially be some time before the source might be fixed.

Happy VMing!