Neither, you'll have to build from source. The ReadyNAS firmware is built on etch but with some updated packages from Lenny thrown in. So chances are you won't be able to use any external .deb packages without major modification to the ReadyNAS base system.
So - I finally got around to reinstalling VB on my Ultra-4.
Here are the steps I used to install the 64 bit version of VB 3.2.8 under RAIDiator 4.2.13 - all worked perfectly first time (though hope I haven't forgotten to copy/paste something)
I would like to throw in a wild question in here ... if the answer is "yes" I'll open a separate topic on it ...
On a Pro, running Virtual Box, running Opensolaris, using ZFS ... would deduplication be supported /working (possibly given enough memory is installed) ?
Well, the general answer is: Yes, it should. But whether it really works or not you'll have to try for yourself. But since in this scenario OpenSolaris would be the guest machine I see no special benefit in using dedup there.
Just updated to 3.2.10 on my Ultra-4 - update went fine.
I have seen the following issue - so hopefully solved in this release as the change log claims:
VBoxHeadless: fixed event queue processing problems which led to hangs if the VM could not be started successfully
Also noticed there is a new startup script included for vboxwebsrv (/etc/init.d/vboxweb-service) To get it to work however, needed to define the user vboxdrv runs as in /etc/vbox/vbox.cfg - just add the line:
In a nutshell: shut down all running virtual machines, shut down VirtualBox, download the new version of VirtualBox, install and compile the drivers as you did with the old version, restart VirtualBox, restart virtual machines.
So - I finally got around to reinstalling VB on my Ultra-4.
Here are the steps I used to install the 64 bit version of VB 3.2.8 under RAIDiator 4.2.13 - all worked perfectly first time (though hope I haven't forgotten to copy/paste something)
I think that by default, the Vm rdp port is @8888 so you should try to connect to : ip_of_vm:8888 Keep us posted if it's ok or not
I tried to connect VM use port 8888 but failed.. Any more advice?
I think the default RDP port is 3389. If you have a Windows system, just connect to the NAS IP, not the IP of the VM (although I'm sure that should work too if it's a Windows VM).
For example, I ran:
$ VBoxHeadless --startvm "WinXP" Oracle VM VirtualBox Headless Interface 3.2.8 (C) 2008-2010 Oracle Corporation All rights reserved.
I think that by default, the Vm rdp port is @8888 so you should try to connect to : ip_of_vm:8888 Keep us posted if it's ok or not
I tried to connect VM use port 8888 but failed.. Any more advice?
I think the default RDP port is 3389. If you have a Windows system, just connect to the NAS IP, not the IP of the VM (although I'm sure that should work too if it's a Windows VM).
For example, I ran:
$ VBoxHeadless --startvm "WinXP" Oracle VM VirtualBox Headless Interface 3.2.8 (C) 2008-2010 Oracle Corporation All rights reserved.
Listening on port 3389.
and connected with Windows RDP with <readynas ip>
I have reinstalled the VB 3.2.8 then it works perfectly. In VB 4.0, when I enter the 'VBoxHeadless --startvm' command, "Listening on port 3389" is doesn't appeared. I guess VB 4.0 is not compatible with RADIator 4.2.15 yet. Specially network adapter..
For those who like me update to VirtualBox 4.0.x, remember that Oracle have change how VBox is packaged and distributed (all binaries are now GPLv2 and no longer ships with VRDP support built in).
This is what I did to install and run 4.0.2 (slightly adopted for easier copy and paste of my commands) and remember that if you log in as root (you really shouldn't) you can skip the 'sudo' part of all the listed commands.
Note that it's the extpack that contains the RDP module...
I won't repeat instructions on how to do a basic setup of a virtual machine, only the additions/changes needed for VBox 4.0
VBoxManage modifyvm <uuid|name> --vrde on --vrdeaddress <host ip> --vrdeport <port for RDP>
After this all that's needed to start is
VBoxHeadless --startvm <uuid|name> &
Or if you don't want to configure your machines with static ip/ports for RDP use
VBoxHeadless --startvm <uuid|name> --vrde on --vrdeaddress <host ip> --vrdeport <port for RDP> &
Edit: Added an '&' to the start command to put the process in the background and returning you to the prompt, which enables you to logout and disconnect your ssh session.
Do I have to keep the SSH client open the whole time a VM is running?
When I close putty, my VM closes. Anyway around this?
Thanks.
Edited my start command in the previous post.. you just need to add an '&' to the end of the start command to put the VBox process into the background allowing you to disconnect your ssh session.
For those who like me update to VirtualBox 4.0.x, remember that Oracle have change how VBox is packaged and distributed (all binaries are now GPLv2 and no longer ships with VRDP support built in).
This is what I did to install and run 4.0.2 (slightly adopted for easier copy and paste of my commands) and remember that if you log in as root (you really shouldn't) you can skip the 'sudo' part of all the listed commands.
Note that it's the extpack that contains the RDP module...
I won't repeat instructions on how to do a basic setup of a virtual machine, only the additions/changes needed for VBox 4.0
VBoxManage modifyvm <uuid|name> --vrde on --vrdeaddress <host ip> --vrdeport <port for RDP>
After this all that's needed to start is
VBoxHeadless --startvm <uuid|name> &
Or if you don't want to configure your machines with static ip/ports for RDP use
VBoxHeadless --startvm <uuid|name> --vrde on --vrdeaddress <host ip> --vrdeport <port for RDP> &
Edit: Added an '&' to the start command to put the process in the background and returning you to the prompt, which enables you to logout and disconnect your ssh session.
Edited my start command in the previous post.. you just need to add an '&' to the end of the start command to put the VBox process into the background allowing you to disconnect your ssh session.
Thanks! I'll give it a try when I get home. I knew it had to be something simple.
Also, I am running VirtualBox 3.2.12 on the "new" Pro 6 (2nd series) so the E5300 CPU has VT-X capabilities allowing a 64bit OS. I did have to enable acpi, in the VM though to allow it to boot without error. Woohoo!!! My 8GB of RAM in the Pro is put to good use now!
VB 4.0.4 is out and all seems well after updating it in the NAS.
Works great over here aswell... did however have to un-install previous version of the extpack and then install the updated extpack to get rdp working properly again.. and reconfigure /etc/vbox/vbox.cfg to get the VirtualBox web console backend back in business. But other than that it's all good :lol:
You are the guy who made me buy 2x4GB for my pro... As I changed processor to E6600, I use my nas to host some VM. I got them running "as services" with help from scripts from here and there. When you want to start a VM then disconnect your ssh session, & is not enough. It only sends VBoxHeadless to the background, but it stays attached to your ssh session.
Try this instead :
nohup VBoxHeadless --startvm <uuid|name> --vrde on --vrdeaddress <host ip> --vrdeport <port for RDP> &
- Mackila
fbmachines wrote:
jmalmlund wrote:
Edited my start command in the previous post.. you just need to add an '&' to the end of the start command to put the VBox process into the background allowing you to disconnect your ssh session.
Thanks! I'll give it a try when I get home. I knew it had to be something simple. [...]
