Virtualbox and phpVirtualbox on XPEnology


Recommended Posts

Here the newest VirtualBox 4.3.26 Version.

I have added a Symlink so the Guest Additions is easy to install from phpvirtualbox:

phpvirtualbox -> click on your VM Machine -> Settings -> Install Guest Additions...

 

For Xpenology: https://mega.co.nz/#!1IJVib7L!879FmBXPN ... MWWT49ZNmw

 

For Real Synology: https://mega.co.nz/#!UchiAbxa!QBPIQWWv2 ... J-HNbU6uBc

 

Use at your own risk.

 

Please Stop all Virtual Machines and the VirtualBox before you deinstall the old VirtualBox.

If there are some Problems with phpvirtualbox please try to clear the Browsercache.

 

Dodo

 

Hello,

Can you make a package for version 5.2 DSM synology ??

There is a new kernel 3.10.35

 

Currently, the DS710 + worked great: D

 

Thank you.

Link to post
Share on other sites
Hi polly76,

 

there is for the Xpenology Version (bromolow) compiled.

I have another Version (x86), this works on Real Synology.

 

@all

 

Here the newest VirtualBox 4.3.24 Version.

 

For Xpenology: https://mega.co.nz/#!IcQyzb4J!rXf7azt1n ... mfbbi5VHyU

 

For Real Synology: https://mega.co.nz/#!dRwgWRAI!IAOjE7OJn ... pnlNOLK2cg

 

Use at your own risk.

 

Please Stop all Virtual Machines and the VirtualBox before you deinstall the old VirtualBox.

If there are some Problems with phpvirtualbox please try to clear the Browsercache.

 

Dodo

 

Btw, thank you Seba.

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.

Link to post
Share on other sites
Hi polly76,

 

there is for the Xpenology Version (bromolow) compiled.

I have another Version (x86), this works on Real Synology.

 

@all

 

Here the newest VirtualBox 4.3.24 Version.

 

For Xpenology: https://mega.co.nz/#!IcQyzb4J!rXf7azt1n ... mfbbi5VHyU

 

For Real Synology: https://mega.co.nz/#!dRwgWRAI!IAOjE7OJn ... pnlNOLK2cg

 

Use at your own risk.

 

Please Stop all Virtual Machines and the VirtualBox before you deinstall the old VirtualBox.

If there are some Problems with phpvirtualbox please try to clear the Browsercache.

 

Dodo

 

Btw, thank you Seba.

 

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.

Edited by Guest
Link to post
Share on other sites

Hi dMajo,

 

i don´t have problems with the index.html

The rights are:

-rw-r--r--    1 root     root         19895 Feb 28 01:28 index.html

and it works.

 

I think you need to stop all VM Machines and VirtualBox and then you make a update.

I don´t test it with Update. Only De/Reinstall.

 

Should i change my Packages with your changes?

 

Thanks

Link to post
Share on other sites
Hi dMajo,

 

i don´t have problems with the index.html

The rights are:

-rw-r--r--    1 root     root         19895 Feb 28 01:28 index.html

and it works.

 

I think you need to stop all VM Machines and VirtualBox and then you make a update.

I don´t test it with Update. Only De/Reinstall.

 

Should i change my Packages with your changes?

 

Thanks

 

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

Link to post
Share on other sites
Hi dMajo,

 

i don´t have problems with the index.html

The rights are:

-rw-r--r--    1 root     root         19895 Feb 28 01:28 index.html

and it works.

 

I think you need to stop all VM Machines and VirtualBox and then you make a update.

I don´t test it with Update. Only De/Reinstall.

 

Should i change my Packages with your changes?

 

Thanks

 

I still stuck in "127.0.0.1:18083" issue, I have following "http://sourceforge.net/p/phpvirtualbox/wiki/vboxweb-service%20Configuration%20in%20Linux/" and try to start vboxweb-service, however, I can't find such "init.d" directory.

Link to post
Share on other sites
If you need to troubleshoot vbox from ssh try this do start drivers:

/var/packages/virtualbox/target/scripts/vboxdrv.sh start

if this goes without error then:

/var/packages/virtualbox/target/scripts/vboxinit.sh start

and finally if vboxinit was without errors:

/var/packages/virtualbox/target/scripts/vboxweb-service.sh start

 

Try this and post the result.

Link to post
Share on other sites
If you need to troubleshoot vbox from ssh try this do start drivers:

/var/packages/virtualbox/target/scripts/vboxdrv.sh start

if this goes without error then:

/var/packages/virtualbox/target/scripts/vboxinit.sh start

and finally if vboxinit was without errors:

/var/packages/virtualbox/target/scripts/vboxweb-service.sh start

 

Try this and post the result.

 

I'm using DS-214Play with DSM5.1-5022 Update 4.

 

DiskStation> /var/packages/virtualbox/target/scripts/vboxdrv.sh start

Starting VirtualBox kernel modules ...fail!

DiskStation> /var/packages/virtualbox/target/scripts/vboxinit.sh start

su: must be suid to work properly

DiskStation> /var/packages/virtualbox/target/scripts/vboxweb-service.sh start

Starting VirtualBox web service ...fail!

