So, check if VT-X is enabled in the OS :
apt-get update
apt-get install msr-tools
modprobe msr
rdmsr 0x3A
It should return 5 if the extensions are enabled, and 1 if disabled.
You can also try to update your bios, and check after that vt-x is still enabled.
Are you sure that your OMV install is 64 Bit ?
In a console, run this command : uname -a, there should be x86_64 at the end.
Hi,
Maybe your CPU does not have the VT-x/d instructions set. What model is it ?
Hi,
You shouldn't have done this, these two files in /etc/default MUST NOT be deleted they are created at the very first installation of virtualbox.
As I said, to get them back you have to delete the vbox user and vboxusers group, and remove /tmp/.vbox-vbox-ipc/. Then reinstall virtualbox.
Next time you read a topic, go to the end before doing anything, it will save you time.
It should remove virtualbox 4 if you did not. Did you purge all the virtualbox 4 related packages ?
I don't remember if I had this problem.
For information, I'm running the 3.16 kernel, and my system si up to date (Debian 7.9) : apt-get update; apt-get dist-upgrade
Nice way to help people...
It was already said that this is not recommended to upgrade from testing packages, but for people like me with a windows 10 client, RDP only works with virtualbox 5.
I successfully upgraded with testing packages and everything works (I'm a linux user for more than 10 years now, I know how to do these things...).
Hi,
Try this : apt-get -f install
Sorry I didn't wrote the complete command, I thought you knew how dpkg works.
So, you must write the full file name :
dpkg -i virtualbox-5.0_5.0.2-102096~Debian~wheezy_amd64.deb virtualbox-extpack-installer_5.0.2_all.deb phpvirtualbox_5.0-1_all.deb openmediavault-virtualbox_1.4_all.deb
Which package gave you these warnings ?
Did you purge the pevious packages ?
You should run this :
dpkg --purge php-virtualbox virtualbox-5.0 virtualbox-extpack-installer openmediavault-virtualbox
then reinstall the downloaded packages :
dpkg -i virtualbox-5.0 virtualbox-extpack-installer php-virtualbox openmediavault-virtualbox
Then restart your NAS.
HI,
Did you restart nginx and php services ?
This card has 64 bits LBA, so it has support for 2 TB drives and more. You'll need SFF SAS to SATA cables for your HDDs.
If you're not affraid by used parts (this one is critical in a NAS build), it can be a good option.
I'm not sure of how it will show you the HDDs in the OS, but for software raid it would be easier if it had pass-through mode.
The downside with this type of hardware is that in case of failure, it can be tricky to get your data back, that's why I would go with a basic SATA controller (or even two to have enough ports).
The question would be more like : do you really need a raid card ? Basic 4 ports SATA cards can do the job and they are cheap. With software raid, you do not need to have the drives plugged on the same card.
HI,
An i3 + 8 GB is a nice upgrade, but your PSU doesn't seem to be compatible with the Haswell CPU range.
You can still try and see if your NAS freezes on low power states.
Finally I got the /etc/default/openmediavault-virtualbox file back by deleting the vbox user and vboxusers group, and removing /tmp/.vbox-vbox-ipc/. After purging the openmediavault packages for Virtualbox 4.3, installed 5.0.2 and testing packages.
Now everything is ok.
I ran
touch /etc/default/openmediavault-virtualboxAnd now I can install the packages. But... I cannot access virtualbox frame in webgui : Error logging in to vboxwebsrv.
Maybe this is because of the empty file in /etc/default.
Also : apt-get can not reinstall the deb package from testing2, it's not in the sources. I think you meant dpkg -r then dpkg -i.
I removed everything and these 2 files, then reinstalled and the file /etc/default/openmediavault-virtualbox is missing, so it cannot install openmediavault-virtualbox.
Hi,
Thank you for the upgrade guide, since I updated to Windows 10 I could not connect to Virtualbox RDP (Bug solved with virtualbox 5.0.2).
You just forgot the phpvirtualbox package : http://omv-extras.org/testing2/phpvirtualbox_5.0-1_all.deb
Without it, dpkg refuses to install openmediavault-virtualbox 1.4.
Just upgraded, restarted my NAS, Virtualbox runs fine, but when opening phpvirtualbox I get a 404 error. Any idea ?
Thanks.
Hi,
In the shared folder ACL, just add full access to debian-transmission.
Hi caseyj,
Have you tried to pause the VM you want to backup ?
You can do this with VBoxManage controlvm name_of_your_vm pause, then rsync and resume the vm.
The vdi should not be corrupted, but it' is possible that you get warnings when you restart the VM from a backed up vdi, as the system did not shutdown properly.