NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Help and questions on Virtualbox install for 6.6.0
Looking to install Virtualbox 6.6.0 and this is going to seem like a dumb questions, sorry, new and learning. Once it is installed, how do you it up? is it all done via command line? is there a gui...
Thank you all! it works. This is the commands I used, with
VBoxHeadless --startvm <uuid|name> --vrde on
to run the script.
unzip ReadyNASOS_V6.6.0_WW_src.zip
cp -rp linux-4.1.30-x86_64 /data/.apps
ln -s /data/.apps/linux-4.1.30-x86_64 /usr/src/linux-4.1.30-x86_64apt-get update
apt-get install build-essential
apt-get install vim git lm-sensors telnet
apt-get install bc
apt-get install libqt4-opengl libvpx1
apt-get install -f
export KERN_DIR=/usr/src/linux-4.30-x86_64
cd /usr/src/linux-4.1.30-x86_64
cp /data/VirtualBox/tmp/linux-4.1.30-x86_64/arch/x86/configs/defconfig.x86 /usr/src/linux-4.1.30-x86_64/.config
# ** Check kernel install options and modules
make ARCH=x86_64 oldconfig && make ARCH=x86_64
## Installation of VirtualBox
cd /data/VirtualBox/
dpkg -i virtualbox-4.3_4.3.20-96996~Debian~wheezy_amd64.deb
apt-get -f install
/etc/init.d/vboxdrv setup
modprobe vboxdrvcd
## Upgrade VirtualBox Extension Pack
VBoxManage extpack uninstall "Oracle VM VirtualBox Extension Pack"
VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.3.20-96996.vbox-extpack
Have you tried :
apt-get install bc
I think it was also missing from the other instructions.
Thank you all! it works. This is the commands I used, with
VBoxHeadless --startvm <uuid|name> --vrde on
to run the script.
unzip ReadyNASOS_V6.6.0_WW_src.zip
cp -rp linux-4.1.30-x86_64 /data/.apps
ln -s /data/.apps/linux-4.1.30-x86_64 /usr/src/linux-4.1.30-x86_64
apt-get update
apt-get install build-essential
apt-get install vim git lm-sensors telnet
apt-get install bc
apt-get install libqt4-opengl libvpx1
apt-get install -f
export KERN_DIR=/usr/src/linux-4.30-x86_64
cd /usr/src/linux-4.1.30-x86_64
cp /data/VirtualBox/tmp/linux-4.1.30-x86_64/arch/x86/configs/defconfig.x86 /usr/src/linux-4.1.30-x86_64/.config
# ** Check kernel install options and modules
make ARCH=x86_64 oldconfig && make ARCH=x86_64
## Installation of VirtualBox
cd /data/VirtualBox/
dpkg -i virtualbox-4.3_4.3.20-96996~Debian~wheezy_amd64.deb
apt-get -f install
/etc/init.d/vboxdrv setup
modprobe vboxdrv
cd
## Upgrade VirtualBox Extension Pack
VBoxManage extpack uninstall "Oracle VM VirtualBox Extension Pack"
VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.3.20-96996.vbox-extpack
i spoke to soon! it was fine for about a day and one of my interfaces stopped working. So I used the other interface, shut down the VM gracefully. Then i rebooted the NAS gracefully.
then it came back and said:
ot@ReadyNAS:~/VirtualBox VMs/Windows10_64/Logs# vboxheadless
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (4.1.30.x86_64.1) or it failed to
load. Please recompile the kernel module and install it bysudo /sbin/vboxconfig
You will not be able to start VMs until this problem is fixed.
VBoxHeadless: Error -1908 in suplibOsInit!
VBoxHeadless: Kernel driver not installedVBoxHeadless: Tip! Make sure the kernel module is loaded. It may also help to reinstall VirtualBox.
What on earth happened? Oh yeah, the interface did come back on reboot.....
A couple of things noted there, did you switch back to the older version of Virtualbox ? And did you run
make menuconfig
andcd /usr/src/linux-4.1.30-x86_64
make modules_install ARCH=x86_64
The modules_install I think is the bit you are missing. If you compare what you did versus the previous instructions you'll see what the difference is.
i did not change versions. however i could not get menuconfig to work, so i did skip that step--to my detriment i see.
i am not familiar with make modules_install...
thanks
so i retraced my steps and used the make module command--Virtualbox seems to be very stable and survives a reboot.
However my main problem now is that the network connection on the readynas and in the VM seems to die after a few hours and only cure is a reboot. I am using the vm exclusively to send my readynas backups to amazon via an app called Goodsync on a Win10 VM--thus very heavy and consistent network usage. (granted it is only a 1mb/sec uplink, so i know i have another 7 mb/sec capability, so it is not link saturation) Strangely, the transfer continues on, but no other app in the VM, nor outside the VM can use the connection.
any thoughts on what network config change i need to make? i am using everything default, thus NAT.
should i looked at bridged networking as an option?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
