Running VirtualBox VM host on ReadyNAS Pro

[Xaver]

is it save to upgrade from 4.2.17 to 4.2.20 with VBox Installed or should i first deinstall the Vbox and so on before Update.

does the 4.2.20 now support the reinstall of the Vbox system?

[WhoCares?]

As VirtualBox suggested when it failed: What's the output of "dmesg"?

-Stefan

[indomiti]

As VirtualBox suggested when it failed: What's the output of "dmesg"?

-Stefan

Hi Stefan, i put it here http://pastebin.com/vJYdmPSr

[WhoCares?]

Pretty much looks like you did something wrong when compiling the modules or preparing the kernel tree but from your snippets I can't really say what exactly. My best advice would be to start from scratch, this is what fixes these kind of problems for me.

-Stefan

[cmassey]

I tried to follow j6harri guide but i think something goes wrong with my VirtualBox kernel modules?

RAIDiator 4.2.20 and VirtualBox 4.1.14

Code: Select all

# VBoxHeadless -startvm "Debian" &
[1] 12927
Netgear-NAS:/c/VirtualBox# WARNING: The vboxdrv kernel module is not loaded. Either there is no module
         available for the current kernel (2.6.37.6.RNx86_64.2.2) or it failed to
         load. Please recompile the kernel module and install it by

           sudo /etc/init.d/vboxdrv setup

Code: Select all

# /etc/init.d/vboxdrv setup
Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...failed!
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)

Code: Select all

# modprobe vboxdrv
FATAL: Error inserting vboxdrv (/lib/modules/2.6.37.6.RNx86_64.2.2/misc/vboxdrv.ko): Invalid argument

Not that this is going to help but I have the same issue.
Was working fine until I upgrade to T20, it stopped working after the upgrade tos so I reinstalled, and still not working.

Will keep playing and may roll back firmware to see if that fixes the issue.

[InTheShires]

Was working fine until I upgrade to T20, it stopped working after the upgrade tos so I reinstalled, and still not working.

Will keep playing and may roll back firmware to see if that fixes the issue.

4.2.17 was all I could make it work happily with. I tried the final of 4.2.19, and a couple of 4.2.20 Txx betas, but never got it running happily. I've resisted the urge to try 4.2.20 Final so far...

[cmassey]

I previously had this working on 4.2.19, just moved back and it is working fine. Will try T20 again later.

[indomiti]

Ok, i start from beginning, kinda..

Code: Select all

# cd /c/VirtualBox
# apt-get update
# apt-get install build-essential amd64-libs lib64stdc++6 bzip2 lib64z1 lzma
# apt-get --reinstall install libc6-amd64
# apt-get -f install
# rm -rf linux-2.6.37.6
# unzip -q RNDP6xxx_4.2.20_WW_src.zip "linux-2.6.37.6/*"
# ln -snf `pwd`/linux-2.6.37.6 /usr/src/linux
# cd linux-2.6.37.6
# cp arch/x86/configs/defconfig.smp .config
# make ARCH=x86_64 silentoldconfig
# make prepare
# make modules_prepare
# make, this warning comes at the end:
WARNING: modpost: Found 1 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'


So i do make CONFIG_DEBUG_SECTION_MISMATCH=y

Code: Select all

# make CONFIG_DEBUG_SECTION_MISMATCH=y, this warning comes at the end:
WARNING: drivers/target/target_core_mod.o(.text+0x5cf5): Section mismatch in reference from the function init_module() to the function .init.text:rd_module_init()
The function init_module() references
the function __init rd_module_init().
This is often because init_module lacks a __init
annotation or the annotation of rd_module_init is wrong.


Could this be the cause of the problem?

[WhoCares?]

Why do you run the "silentoldconfig" part?

-Stefan

[indomiti]

Why do you run the "silentoldconfig" part?

-Stefan

I dont know why, i just followed j6harri's guide... it says to do "make ARCH=x86_64 silentoldconfig"

[laksmkk]

Did anyone had a successful installation with RAIDiator-x86-4.2.20 and running VirtualBox 4.1.14? I just fallowing step by step written by jmalmlund.
Virtualbox itself install fine but when I try to install VirtualBox 4.1.14 Oracle VM VirtualBox Extension Pack is giving me errors like the people above me.
I did run

Code: Select all

# make ARCH=x86_64
# make CONFIG_DEBUG_SECTION_MISMATCH=y

[gexxie]

Same problem here

Code: Select all

:/vm# sudo /usr/bin/VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.0.2-69518.vbox-extpack
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
         available for the current kernel (2.6.37.6.RNx86_64.2.2) or it failed to
         load. Please recompile the kernel module and install it by

           sudo /etc/init.d/vboxdrv setup

         You will not be able to start VMs until this problem is fixed.
0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to install "/c/vm/Oracle_VM_VirtualBox_Extension_Pack-4.0.2-69518.vbox-extpack": Extension pack 'Oracle VM VirtualBox Extension Pack'is already installed. In case of a reinstallation, please uninstall it first

NAS:/vm# sudo /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules ...done.
Uninstalling old VirtualBox DKMS kernel modules ...done.
Trying to register the VirtualBox kernel modules using DKMS ...failed!
  (Failed, trying without DKMS)
Recompiling VirtualBox kernel modules ...failed!
  (Look at /var/log/vbox-install.log to find out what went wrong)



[indomiti]

I have not found any solution to this yet.
I am not good enough to figure out whats going wrong when compiling the modules for the kernel, or if that is even the problem or not....

[itachi1]

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:

Code: Select all

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

Code: Select all

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"):

Code: Select all

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:

Code: Select all

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

then installed the extensions (uninstalled old ones first):

Code: Select all

/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!

[shjips]

Could someone write a noobfriendly guide how to install/update with the new firmware?

Really dont want to mess up my nas