Because actual Pluging only install virtualBox 4.x that have problems to connect to Win10 using RDP, and VirtualBox 5.0.2 works fine.
My suggest is to create a new Virtualbox 5.0 Pluging to avoid problems described here: Some help please - virtualbox won't update to latest version
I actually install 4.3 pluging, and once stoped execute vb5.shell script that suggest subzero, but a new plugging is easyer for beginers.
A new plugin doesn't really help. You still need to purge 4.3 before installing 5.0 and you can't do that with the plugin. My plan was to save virtualbox 5 for OMV 3. If someone wants/needs virtualbox 5 before that, they can manually run the script. I will update the packages that are in that script and update the script itself.
My point is for new install, not for upgrades.
eg: I have previosly VB4.3 instaled but do not work RDP, my plan is to uninstall VB4.3 pluging and do a new fresh install of 5.03, and only need to configure folder of my VM chown vbox:vbox myfolder.
Other users can see 2 plugings in omv-extras and normaly opted to install latest (5.03) so I do not see problem excep in the case that try to update from 4.x to 5.x , but is esay to check it and abort install no?.
Then we have to maintain two plugins and uninstalling the plugin from the web interface does not purge everything. So, we would still have people reporting problems installing 5.x. In my opinion, there isn't much reason to upgrade to 5.x unless you have to have usb3. If someone needs it that bad, it isn't hard to install using the script.
The existing plugin seems to work fine after upgrading with the script. You don't need to uninstall the virtualbox plugin when you run the script to install the new version of virtualbox.
Yep, the plugin doesn't need to be changed to work with 5.x. The reason you don't have to uninstall the plugin when using the script is because the script purges virtualbox-4.3, the plugin, the vbox user, and a couple of config files.
I too have problems to connect to my virtual boxes with my win10 laptop. According to this https://www.virtualbox.org/ticket/14216 we need at least 4.3.31 to solve this issue. I still have 4.3.28. Did I miss an update of the virtual box plugin?
No, I didn't update the 4.3 version. I recommend updating to 5.0.10 using the script a few posts above.
mmmh. Seemed to me that there is some risk to brick my working NAS. Wanted to wait until OMV3 is coming with VB5.
mmmh. Seemed to me that there is some risk to brick my working NAS. Wanted to wait until OMV3 is coming with VB5.
I disagree. When using the script, every upgrade I have seen (and tested myself) has worked fine. Probably just as much risk updating to 4.3.31. When OMV 3 is ready (long way off), updating to OMV3 will be a much bigger risk since it involves updating to Debian Jessie. You can always manually update to 4.3.31 or 4.3.34 which is the latest. The plugin doesn't need any changes to work with it.
I disagree. When using the script, every upgrade I have seen (and tested myself) has worked fine. Probably just as much risk updating to 4.3.31.
O.K., you mean the script "vb5_install.zip", mentioned by raulfg3?
THNX for the hint.
Crossed my fingers and did run the script. There was one error: "addgroup: The group `vboxusers' already exists as a system group. Exiting."
- After a reboot and setting the location of the virtual machines I wanted to start a vbox session. But: there are no virtual machines in the list?
O.K. the userid of the newly created vbox user did not match the id of the old vbox user. Did a chown -R vbox of the whole sub-directory. But the virtual machines are still not found?
- after first time login on phpVirtualBox with admin/admin the clock-dialog did appear. This dialog does not went away even after reboot
Any idea what went wrong?
The vboxusers group message is not error just a message that it did not have to create the group.
Just add the VMs back from phpvirtualbox. It should find the .vbox file and add everything back like it was.
Clock dialog? You probably need to clear your browser cache since phpvirtualbox was updated.
I think the only thing I had to do was redo my password.
The vboxusers group message is not error just a message that it did not have to create the group.
Just add the VMs back from phpvirtualbox. It should find the .vbox file and add everything back like it was.
Clock dialog? You probably need to clear your browser cache since phpvirtualbox was updated.
Back from weekend and it is still not working...
With "Clock dialog" I meant the hourglass symbol. To be precise: it is "Loading...." showing a circular ring (see attachment #1)
When I hit the ctrl+f5 (for browser refresh) there is a message shown for a short time (see attachment #2) which is overwritten by the circular "Loading...." dialog.
Try clearing your browser cache and the restart your browser.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
