dMajo

Members
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dMajo

  • Rank
    Newbie
  1. There was no 5.1.30 since this will be newer (later) than 5.0.40. For previous versions click on expand under history under the latest version description.
  2. I think you need to download the guest additions from the VB official site. Perhaps sources and you will need to build them. For linux system on which DSM is based over. This thread discusses the VB installation under DSM not the opposite. You can try other xpenology forums where the argument is running xpenology in a VM. Perhaps there they have already compiled guest additions.
  3. You can install VB from here Once finshed you will find the right guest additions iso in the vb folder in @appstore
  4. It works on mine DS1815+ and RS2414RP+ but I can confirm also DS1515+ DS415+ which is obvious being all on the same architecture.
  5. If you are using win client you can use the in-built remote desktop connection client with: ip.of.the.nas:9000 Look for the port range in the vm settings. Be sure that on the nas firewall these ports are open at least for the local lan.
  6. I think that DTech meant that he updated the package without uninstalling the previous version. Since version 5.0.4 this is working, Dodo-dk has done a great job, tha package gets updated and preserves all the settings and VMs. Regarding the auto update I think you do not want the package center update automatically virtualbox shutting down the running VMs in an uncontrolled fashion.
  7. In the application installation folder volume/@appstore/virtualbox there is a iso for the guest additions
  8. In the package center settings you need to allow installation from untrusted sources, ie any publisher.
  9. Regarding the index.html I don't know. At first I updated the previous version through the package center update function. Then after the gui was not working I added the execution rights (744) to the index file. There wasn't any VM in execution during the upgrade, but the vb service was started. After the change anything worked fine. I suspected that maybe you have not handled/foreseen the upgrade process so later I uninstalled the package, checked if there was any pending folder that needs manual deletion and re-installed the latest package. Again I needed to apply the change to the index file. Except for that everything worked fine. The lan in bridge mode works greatly also over the bonded underlying nics. The only thing that I noted after the second "fersh" install was that I didn't need to import the VMs nor to configure the preference settings. I don't know from where these was restored because as I told you I checked with webmin through the file system for any pending file that perhaps was not deleted by the uninstall process, but I didn't find anything. Perhaps you can automate in the preupgrade script the stopping of any involved service, you can copy to a tmp folder the config settings to restore them later in the postupgrade. I think this can be enough to support updates properly. Here below are the changes I've made, every other thing in the package remained untouched except for the info file and the package's name itself. Otherwise the DSM on syno bromolow units would had troubles in choosing the package from the repo because two would have the same name, architecture and version thus only one would have been showed and you don't know which one. virtualbox-x64-4.3.24_DSM-5.1_x86.spk displayname="VirtualBox Syno Edition" package="virtualbox" version="4.3.24-98716" beta=true description="VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. For front-end phpVirtualBox is used, if authentication is used default user/pass is admin/admin. This release is for Synology" arch="x86 cedarview avoton bromolow evansport" firmware="5.1-5022" maintainer="seba/dodo-dk" distributor="Synology Italia Forum" distributor_url="http://spk.synologyitalia.com" report_url="http://forum.synology.com" install_dep_services="apache-web" start_dep_services="apache-web" instuninst_restart_services="apache-web" reloadui="yes" dsmuidir="app" adminurl="/phpvirtualbox/" changelog="New VirtualBox and phpvirtualbox for Synology" virtualbox-x64-4.3.24_DSM-5.1_xpe.spk displayname="VirtualBox XPE Edition" package="virtualbox-xpe" version="4.3.24-98716" beta=true description="VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. For front-end phpVirtualBox is used, if authentication is used default user/pass is admin/admin. This release is for XPEnology, do not install it on Synology units" arch="bromolow" firmware="5.1-5022" maintainer="seba/dodo-dk" distributor="Synology Italia Forum" distributor_url="http://spk.synologyitalia.com" report_url="http://forum.synology.com" install_dep_services="apache-web" start_dep_services="apache-web" instuninst_restart_services="apache-web" reloadui="yes" dsmuidir="app" adminurl="/phpvirtualbox/" changelog="New VirtualBox and phpvirtualbox for XPEnology" Regards and again congratulations for your wonderful work
  10. Dodo, I've added your packages to our repository. Since the info in the packages are pretty the same I had to modify the xpenology build: I've renamed the package's internal name from "package=virtualbox" to "package=virtualbox-xpe" I've added to the description (of both): "Release made for Synology"/"Release made for XPEnology" I've changed the displayname to "VirtualBox Syno Edition"/"VirtualBox XPE Edition" I've added the beta information: packages that are actually in beta and/or require higher user's skills are published under the beta channel thus you need to enable it in the package center and choose "Show beta packages" to see them on the repository's website This was needed to show both the packages on syno and xpenology units that identifies itself to the repo with the same architecture but actually needs different binaries. From the description the user can choose which one to install and thus further updates (when version number increases) can't cross-update the wrong release. Keep on the good work !!! BTW: in both cases, when upgrading from 4.3.12 to 4.3.24 and later with a fresh new install of 4.3.24, the php didn't start until I chmod the index.html and given it the execution rights. Perhaps you should check it in the postinstall/postupgrade scripts.
  11. Dodo, I've added your packages to our repository. Since the info in the packages are pretty the same I had to modify the xpenology build: I've renamed the package's internal name from "package=virtualbox" to "package=virtualbox-xpe" I've added to the description (of both): "Release made for Synology"/"Release made for XPEnology" I've changed the displayname to "VirtualBox Syno Edition"/"VirtualBox XPE Edition" This was needed to show both the packages on syno and xpenology units that identifies itself to the repo with the same architecture but actually needs different binaries. From the description the user can choose which one to install and thus further updates (when version number increases) can't cross-update the wrong release. Keep on the good work !!! BTW: in both cases, when upgrading from 4.3.12 to 4.3.24 and later with a fresh new install of 4.3.24, the php didn't start until I chmod the index.html and given it the execution rights. Perhaps you should check it in the postinstall/postupgrade scripts.