NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
enxer
Jul 15, 2016Aspirant
RN31200 - Installing virtualbox on ReadyNas 6.5.0
I just recently purchased a 312 and I've been following JMehring's post: https://community.netgear.com/t5/Community-Add-ons/Virtualbox-on-OS6-NAS/td-p/902756 and I get stuck on installing virtualbox ...
- Jul 24, 2016
Sorry for not getting back to you until now - I saw your post but two active kids kept me busy from repling to these threads I've made.
So I posted over in virtualbox and they reiterrated that my headers I built were not matching the running ones dispite the uname -r matching so I scraped everything, purged all modules and /usr/src and reviewed the orginal url that this author got. I pulled a similar name down that matched my readynas os 6.5.1 and made them. Additionally I added the debian repository for virtualbox wheezy and I installed dkms which monitors for kernel header changes and compiles based on the kernel modules in the system. This got me to be able to install 4.3.8 which is happily running my Windows 7 32bit (I have atom processor (non-VT-x)) running Passwordstate for the house quite well.
I hope my post helps someone out!
powareverb
Jul 23, 2016Star
Trying the same thing here, and also having issues with module magics, though it's possibly something else I'm doing wrong.
Out of interest, you've mentioned directory showing some additional number in it (197):
linux-4.1.21-197-x86_64
The kernel dir I have out of the latest zip here:
http://www.downloads.netgear.com/files/GPL/ReadyNASOS_V6.5.1_WW_src.zip
just has a directory called:
linux-4.1.21-x86_64
With this kernel:
head -4 /usr/src/linux/Makefile VERSION = 4 PATCHLEVEL = 1 SUBLEVEL = 21 EXTRAVERSION = NAME = Series 4800
Where'd you get the kernel sources with this extra number in the directory name?
As for my lack of success, I'm not even able to
sudo cp .config .config-old sudo cp arch/x86/configs/defconfig.x86 .config sudo make clean sudo make ARCH=x86_64 sudo make modules_install ARCH=x86_64
then
sudo modprobe configs # modprobe: can't load module configs (kernel/kernel/configs.ko): invalid module format
So I'm expecting anything the VirtualBox installer is trying to build will fail with mismatches also.
sudo modinfo configs vermagic: 4.1.21.x86_64.1 SMP mod_unload modversions uname -r 4.1.21.x86_64.1
Seems... Odd to me.
ReadyNAS 6.5.1
RN516
- powareverbJul 24, 2016Star
Actually sorted this out in the end.
On a hunch I'd got the wrong config, I had a look around and realised there's a special config file for the readynas setup...
#Normal #sudo cp arch/x86/configs/defconfig.x86 .config #ReadyNAS sudo cp arch/x86/configs/readynas_defconfig .config
Give this a shot and see if it works. You may need to do a clean out first (of /lib/modules & kernel build dir).
Have written up a full description based on a number of great forum posts.
Kernel build:
https://gist.github.com/powareverb/5a59e4e68c7e56033ba0998ef3b53b94
VirtualBox build:
TBC
- enxerJul 24, 2016Aspirant
Sorry for not getting back to you until now - I saw your post but two active kids kept me busy from repling to these threads I've made.
So I posted over in virtualbox and they reiterrated that my headers I built were not matching the running ones dispite the uname -r matching so I scraped everything, purged all modules and /usr/src and reviewed the orginal url that this author got. I pulled a similar name down that matched my readynas os 6.5.1 and made them. Additionally I added the debian repository for virtualbox wheezy and I installed dkms which monitors for kernel header changes and compiles based on the kernel modules in the system. This got me to be able to install 4.3.8 which is happily running my Windows 7 32bit (I have atom processor (non-VT-x)) running Passwordstate for the house quite well.
I hope my post helps someone out!
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!