DiskStation>

Link to post
Share on other sites
Under /var/log/ you have logs from vbox, can you post the content?

 

I can't find any logs from vbox under /var/log/ :sad:

 

cloudsync dpkg_upgrade.log nginx surveillance.log

cstn gcpd.log partition synodtv.log

ddclient.log httpd php-fpm.log synoinfo.conf.bad

disk_log.xml kern.log postgresql.log synolog

disk_overview.xml log.nmbd samba synopkg.log

dmesg log.smbd scemd.log synoservice.log

dmesg.1.xz lvm_lv_create_log selfcheck synoupdate.log

dms.log messages smart_quick_log syslog.log

dpkg.log mount.log ssupgradeerr.log upstart

Link to post
Share on other sites

/var/log should have

 

vbox.log for the current boot and vbox.log.N for the previous 10 boots.

This file contains detail information.

vboxscripts.log (just one)

This file just contains the start and stop of the guest VMs.

 

see viewtopic.php?f=15&t=5350#p32723

 

have a look at /var/packages/virtualbox/target/etc/vbox/vbox.cfg, mine contains

 

VBOXWEB_LOGFILE=/var/log/vbox.log

 

Andrew

Link to post
Share on other sites
/var/log should have

 

vbox.log for the current boot and vbox.log.N for the previous 10 boots.

This file contains detail information.

vboxscripts.log (just one)

This file just contains the start and stop of the guest VMs.

 

see viewtopic.php?f=15&t=5350#p32723

 

have a look at /var/packages/virtualbox/target/etc/vbox/vbox.cfg, mine contains

 

VBOXWEB_LOGFILE=/var/log/vbox.log

 

Andrew

 

I have checked the configuration in vbox.cfg, it shows the log should be in /var/log/vbox.log, however, I still can't find the vbox.log in /var/log/

 

DiskStationmore /var/packages/virtualbox/target/etc/vbox/vbox.cfg

# VirtualBox installation directory

INSTALL_DIR='/opt/VirtualBox'

# VirtualBox version

INSTALL_VER='4.3.26'

INSTALL_REV='98988'

# Build type and user name for logging purposes

BUILD_TYPE='release'

VBOXWEB_HOST='127.0.0.1'

VBOXWEB_USER='root'

VBOXWEB_LOGFILE=/var/log/vbox.log

VBOXWEB_AUTH_LIBRARY=null

SHUTDOWN_USERS=root

SHUTDOWN=acpibutton

Link to post
Share on other sites
  • 3 weeks later...

Hi everybody,

 

I just wanted to start by saying thanks to the devs for creating/maintaining this spk. It rocks. Got a Win8.1 system up and running with ease.

 

However, I do have a few quick questions: 1) Will I be able to rip my DVD/BluRay collection? I know Xpenology doesn't recognize my LG Blu Ray drive, but would my Windows install running within VB?

2) I'm having trouble accessing a shared folder. Haha...hard to get the ripped movie off the vHDD without a shared folder. Is there a trick to it? Or am I just a doofus?

 

Anyways, thanks again for the solid work. Keep on keepin' on.

 

TB

Link to post
Share on other sites
  • 1 month later...

I'm using DS-1515+ with DSM 5.2-5565.

 

and got same issue with @ttc (I still stuck in "127.0.0.1:18083")

 

and try start service with ssh

 

same result with @ttc

 

no logs

 

before i update to 5.2-5565 my vitrualbox is work great

i think may synology change somtehing in DSM

Link to post
Share on other sites
I'm using DS-1515+ with DSM 5.2-5565.

 

and got same issue with @ttc (I still stuck in "127.0.0.1:18083")

 

and try start service with ssh

 

same result with @ttc

 

no logs

 

before i update to 5.2-5565 my vitrualbox is work great

i think may synology change somtehing in DSM

 

i've got 2 baremetal systems running 5.1 U5, bot systems have an 128GB SSD as Volume1 where i install all apps

i could narrow down the issue to the system using SHR for volume1 to have the issue

2nd system where i made the Volume1 as a raid (non SHR) works flawless...

so you should check this too

Link to post
Share on other sites

Hi,

 

here a new Update. Only one Version, supports Synology and Xpenology / DSM 5.1 and 5.2.

 

CHANGELOG:

 

Version: 4.3.28-100309-1

Changes made by dodo-dk

Update VirtualBox and Kernels to version 4.3.28 r100309 for DSM 5.1/5.2 bromolow/x86_64

 

Version: 4.3.26-98988-3

Changes made by DI4bI0

1. Added support for the new Kernel 3.10.35

2. This Version includes Kernel 3.2.40 for x86_64 and bromolow

3. This Version includes Kernel 3.10.35 for x86_64 and bromolow

4. fixed the Networkbridge error on bromolow

5. Added the ability to chose the Keyboard layout

6. Added the ability to chose the UI languge

7. Fixed a problem that would prevent VirtualBox to shut down

8. Improved error reporting

9. Changed the way how to handle missing symlinks

 

Use at your own risk

Download: https://mega.nz/#!ZFInHRSb!2hcB4V0ztc2o ... 91IFvFhM3M

 

Dodo

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.