NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
chirpa
Mar 07, 2009Luminary
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
- chirpaLuminary(VirtualBox 3.1.8 is out: http://download.virtualbox.org/virtualbox/3.1.8/)
Your error above in previous posts looks like 32/64bit issues. I ran into it a long time ago, but haven't seen it in ages.
Someone bug me tomorrow and I'll try and get this post updated with 4.2.11/VB 3.1.8 fresh installation. - MackilaAspirantWhoCares? helped me by installing new 3.1.8 AMD64 .run binary of virtualbox.
We were able to successfully start virtual machines.
You need to apt-get some tools and libs to install virtualbox from binary installer (bzip2 as requested by binary installer, plus two libs - see last page of this thread).
As I got a brand new Pro yesterday, I will use it to make a step-by-step virtualbox install guide from factory reset-ed 4.1.9. - MackilaAspirantHere the step-by-step guide :D
All these steps were tested on a just-reseted 4.2.9 stock ReadyNAS PRO (no RAM or processor upgrade), with rootSSH.
# Get some needed tools
apt-get update
apt-get install build-essential
apt-get install bzip2
# Setup build environment
cd /c/backup
wget http://www.readynas.com/download/GPL/RNDP6xxx_4.2.9_WW_src.zip
unzip -q RNDP6xxx_4.2.9_WW_src.zip -d ./GPL
# Just wait
cd GPL/linux-x86-2.6/
make oldconfig
# Just press enter until make oldconfig ends
make && make prepare
# This step will take a while
ln -s /c/backup/GPL/linux-x86-2.6/ /usr/src/linux
KERN_DIR=/usr/src/linux
# Install virtualbox from binary installer
cd /c/backup
mkdir virtualbox
cd virtualbox
wget http://download.virtualbox.org/virtualbox/3.1.8/VirtualBox-3.1.8-61349-Linux_amd64.run
chmod 755 VirtualBox-3.1.8-61349-Linux_amd64.run
./VirtualBox-3.1.8-61349-Linux_amd64.run
# You will need the next 2
apt-get install lib64stdc++6
apt-get install lib64z1
# Get some live CD to test our VirtualBox installation
cd /c/backup
mkdir CDs
cd CDs
wget http://ftp.crihan.fr/releases/10.04/ubuntu-10.04-desktop-i386.iso
# Create the virtual machine
VBoxManage createvm --name Live --ostype "Linux" --register --basefolder /c/backup/virtualbox/machines
VBoxManage storagectl Live --name "IDE Controller" --add ide
VBoxManage storageattach Live --storagectl "IDE Controller" --port 0 --device 0 --type dvddrive --medium "/c/backup/CDs/ubuntu-10.04-desktop-i386.iso"
VBoxManage modifyvm Live --memory 512 --nic1 bridged --bridgeadapter1 eth0 --boot1 dvd --boot2 none --boot3 none --boot4 none
# Start the machine
VBoxHeadless --startvm Live --vrdp on &
# You now connect to your nas using any RDP client
I got this (after apt-get install htop && htop) :
http://mackila.com/VirtualBoxOnRNDP.jpg
Hope this will help :) - levityAspirant
chirpa wrote: Haven't tested this yet, but covers the basics of having the VM start and stop on bootup... (till super-poussin makes a nice GUI add-on for it ;)
Add these lines:
/etc/default/servicesMOTION=1
/etc/frontview/addons/addons.confVIRTUALBOX!!VirtualBox!!2.1.4!!/root/vboxctrl.sh start!!/root/vboxctrl.sh stop
i tried that but it was not successful...
on reboot the box seems to stop as it should, but it does not come up on startup
has anyone done this... - chirpaLuminaryThat first CODE box should say VIRTUALBOX, to match the first field in the 2nd CODE box, I must have been tired that night. Make sure both match and it should work for you.
- chirpaLuminaryVirtualBox 3.2.0 was released yesterday.
RAIDiator-x86 4.2.11 is due soon (T21 beta posted today), I am planning on doing a fresh install how-to on that version shortly, the steps should be a lot simpler now. - LichonAspirantTried on a new Pro with 4.2.9 (before my upgrade to Ext4). Not sure if your steps would work on a 4.2.9 Ext4 system.
viewtopic.php?p=231780#p231780
What risk there to use the compile method ? - chirpaLuminaryVirtualBox 3.2.2 released today: http://www.virtualbox.org/wiki/Changelog
- berkut1TutorOk, I think I am close to getting the VB working. I've been able successfully complete installation and building of the GPL 4.2.11 codes and installing VB 3.2.2 without errors. However when I attempt to execute VBoxManage I get the following error message:
nas3:/backup/CDs# VBoxManage list vms
/opt/VirtualBox/VBoxManage: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
I assumed that this is because I was missing libc6 or libc6-dev but both libraries are reported as being installed when I perform an apt-get install operation. And searching this forum I did not see at anyone having this error.
I would appreciate any help on this - as I'm itching to get this working. - WhoCares_MentorYou're right, libcrypt.so seems to be missing from 4.2.11 whereas it was part of 4.2.9. You can get it by doing:
apt-get update
apt-get install libc6-dev
This will install some other stuff on the ReadyNAS like the gcc compiler and such but since you're already compiling the VBox drivers I guess most of it should be there already.
What makes me wonder though is that your system reports libc6-dev as being installed. It wasn't on my system and installed just fine using the commands above.
Maybe you could try to remove libc6-dev using "apt-get remove libc6.dev" and re-installing it? As an alternative you could try toapt-get install aptitude
aptitude download libc6-dev
dpkg -i libc6-dev_2.7-18lenny2_i386.deb
-Stefan
Related Content
NETGEAR Academy

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