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
cduce wrote: Any guidance on this will be appreciated :)
Did you see the post above?cmassey wrote:
So I decided to upgrade to 4.2.20 [T32] installed what I needed and moved back to 4.2.19 (not sure if this was a good or bad thing to do but no issues so far for the NAS or Virtualbox)- Hello,
I was a happy user on VMware server 2 on top on my readynas ultra 2+ but since I upgraded to the last releases, I have not been able to make it work again. I know, I should have waited for other folks to confirm it would still work...
This is really a pain because I was running a SSL VPn appliance and since I have no longer remote access to my network :cry:
So I decided to migrate to Virtual box and no joy I can not make it work.
I have followed the instructions on this forum but still not working.
I've got the following/usr/bin/VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.1.0-73009.vbox-extpack
/opt/VirtualBox/VBoxManage: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
The library is already on the nas:find -name libcrypt.so.1
./lib/libcrypt.so.1
so I tried to link it but still no joyln -s libcrypto.so.1 /lib/libcrypto.so.1
ldconfig
/usr/bin/VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.1.0-73009.vbox-extpack
/opt/VirtualBox/VBoxManage: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
openssl is the latest version on my nassudo apt-get install openssl
Reading package lists... Done
Building dependency tree... Done
openssl is already the newest version.
0 upgraded, 0 newly installed, 0 to remove
any ideas? - Just a quick update of the install instructions provided by jmalmlund...
I just ran through and updated this Miniguide on installing/upgrading VirtualBox 4.1.14 on RAIDiator 4.2.20.
Section 1 for new installations,
apt-get update
apt-get install build-essential amd64-libs lib64stdc++6 bzip2 lib64z1 lzma
apt-get --reinstall install libc6-amd64
Section 1 for upgrades,
apt-get update
apt-get -f install
Section 2 for both new installs and upgrades.
mkdir /c/VirtualBox
cd /c/VirtualBox
wget -q http://www.readynas.com/download/GPL/RNDP6xxx_4.2.20_WW_src.zip
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
make modules
cd ..
wget -q http://download.virtualbox.org/virtualbox/4.1.14/VirtualBox-4.1.14-77440-Linux_amd64.run
wget -q http://download.virtualbox.org/virtualbox/4.1.14/Oracle_VM_VirtualBox_Extension_Pack-4.1.14-77440.vbox-extpack
chmod 755 VirtualBox-4.1.14-77440-Linux_amd64.run
Section 3, optional for upgraders, not relevant for new installs.
IF upgraders want to start clean with the install insert this command now to uninstall previous lingering VirtualBox components.
./VirtualBox-4.1.10-73009-Linux_amd64.run uninstall
Section 4, install/upgrade VirtualBox
./VirtualBox-4.1.14-77440-Linux_amd64.run
Section 5, new installs
/usr/bin/VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.1.14-77440.vbox-extpack
Section 5, for upgrades,
It's to my knowledge not possible to just upgrade the extpack, the old one needs to be uninstalled to allow the new pack to be installed.
/usr/bin/VBoxManage extpack uninstall "Oracle VM VirtualBox Extension Pack"
/usr/bin/VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.1.14-77440.vbox-extpack
Note that it's the extpack that contains the RDP module...
Xaver added a really nice set of instructions on how to set up a basic virtual machine here, just keep in mind that most ReadyNas'es come with only 1GB ram, don't assign too much to your virtual machines or everything will come to a crawl if heavy memory swapping starts to occur.
Mini FAQ:
1. Are these instructions valid for my ReadyNas of type <insert your Nas here>?
If it has an 64bit intel CPU they should be. (I have a ReadyNas Pro Pioneer so if you have something else, well then your milage may vary and if so, then please help us by posting the specifics for your type of nas.)
2. Why is AMD stuff mentioned when the ReadyNas boxes use Intel cpu's?
Because the cpu is 64bit, more details by sphardy: here
3. A new version is out, (Radiator or VirtualBox), is this guide still valid?
Well, other than that you have to use other links and perhaps extract a newer kernel version than what's suggested herein you can still follow the guide and change to newer versions/links where needed.
ps. I've been thinking that it would be nice if there was a wiki so that it would be easier for anyone to help out keeping the instructions up to date... get in touch if you'd like to be a part of such a wiki-forum.[/quote] - 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# 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# /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)# modprobe vboxdrv
FATAL: Error inserting vboxdrv (/lib/modules/2.6.37.6.RNx86_64.2.2/misc/vboxdrv.ko): Invalid argument - 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? - As VirtualBox suggested when it failed: What's the output of "dmesg"?
-Stefan WhoCares? wrote: As VirtualBox suggested when it failed: What's the output of "dmesg"?
-Stefan
Hi Stefan, i put it here http://pastebin.com/vJYdmPSr- 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 indomiti wrote: 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# 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# /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)# 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.cmassey wrote:
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... :|
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
