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 after using it for ages, plus its open and free :) Eventually, I may look into VMWare as well.
After a bit of messing around, got it installed. Since the system is based off of Debian, was easy to get VirtualBox itself there (deb package). The trickiest part was getting the kernel modules required installed (see end of post).
In the end, I've got Windows 2003 R2 running on my Pro, interacting with it via RDP, and I am happy with the performance. I've added an extra 1GB memory (for a total of 2GB). I assigned 1GB of ram to my virtual OS, which still leaves the default configuration of 1GB for the NAS itself (which is more than enough still, 800MB+ is always cached).
I made a 10GB virtual disk to install the OS on. If I need more space later for extra applications, I can just add another virtual drive to that installation. And since I always like a bit extra security, I went a bit beyond the usual, and also have TrueCrypt running full disk encryption in the virtual OS. So no one can even boot and read the data in that OS without my bootup password.
I don't really have any screenshots to show, just a standard Windows installation. Here is a few of the steps I used while creating the VM on the console:
VirtualBox 3.1 has changed the CLI configuration. Until I update this how-to, please reference this: http://www.uhleeka.com/blog/2009/12/vir ... 9-04-host/
With the OS booted up and just sitting at the desktop, top reports:
Ad-hoc installation of VirtualBox. Should work for RAIDiator 4.2.4. Download links for the kernel modules, for those who don't want to go through the mess of compiling them.
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 after using it for ages, plus its open and free :) Eventually, I may look into VMWare as well.
After a bit of messing around, got it installed. Since the system is based off of Debian, was easy to get VirtualBox itself there (deb package). The trickiest part was getting the kernel modules required installed (see end of post).
In the end, I've got Windows 2003 R2 running on my Pro, interacting with it via RDP, and I am happy with the performance. I've added an extra 1GB memory (for a total of 2GB). I assigned 1GB of ram to my virtual OS, which still leaves the default configuration of 1GB for the NAS itself (which is more than enough still, 800MB+ is always cached).
I made a 10GB virtual disk to install the OS on. If I need more space later for extra applications, I can just add another virtual drive to that installation. And since I always like a bit extra security, I went a bit beyond the usual, and also have TrueCrypt running full disk encryption in the virtual OS. So no one can even boot and read the data in that OS without my bootup password.
I don't really have any screenshots to show, just a standard Windows installation. Here is a few of the steps I used while creating the VM on the console:
VirtualBox 3.1 has changed the CLI configuration. Until I update this how-to, please reference this: http://www.uhleeka.com/blog/2009/12/vir ... 9-04-host/
# Creating the Virtual Machine.
$ VBoxManage createvm -name "Windows2003" -register
$ VBoxManage modifyvm "Windows2003" -memory "1024MB" -acpi on -boot1 dvd -nic1 nat
$ VBoxManage createvdi -filename "/c/backup/VirtualBox/Windows2003.vdi" -size 10000 -register
$ VBoxManage modifyvm "Windows2003" -hda "/c/backup/VirtualBox/Windows2003.vdi"
$ VBoxManage registerimage dvd /c/backup/VirtualBox/Windows2003Ent.iso
$ VBoxManage modifyvm "Windows2003" -dvd /c/backup/VirtualBox/Windows2003Ent.iso
$ VBoxHeadless -startvm "Windows2003" &
# Connected via Remote Desktop at this point.
# After the installation, first page requires Ctrl-Alt-Del, so I sent the keycodes.
$ VBoxManage controlvm "Windows2003" keyboardputscancode 1d 38 53
# System is up and running, time to install GuestAdditions for better video, etc.
$ wget http://download.virtualbox.org/virtualbox/2.2.2/VBoxGuestAdditions_2.2.2.iso
$ VBoxManage registerimage dvd /c/backup/VirtualBox/VBoxGuestAdditions_2.2.2.iso
$ VBoxManage controlvm "Windows2003" dvdattach /c/backup/VirtualBox/VBoxGuestAdditions_2.2.2.iso
With the OS booted up and just sitting at the desktop, top reports:
top - 16:17:10 up 1 day, 17:58, 1 user, load average: 0.00, 0.01, 0.00
Tasks: 93 total, 1 running, 92 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.7%us, 0.2%sy, 0.0%ni, 99.2%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 2072432k total, 2020100k used, 52332k free, 6120k buffers
Swap: 1048536k total, 144k used, 1048392k free, 784620k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
10297 root 20 0 1104m 1.0g 4720 S 4 52.5 57:31.53 VBoxHeadless
12792 root 20 0 46092 9520 1720 S 1 0.5 59:54.51 motion
12196 root 20 0 9196 7688 980 S 0 0.4 0:57.72 wastesrv
1 root 20 0 1948 600 508 S 0 0.0 0:01.30 init
Ad-hoc installation of VirtualBox. Should work for RAIDiator 4.2.4. Download links for the kernel modules, for those who don't want to go through the mess of compiling them.
$ mkdir /lib/modules/`uname -r`/miscOr, if you want to compile the kernel modules yourself:
$ cd /lib/modules/`uname -r`/misc
$ wget http://www.readynas.com/contributed/chirpa/modules/virtualbox/pro/vboxdrv.ko
$ wget http://www.readynas.com/contributed/chirpa/modules/virtualbox/pro/vboxnetflt.ko
$ echo "deb http://download.virtualbox.org/virtualbox/debian etch non-free" >> /etc/apt/sources.list
$ wget -q http://download.virtualbox.org/virtualbox/debian/sun_vbox.asc -O- | apt-key add -
$ apt-get update
$ apt-get install virtualbox-2.1
$ /etc/init.d/vboxdrv start
envyious:/c/backup# echo "deb http://download.virtualbox.org/virtualbox/debian etch non-free" >> /etc/apt/sources.listInstall of VirtualBox 2.2.2, before Sun updates the Debian Repository...
envyious:/c/backup# wget -q http://download.virtualbox.org/virtualbox/debian/sun_vbox.asc -O- | apt-key add -
envyious:/c/backup# apt-get update && apt-get install build-essential
...
Setting up build-essential (11.3) ...
envyious:/c/backup# wget -q http://www.readynas.com/download/GPL/RNDP6xxx_4.2.4_WW_src.zip
envyious:/c/backup# unzip -q RNDP6xxx_4.2.4_WW_src.zip -d ./GPL
envyious:/c/backup# cd GPL/linux-x86-2.6/
envyious:/c/backup/GPL/linux-x86-2.6# make && make prepare
...
envyious:/c/backup/GPL/linux-x86-2.6# ln -s /c/backup/GPL/linux-x86-2.6/ /usr/src/linux
envyious:/c/backup/GPL/linux-x86-2.6# KERN_DIR=/usr/src/linux
envyious:/c/backup/GPL/linux-x86-2.6# apt-get install virtualbox-2.1
...
Setting up virtualbox-2.1 (2.1.4-42893_Debian_etch) ...
Adding group `vboxusers' (GID 101) ...
Done.
Messages emitted during module compilation will be logged to /var/log/vbox-install.log.
Success!
Starting VirtualBox kernel module: done.
envyious:/c/backup/GPL/linux-x86-2.6# cd
envyious:/c/backup/GPL/linux-x86-2.6# VBoxManage list vms
VirtualBox Command Line Management Interface Version 2.1.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
# wget -q http://www.readynas.com/download/GPL/RNDP6xxx_4.2.4_WW_src.zip
# unzip -q RNDP6xxx_4.2.4_WW_src.zip -d ./GPL
# cd GPL/linux-x86-2.6/
# make && make prepare
# ln -s /c/backup/GPL/linux-x86-2.6/ /usr/src/linux
# export KERN_DIR=/usr/src/linux
# apt-get install libfontconfig1 libglib2.0-0 libice6 libsdl1.2debian libsm6 libx11-6 libxcursor1 libxext6 libxi6 libxmu6 libxrandr2 libxrender1 libxslt1.1 libxt6 python2.4
# wget -q http://download.virtualbox.org/virtualbox/2.2.2/virtualbox-2.2_2.2.2-46594_Debian_etch_i386.deb
# dpkg -i virtualbox-2.2_2.2.2-46594_Debian_etch_i386.deb
Setting up virtualbox-2.2 (2.2.2-46594_Debian_etch) ...
Recompiling VirtualBox kernel module: done.
Starting VirtualBox kernel module: done.
441 Replies
Replies have been turned off for this discussion
- I previously had this working on 4.2.19, just moved back and it is working fine. Will try T20 again later.
- Ok, i start from beginning, kinda..
# 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
# 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? - Why do you run the "silentoldconfig" part?
-Stefan WhoCares? wrote: 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"- 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# make ARCH=x86_64
# make CONFIG_DEBUG_SECTION_MISMATCH=y - Same problem here
:/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) - 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.... - 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 themake 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! - Could someone write a noobfriendly guide how to install/update with the new firmware?
Really dont want to mess up my nas :D - Hi
I really need help with reinstall virtualbox to ReadyNas Pro. I manage to get it work in 4.2.17 but now I have trying to remove it and make it work in 4.2.20. So I probably mess up my current installation.
First problem is error below (from apt-get update). I assume that it is something that I don't have to care (annoying but harmless). I'd like to fix it however...
W: GPG error: http://www.readynas.com 4.2.20/ Release: The following signatures were invalid: BADSIG B7F02108D553259A RAIDiator Release Key <admin@readynas.com>
W: You may want to run apt-get update to correct these problems
When I try to go thru section 2 I will get this error...
WARNING: modpost: Found 1 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
It comes in both make and make modules.
If I just ignore these and try "./VirtualBox-4.1.14-77440-Linux_amd64.run"
netgear:/c/Virtualbox# ./VirtualBox-4.1.14-77440-Linux_amd64.run
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation...........
VirtualBox Version 4.1.14 r77440 (2012-04-12T16:28:20Z) installer
Please install the build and header files for your current Linux kernel.
The current kernel version is 2.6.37.6.RNx86_64.2.2
Problems were found which would prevent VirtualBox from installing.
Please correct these problems and try again.
It is ok to remove all virtualbox settings (I don't have any old virtualbox running) but I need to sure need some instruction to do it.
-JeIlMa
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
