Hi there,
I finally got it to work!
But I tried a lot of things, so maybe not all of the steps I've been taking are really nessesary:
After updating my test server to 3.0.25 this morning I reinstalled the virtualbox plugin (still 3.0.4). The installation seemed to go fine except for one warning:
WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-ose-dkms package and the appropriate
headers, most likely linux-headers-amd64.
You will not be able to start VMs until this problem is fixed.
So, I found a solution for that at: http://crunchbang.org/forums/viewtopic.php?id=37999
The hint I've been following was
, so the character device was availlable afterwards.
I did not get the error message (initial post) any more...but I haven't been able to login as none of my admin passwords (incl. admin/admin) would work.
I changed the ownership of the phpVirtualBox folder because I read somewhere that the login problem could be caused by a config.php that is not accessable and I've noticed that it was set up like this on my productive server (OMV 2.2.5):
chown -R www-data:www-data /usr/share/phpvirtualbox
Unfortunately, I still wasn't able to log on to the phpVirtualBox site.
This is when I checked the /usr/share/phpvirtualbox/config.php on my productive server and copied it to the test server.
Result: finally I was able to login with the default login (admin/admin).
Anyway, I still came across another issue:
I've set the network of my new VM to bridge. When I tried to start the VM I got the message that eth0 cannot be accessed and that a
might be helping.
I did that and finally I've been able to start the VM and install a system!!
I'm sorry if my actions seem to be pretty uncoordinated and maybe stupid but I'm a real linux noob. I just wanted to let you know that (at least for now) the VirtualBox plugin in OMV 3.0.25 is working for me.
Maybe my trials will help someone who actually knows what he/she is doing finding a *real* solution.
Thank you!