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
- Without further information: Not really ;) Did you run at least "make modules_prepare" in your kernel directory?
-Stefan - How do I completely remove VB so I can start from scratch?
WhoCares? wrote: Without further information: Not really ;) Did you run at least "make modules_prepare" in your kernel directory?
-Stefan
Did one, but almost the same problem.. This time vboxdrv setup took some longer time, but it failed anyway..
If I remove everything and re-install it, can I follow the guide a couple pages back but change to the new version? And copy the file like you posted?- Sure. I just can't guarantee it will work then. I haven't tried to install VirtualBox on 4.2.16 yet, so I'm not yet familiar with all the possible problems and pitfalls.
-Stefan WhoCares? wrote: jmalmlund wrote: Edit: It seems Netgear has made some mistake or I'm just tired... the new GPL source supplied contains kernel version 2.6.37.5.RNx86_64.2.2 but the kernel that's included in 4.2.16 is version 2.6.37.5.RNx86_64.2.1
I don't know how you come to that conclusion. The GPL sources I'm using contain a kernel that identifies itself as "2.6.37.5.RNx86_64.2.1" - as can be checked bycd linux-2.6.37.5/arch/x86/configs
grep "RNx86" *
Should list defconfig.smp with a CONFIG_LOCALVERSION string of ".RNx86_64.2.1"
Well, just like you said Stefan, it was the second alternative that turned out to be correct, I was tired (and running a fever) and clearly not paying enough attention to what I was doing. Thank you for pointing that out to me ;)
When I started out working with *nix systems a friend of mine helped me and gave me a script that I've kept around , it's purpose was to make a diff between two kernel sources and transfer manual changes from the old source tree to the new one's config. A nice help back then before I learnt how to configure the kernel I needed for the computer I had, but not very foolproof I've now learnt... because I hadn't copied /arch/x86/configs/defconfig.smp to .config it took my entire .config file from the 4.2.15 source and basically copied that into the 4.2.16 source tree... now you might remember that the kernel in 4.2.15 was CONFIG_LOCALVERSION=".RNx86_64.2.2" and THAT'S what I saw and noticed that it didn't match `uname -r` ...
So this is to all I've might have offended by saying that the Netgear guys had messed up, Please forgive my mistake! :oops: :oops:
The good news is that since I started over with a fresh source doing all my changes manually I've now got all needed bits and pieces up and running and my VirtualBox servers are back up. Still running a slight fever so I'm going to hit the sack again (already slept most of the day) and unless someone else beats me to it I'll try and write an short how-to on installing/updating all that's needed to get VirtualBox up-to-date and running on 4.2.16.
Once again, thank you Stefan for :slap: you gave me, guess I needed it :roll: :lol:- Miniguide on installing/upgrading VirtualBox on RAIDiator 4.2.16.
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.16_WW_src.zip
unzip -q RNDP6xxx_4.2.16_WW_src.zip "linux-2.6.37.5/*"
ln -snf `pwd`/linux-2.6.37.5 /usr/src/linux
cd linux-2.6.37.5
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.0.4/VirtualBox-4.0.4-70112-Linux_amd64.run
wget -q http://download.virtualbox.org/virtualbox/4.0.4/Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack
chmod 755 VirtualBox-4.0.4-70112-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.0.4-70112-Linux_amd64.run uninstall
Section 4, install.
./VirtualBox-4.0.4-70112-Linux_amd64.run
/usr/bin/VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack
Note that it's the extpack that contains the RDP module...
Instructions on how to install/create/configure/start VM's might be added later if needed.
Edit: Fixed wrong parameter on uninstall command.
Edit 2: Added two lines to create a work-directory, "VirtualBox" on your data volume "c" to avoid filling the root filesystem (when logging in as root the default directory is /root/ which resides on the small 4GB system partition).
Also added a few "extra" make commands after Sebastien and I found that they were needed on his ReadyNAS to successfully build the VBox kernel modules, I didn't need them but since they don't hurt in any way (just takes a tad bit longer to complete the kernel preparations) I include them in the guide as a precaution. - Nice guide. Thanks.
-Stefan - Fantastic guide!
Would love to see instructions on how to install/create/configure/start VM's within this environment (I'm both a VB and linux noob).
- Robbie - Hello,
First, thank you for your instructions. VirtualBox works very well on RAIDiator 4.2.15 but since the update, and despite your guide, I can no longer start it.ChildNemesis:~# /usr/bin/VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (2.6.37.5.RNx86_64.2.1) 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 "/root/Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack": Extension pack 'Oracle VM VirtualBox Extension Pack' is already installed. In case of a reinstallation, please uninstall it firstChildNemesis:~# /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)
Would you have an idea of what to do? Sebastien wrote: Hello,
.....
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to install "/root/Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack": Extension pack 'Oracle VM VirtualBox Extension Pack' is already installed. In case of a reinstallation, please uninstall it firstChildNemesis:~# /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)
Would you have an idea of what to do?
Havin the same problem. vbox-install.logt0wnz:~# cat /var/log/vbox-install.log
Makefile:167: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
