Running VirtualBox VM host on ReadyNAS Pro

[Nico21311]

Hello

I am very interresting for install VB on my readynas pro. But I read the topic and I don't understand the process.
I use windows 7 on my pc.
For install on pro need linux?


thanks by advance for your help.

[mdgm-ntgr]

You need to enable the root ssh add-on to enable ssh access to your NAS (note NetGear may deny support if you say e.g. delete something you shouldn't and your NAS stops working). Using linux commands can take a while to get used to.

[Nico21311]

It s possible install VB with T55?

Thanks by advance for your answer

[Bigbearf]

@chirpa

Basically, just download and install http://download.virtualbox.org/virtualb ... _amd64.run. Upon installation, it will compile the needed modules, if you have the kernel tree ready to go (apt-get install build-essential, and drop the GPL/linux-kernel-2.6 files in /usr/src/linux)

The second part of your statement "if you have the kernel tree ready to go (apt-get install build-essential, and drop the GPL/linux-kernel-2.6 files in /usr/src/linux" is a bit confusing to me. Could you be a little more step by step as far as this is concerned?

So far I have:
1. downloaded the .gz file and chmod +x the file
2. #tar xvf RAIDiator-x86-4.2.7-T51-Kernel.tar
3. #make && make prepare and got error to run make oldconfig and got "configuration written to .config"
4. Ran #make oldconfig and got "configuration written to .config"
5. Ran #make prepare (OK no errors)
6. Ran # ln -s /c/backup/GPL/linux-x86-2.6/ /usr/src/linux (OK I think.)
7. Ran #./VirtualBox-3.0.8-53138-Linux_amd64.run.sh

I see that the .gz file is T51 and I am running T55. Could that be the problem?
Thanks for your help.
BigBearf

[beisser1]

BigBearf wrote:
I see that the .gz file is T51 and I am running T55. Could that be the problem? Thanks for your help. BigBearf

no i have the same. the kernel sources havent changed between t51 and 55

[Nico21311]

hello

Is it possible to put this kernel version 2.6.30.9.RNx86_64.2.1 file on the forum.
Because the kernel of version T51 is not a good version

Thanks by advance.

If it s have an other method for install virtual box please write a clear tutorial.

Because I try 2 week end to install the virtual box without success.


Thanks by advance for your answer.

I using the version 4.2.7 T78

[chirpa]

The kernel zip of T51 would still work fine with T78.

Here is a 4.2.7 GPL bundle anyways with all the other junk in it: RAIDiator x86 4.2.7 GPL

[chirpa]

Here is my desk Pro that was running 4.2.5, updated to 4.2.7, installing VirtualBox for the first time...

# apt-get update;apt-get install build-essential amd64-libs lib64stdc++6 bzip2
...
Setting up build-essential (11.3) ...
Setting up amd64-libs (1.4) ...
Setting up bzip2 (1.0.3-6) ...
Setting up lib64stdc++6 (4.1.1-21) ...
# cd /c/backup/
# wget http://www.readynas.com/download/GPL/RNDP6xxx_4.2.7_WW_src.zip
2009-11-04 18:27:41 (2.97 MB/s) - `RNDP6xxx_4.2.7_WW_src.zip' saved [605547954/605547954]
# unzip -q RNDP6xxx_4.2.7_WW_src.zip -d ./GPL
# cd GPL/linux-x86-2.6/
# make oldconfig; make all
... ... (this takes a long time)
# ln -s /c/backup/GPL/linux-x86-2.6/ /usr/src/linux
# cd; wget http://download.virtualbox.org/virtualbox/3.0.10/VirtualBox-3.0.10-54097-Linux_amd64.run
2009-11-04 18:40:10 (4.21 MB/s) - `VirtualBox-3.0.10-54097-Linux_amd64.run?e=1257389097&h=da6ad1eb269ffcef8eb694d85ef1cab4' saved [50677201/50677201]
# mv VirtualBox-3.0.10-54097-Linux_amd64.run\?e\=1257389097\&h\=da6ad1eb269ffcef8eb694d85ef1cab4 VirtualBox-3.0.10-54097-Linux_amd64.run
# chmod +x VirtualBox-3.0.10-54097-Linux_amd64.run
# ./VirtualBox-3.0.10-54097-Linux_amd64.run
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.........
VirtualBox Version 3.0.10 r54097 (2009-10-29T13:31:14Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
/bin/bash: python: command not found
Building the VirtualBox vboxdrv kernel module
Building the VirtualBox netflt kernel module
Building the VirtualBox netadp kernel module
VirtualBox has been installed successfully.
# VBoxManage list hostinfo
VirtualBox Command Line Management Interface Version 3.0.10
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

Host Information:

Host time: 2009-11-05T02:56:21.269000000Z
Processor online count: 2
Processor count: 2
Processor#0 speed: 1800 MHz
Processor#1 speed: 1800 MHz
Memory size: 494 MByte
Memory available: 390 MByte
Operating system: Linux
Operating system version: 2.6.30.9.RNx86_64.2.1

[mdgm-ntgr]

If VirtualBox is installed, will it need to be removed before each RAIDiator upgrade and then re-installed afterwards?

Any plans for a community add-on to install VirtualBox?

[chirpa]

No, unless the kernel tree changes, not very often. And then, doesn't need re-installing, just re-compiling the kernel modules.

Its files will remain through firmware upgrades otherwise.

[Bigbearf]

@chirpa.
Thanks for the update. I will update firmware and try it tonight and post results.
BigBearf

[snipes]

Thanks Chirpa! Your instructions worked perfectly on T55.

[Nico21311]

hello

Thanks you chirpas for your tutorial

but i have an other problem

I following your tuto for start VB in same time of readynas but vb don't start automaticly?

Why

I try change VIRTUALBOX!!VirtualBox!!2.1.4!!/root/vboxctrl.sh start!!/root/vboxctrl.sh stop by VIRTUALBOX!!VirtualBox!!3.0.1!!/root/vboxctrl.sh start!!/root/vboxctrl.sh stop

not effect

Thanks by advance for your answer.

[Bigbearf]

@chirpa
Success!! VB 3.0.10 installed. I have got it installed now I just need to access it remotely and install XP3. Has anyone tried MS Home Server under VB on the RNP and if so any advantages or disadvantages? Any quick suggestions on how to access remotely anyone? A quick how to would be great. I have the VB User Manual that I will study this weekend and I have used it on my MBP just not remotely.
More to be learned and revealed.
BigBearf

[Nico21311]

hello

Problem resolved for start VB in same time of readynas

First adapt the script provide by chirpa sheet 5 this forum

and use this process

1) create a script
sudo nano /etc/init.d/vboxctrl.sh
3) executable script
chmod 700 /etc/init.d/vboxctrl.sh
4) create a link in /etc/rc2.d/ to put on /etc/rc2.d/ :
ln -s ../init.d/vboxctrl.sh S99vboxctrl.sh

