NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Running VirtualBox VM host on ReadyNAS Pro
What is VirtualBox? So, I got bored while laundry was going... and decided to see how well a virtual OS would run on the Pro. My first choice of VM was VirtualBox, just cause I'm familiar with it a...
Okay, so I got VirtualBox amd64 4.1.18 working on 4.2.21.
Sorry this isn't really a step-by-step, but kind of a "what I did" using a very abbreviated version of j6harri's post (page 23, bottom) at
http://www.readynas.com/forum/viewtopic.php?f=35&t=26468&start=330#p352009
Got the source, put it in a directory and unzipped the whole thing, but you could probably just do
As far as I can tell, it's a vanilla kernel with the "netgearize" tool to make it device specific. I followed the README in the kernel directory:
Steps 1-3 immediately below are already done!
1) Grab your preferred kernel source tarball from kernel.org.
(eg. "# wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.4.tar.bz
2) Change to the directory that matches your selected kernel.
(eg. "# cd 2.6.32")
3) Extract it into this directory. That should leave you with a linux-2.6.xx directory.
4) Change into the new linux-2.6.xx directory.
(eg. "# cd linux-2.6.32.4")
5) Run the netgearize script.
(eg. "# ../netgearize_kernel.sh")
BUILD INSTRUCTIONS
x86_64 SMP
1) Copy the SMP defconfig file to .config.
# cp arch/x86/configs/defconfig.smp .config
2) Run 'make oldconfig'.
# make ARCH=x86_64 oldconfig
3) Build the kernel.
# make ARCH=x86_64
So under kernel/2.6.37/linux-2.6.37.6, run
It takes about 15 seconds with 2 "Hit Enter" prompts. It appears to copy the "defconfig.smp" from the directory above to .config .
Then I ran the Build Instructions above, steps 2 & 3 only because 1 was just done.
Make sure the symlink from /usr/src/linux points to whatever directory you decide to place your fresh kernel source.
ln -snf [your kernel source directory] /usr/src/linux
./VirtualBox-4.1.18-78361-Linux_amd64.run
Everything appeared to compile okay, but I couldn't load some of the VirtualBox modules like vboxnetflt.ko until I ran "depmod" and then was able to do "/etc/init.d/vboxdrv start"
Possibly "depmod -a" might do better even though I don't think ReadyNAS includes a modules.conf file.
A reboot confirmed that the vboxdrv and the four compiled modules (list using lsmod) were being loaded at boot. Then I could install the VBox Extensions.
Like I said in a previous post, under 4.2.20 I installed various packages from the debian archive to get some of my stuff working, like aptitude and mc, so I'm not sure how my build environment compares with other users'.
Off topic, I highly recommend mc for a quick and dirty Norton Commander. It makes it pretty painless to move stuff around and quick-view things. Read the F1 help for key commands, but "ctrl-t" selects.
I hope you all can get it working. I'm absolutely no expert, but was able to get the modules to compile and load. I may be able to help with errors -- I went through so many it may be tough to remember what I did for any particular one!
Sorry this isn't really a step-by-step, but kind of a "what I did" using a very abbreviated version of j6harri's post (page 23, bottom) at
http://www.readynas.com/forum/viewtopic.php?f=35&t=26468&start=330#p352009
Got the source, put it in a directory and unzipped the whole thing, but you could probably just do
unzip -q RNDP6xxx_4.2.21_WW_src.zip "kernel/*"
As far as I can tell, it's a vanilla kernel with the "netgearize" tool to make it device specific. I followed the README in the kernel directory:
Steps 1-3 immediately below are already done!
1) Grab your preferred kernel source tarball from kernel.org.
(eg. "# wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.4.tar.bz
2) Change to the directory that matches your selected kernel.
(eg. "# cd 2.6.32")
3) Extract it into this directory. That should leave you with a linux-2.6.xx directory.
4) Change into the new linux-2.6.xx directory.
(eg. "# cd linux-2.6.32.4")
5) Run the netgearize script.
(eg. "# ../netgearize_kernel.sh")
BUILD INSTRUCTIONS
x86_64 SMP
1) Copy the SMP defconfig file to .config.
# cp arch/x86/configs/defconfig.smp .config
2) Run 'make oldconfig'.
# make ARCH=x86_64 oldconfig
3) Build the kernel.
# make ARCH=x86_64
So under kernel/2.6.37/linux-2.6.37.6, run
../netgearize_kernel.sh
It takes about 15 seconds with 2 "Hit Enter" prompts. It appears to copy the "defconfig.smp" from the directory above to .config .
Then I ran the Build Instructions above, steps 2 & 3 only because 1 was just done.
Make sure the symlink from /usr/src/linux points to whatever directory you decide to place your fresh kernel source.
ln -snf [your kernel source directory] /usr/src/linux
./VirtualBox-4.1.18-78361-Linux_amd64.run
Everything appeared to compile okay, but I couldn't load some of the VirtualBox modules like vboxnetflt.ko until I ran "depmod" and then was able to do "/etc/init.d/vboxdrv start"
Possibly "depmod -a" might do better even though I don't think ReadyNAS includes a modules.conf file.
A reboot confirmed that the vboxdrv and the four compiled modules (list using lsmod) were being loaded at boot. Then I could install the VBox Extensions.
Like I said in a previous post, under 4.2.20 I installed various packages from the debian archive to get some of my stuff working, like aptitude and mc, so I'm not sure how my build environment compares with other users'.
Off topic, I highly recommend mc for a quick and dirty Norton Commander. It makes it pretty painless to move stuff around and quick-view things. Read the F1 help for key commands, but "ctrl-t" selects.
I hope you all can get it working. I'm absolutely no expert, but was able to get the modules to compile and load. I may be able to help with errors -- I went through so many it may be tough to remember what I did for any particular one!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