[Nico21311]

hello

vb is ok

But I don't arrive to put a password for remote desktop

Thanks by advance for your answers

[lchapuis]

New VirtualBox 3.1 beta 1 has been installed successfully on 4.2.7 firmware

Changelog : http://forums.virtualbox.org/viewtopic.php?f=15&t=24458

[mdgm-ntgr]

Can a VirtualBox VM get control of the USB disks attached to the ReadyNas? Could this be used to recover data from a ReadyNas using USB onto a x86 ReadyNas without having to copy data over a network?

[alanpdodd]

Just got it working on 4.2.8 with the instructions from page 9 with the odd version change. No problems experienced.

[twinty7]

So... I've tried to read through all of the posts here - and unfortunately for a newbie like me - way above my head.

Has there been any progress made on a "How-To" or an Add-On that I've seen mentioned every now and then?

Or perhaps at least a start HERE and do these things....?

Thanks all - you guys rock !.

[Dwarf1]

Hi there,

After some mistakes and problems due to firmware changes offered by the v4.2.8, We successfully installed VirtualBox on 2 ReadyNAS Pro 6310 this Week-end with a friend of mine.

We used the Chirpa's step by step procedure found at page 9 and everything worked well (the make all step is quite loooooooooooooong ! lol) => thanks chirpa !

Then, we've tried to build our first VirtualMachine with VirtualBox v3.1.2 grabbed from the net and we've failed at some VBoxManage commands because they have changed since 3.0.x

The problem we met was that we couldn't attach the HDD/DVD to the virtualmachine. Later we found out why !
===> We needed to declare an IDE Controller and then attach the devices on it ! <===

OK said like that this seems to be a little bit "logic", but for 2 newbies of VirtualBox this wasn't ^_^

In fact, the "storage system" of VirtualBox have changed since 3.0 and here are the commands you need to do:

creation of the .vdi file !

VBoxManage createhd --filename "</PATH/TO .VDI FILENAME>" --size <SIZE IN MB> --register

Creation of the Controller(s) <== Needed to attach some HDD or DVD/Floppy Drive later

VBoxManage storagectl "<VM NAME>" --name "IDE Controller" --add ide

... but you can also create a SATA Controller (faster than IDE). Note that it seems that we can only attach HDD to a SATA Controller. I didn't succes to attach a DVD Drive to the Sata Controller

VBoxManage storagectl "<VM NAME>" --name "SATA Controller" --add sata

Now that you've got your Controller(s), you must attach some device !

For example, the HDD attached to the SATA Controller, and the DVD Drive with an ISO to the IDE controller.

VBoxManage storageattach "<VM NAME>" --storagectl "SATA Controller" --port 0 --type hdd --medium "</PATH/TO THE .VDI FILE DECLARED ABOVE>"
VBoxManage storageattach "VM NAME" --storagectl "IDE Controller" --port 0 --device 0 --type dvddrive --medium "</PATH/TO INSTALL ISOs>"

Earlier in that post, there were a remark about how to bridge the Network card of the VM to the Network card of the NAS. In v3.1.2 of VirtualBox, the argument changed again, no more use of "hostif"

To bridge the VM to a particular ethernet card of the NAS, the command is now :

VBoxManage modifyvm "VM NAME" --nic<1-N> bridged --bridgeadapter<1-N> <Host Ethernet Device, usually eth0 or eth1>

Hope this could help those who, like my friend and I, are new to VirtualBox experience with the ReadyNAS Pro 😛

@++
Dwarf

[Dwarf1]

New firmware available yesterday: v4.2.9

Has someone of you upgraded to 4.2.9 ??

No issue with VirtualBox after upgrade ?

@++
Dwarf

[chirpa]

I'll try it out tonight with 4.2.9.

[Dwarf1]

Successfully upgraded to firmware 4.2.9 (I used the patch of super-poussin to remove php before the upgrade !)

No problem with VirtualBox v3.1.2, my WinXP VM is working nice after upgrade !

@++
Dwarf

[MacManiak]

Dwarf wrote:
Successfully upgraded to firmware 4.2.9 (I used the patch of super-poussin to remove php before the upgrade !) No problem with VirtualBox v3.1.2, my WinXP VM is working nice after upgrade ! @++ Dwarf

Helloooooooo

I heard from Rom1 that 64bits system can't be installed ?
I think there's a compilation problem (forget the x64 options ?).

:)+