seba

Virtualbox and phpVirtualbox on XPEnology

Recommended Posts

I'm having problem installing the VirtualBox package, from the Repo, or manually upload the package. It fails to proceed in the "Confirm Settings" step, with the message: "Failed to install VirtualBox." Here is the logs:

2017/04/13 23:38:53     (system) trigger         :
                       Begin:  /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 INFO --no-same-owner
2017/04/13 23:38:53     (system) trigger         :
                       End:    /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 INFO --no-same-owner      ret=[0]
2017/04/13 23:38:53     (system) trigger         :
                       Begin:  /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 conf --no-same-owner
/bin/tar: conf: Not found in archive
/bin/tar: Exiting with failure status due to previous errors
2017/04/13 23:38:53     (system) trigger         :
                       End:    /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 conf --no-same-owner      ret=[2]
2017/04/13 23:38:53     (system) trigger        virtualbox 5.0.36-114008-2:
                       Begin:  /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 scripts/start-stop-status --no-same-owner --no-same-permissions
2017/04/13 23:38:53     (system) trigger        virtualbox 5.0.36-114008-2:
                       End:    /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 scripts/start-stop-status --no-same-owner --no-same-permissions   ret=[0]
2017/04/13 23:38:53     (system) trigger        virtualbox 5.0.36-114008-2:
                       Begin:  /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 scripts/preinst --no-same-owner --no-same-permissions
2017/04/13 23:38:53     (system) trigger        virtualbox 5.0.36-114008-2:
                       End:    /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 scripts/preinst --no-same-owner --no-same-permissions     ret=[0]
2017/04/13 23:38:53     (system) trigger        virtualbox 5.0.36-114008-2:
                       Begin:  /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 scripts/postinst --no-same-owner --no-same-permissions
2017/04/13 23:38:53     (system) trigger        virtualbox 5.0.36-114008-2:
                       End:    /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 scripts/postinst --no-same-owner --no-same-permissions    ret=[0]
2017/04/13 23:38:53     (system) trigger        virtualbox 5.0.36-114008-2:
                       Begin:  /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 scripts/preuninst --no-same-owner --no-same-permissions
2017/04/13 23:38:53     (system) trigger        virtualbox 5.0.36-114008-2:
                       End:    /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 scripts/preuninst --no-same-owner --no-same-permissions   ret=[0]
2017/04/13 23:38:53     (system) trigger        virtualbox 5.0.36-114008-2:
                       Begin:  /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 scripts/postuninst --no-same-owner --no-same-permissions
2017/04/13 23:38:53     (system) trigger        virtualbox 5.0.36-114008-2:
                       End:    /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 scripts/postuninst --no-same-owner --no-same-permissions  ret=[0]
2017/04/13 23:38:53     (system) trigger        virtualbox 5.0.36-114008-2:
                       Begin:  /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 scripts/preupgrade --no-same-owner --no-same-permissions
2017/04/13 23:38:53     (system) trigger        virtualbox 5.0.36-114008-2:
                       End:    /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 scripts/preupgrade --no-same-owner --no-same-permissions  ret=[0]
2017/04/13 23:38:53     (system) trigger        virtualbox 5.0.36-114008-2:
                       Begin:  /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 scripts/postupgrade --no-same-owner --no-same-permissions
2017/04/13 23:38:53     (system) trigger        virtualbox 5.0.36-114008-2:
                       End:    /bin/tar xf /volume2/@tmp/@synopkg/@download/virtualbox/@SYNOPKG_DOWNLOAD_virtualbox -C /volume2/@tmp/58F0525D0 scripts/postupgrade --no-same-owner --no-same-permissions ret=[0]

 

I am running Jun's 1.02a2, DS3617xs, on a Supermicro X10SDV (Xeon D1540) motherboard.

Share this post


Link to post
Share on other sites
Same here. Creator's update does not work wor me also.

 

did you get the same error "/bin/tar: conf: Not found in archive" ?

What's your set up?

Share this post


Link to post
Share on other sites

I can't set it to Legacy because I failed to install it. So, I'm not that far in the process.

Share this post


Link to post
Share on other sites

Quick note, do not allow or manually update to DSM 6.1.1 (DSM_DS3615xs_15101) if you are using VirtualBox 5.0.38-114632-1. The addon fails to load period. Also, if doing a fresh install, make sure to get DSM_DS3615xs_15047.pat to do your install from, not DSM_DS3615xs_15101.pat.

 

Edit: http://spk.diablos-netzwerk.de/ is also down right now, hopefully updating their VirtualBox to be compatible with the newest DSM. I've only started working with this a couple days ago, but it's been a fun and wild ride (I'll post more on that later).

Share this post


Link to post
Share on other sites

I still can't install VirtualBox on my setup. With Jun's 1.02a2 DS3617.

 

Failed during installation:

"/bin/tar: conf: Not found in archive"

Share this post


Link to post
Share on other sites

For those of you that have this working with baremetal setup, can you share your hardware information? I can't seem to get this to work on my set up.

Share this post


Link to post
Share on other sites

I just switched to using the new Synology Virtual Machine Manager that's been in beta for a couple weeks:

https://www.synology.com/en-global/beta ... ualization

 

It's not anywhere near as full featured as phpVirtualBox yet, but it's the usual qemu and libvirt that is common on LInux, and does run my Windows VM just fine. I'll never have to worry about compatibility issues again when upgrading DSM, which is great. I would not recommend trying to migrate a VM from phpVirtualBox, to VMM, it was an absolutely nightmare.

 

There's also some gotchas, you must have 2 or more LAN connections, and you can only put the VMs on BTRFS volumes. No workaround for either that I've seen.

 

The problems I ran into were twofold. One, VMM seems to not support UEFI yet, and I had my vbox vm using UEFI and GPT partitions. Two, and this is the big problem, VMM only supports VirtIO SCSI for the drives, and it's virtually impossible to install these drivers cleanly in a pre-existing VM. If they were using the regular qemu setup, you could migrate over a VM, set the controller to IDE, and boot up fine the first time. Add a 2nd small drive using VirtIO SCSI to get Windows to properly install the drivers, then shutdown, remove the 2nd drive, and change the primary over the VirtIO SCSI. However, this isn't possible with VMM.

 

So here's what I did.

 

First, I copied over the vdi and vbox files from the NAS so I could fix everything up on my local PC, since it's much faster.

 

UEFI to MBR:

I imported into VirtualBox, added a 2nd drive the same size as the primary, and booted up with a GParted live iso. Initialized 2nd drive using MBR, then copied the partition from the GPT to MBR drive using GParted. Shutdown VM, replaced GParted ISO with Win10 ISO, booted back up, ran Command Prompt from Recovery menu ran these commands:

bootrec /scanos

bootrec /rebuildbcd

bootrec /fixmbr

bootrec /fixboot

Rebooted back into recovery again, ran Startup Repair, booted back into Windows without issue after that.

 

Getting VirtIO Drivers installed:

This is annoying, because even though you can right-click install the inf files, Windows won't complete the install until it sees the hardware, and this can't be on first boot. So you somehow need Windows to "see" the VirtIO hardware and install the drivers before you can switch the boot drive. And VirtualBox doesn't support VirtIO SCSI (just VirtIO network), so much more work is needed. Here's my painful steps.

 

QEMU works much better under linux, so I created an Ubuntu VM with VMWare Player (vbox can't do nested virtualization, player can if you enable it), copied my VDI file from vbox to it, and installed the qemu files

sudo apt-get install qemu-kvm libvirt-bin virt-manager (something like that).

Converted the VDI to a format qemu likes

qemu-img convert -p -f vdi vbox.vdi -O qcow2 qemu.qcow2

Created a VM using virt-manager that matched the specs of my VM, added the new qcow2 disk image as an IDE drive.

Fight with VM settings to actually get something to boot.

Booted VM up, confirmed working.

Added a 2nd 1GB drive using VirtIO SCSI, windows saw device, installed drivers from VirtIO iso: https://fedorapeople.org/groups/virt/vi ... io-win.iso

Added a few other drives using the other VirtIO types, since I didn't want to mess with this again.

Powered down VM

Important step, have to remove the VM (leaving the qcow2 image along), then setup a new VM again, this time chosing to add the qcow2 drive as VirtIO. When I just changed the drive from IDE to VirtIO, it wouldn't boot, and googling found I had to remove and reimport. Dumb.

Powered up VM, all good.

Powered down, converted back to a format vbox can use (I used vmdk cause I need to export to OVA anyway)

qemu-img convert -p -f qcow2 qemu.qcow2 -O vmdk vbox-fixed.vmdk

Copy vbox-fixed.vmdk back to PC with vbox, replace old vdi in VM with this new vmdk

Export the vm to an ova file.

 

Uninstall phpVirtualbox, upgrade NAS to 6.1.1 (required for VMM), enable beta software, install VMM, configure VMM, import ova file, cross fingers. Worked for me, though still some weirdness that the VM gets stuck in a boot loop if I reboot it, but is fine if I shutdown/power up. So it looks like things are borked as Windows does the first boot and installed devices and reboots, but just needs a forced power off/back on to be fine.

 

It took me literally days to get it working, and it was totally not worth it. Could have easily just created a new VM and reconfigured it in far lass time, but I was mainly curious to see if it was actually possible.

 

If you're just starting out, and you meet the 2+ LAN and BTRFS requirements, definitely look at VMM. It's getting a bunch of updates to add new features roughly every week, so should be quite nice in a couple months.

Share this post


Link to post
Share on other sites

Thanks for sharing. last time I read about VMM, it was only capable of running the virtualized DSM. Now it can install other OS? I'm sold on it.

  • Like 1

Share this post


Link to post
Share on other sites

Hi,

 

any release of virtualbox for dsm 6.0.2 ?

 

I added diablos source, but only allow for 6.1 :(

Share this post


Link to post
Share on other sites

Why would you bother?
6.1.2 has Virtual Machine Manager (beta) and it supports any VM.

I was able to install, for example, Windows 7 with almost no effort.

The hypervisor is KVM.

Regards,


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites
On 23/06/2017 at 11:24 AM, Mircevski said:

Why would you bother?
6.1.2 has Virtual Machine Manager (beta) and it supports any VM.

I was able to install, for example, Windows 7 with almost no effort.

The hypervisor is KVM.

Regards,


Sent from my iPhone using Tapatalk

 

- can you import/convert a virtualbox vdi ? (with vbox you can select hypervisor kvm)

 

- when i install this package, the problem is i have only one network card, i can add one more card.

 

Is it the only requirement for virtual dsm ?

 

 

 

 

Is there a way to get vbox 5.1.x on xpeenology 6.1 i can't import vbox file from 5.1.22 to 5.0.38 ((same effect on windows or xpenology) ?

 

 

 

 

Share this post


Link to post
Share on other sites
19 minutes ago, ygor said:

 

It seems they will add licence to it after the beta.

 

 

Share this post


Link to post
Share on other sites

Hello guys, please tell me do you have good disk performance on this Virtualbox instalation ? I have I|O disk cache enabled, Legacy VM checked ... i checked it on tho different severs with xpenology ... one with RAID5 8Gb RAM and Xeon , other I3 2120 with 10GB ram ... Performance on Windows 7 64Bit with tools installed is very poor ... May you please help me to check what is going on ?

Share this post


Link to post
Share on other sites

Hi,

 

I installed latest version of phpvirtualbox on dsm6.1.3

 

During install you have some options you can set:

 

  1. You can disable phpVirtualbox authentication, if enabled user/pass is admin/admin

Is there a possibility to enable it again without reinstalling?

 

Thanks!

Share this post


Link to post
Share on other sites

I found the config.php in volume1/web/phpvirtualbox/config.php

Quote

// Disable authentication
var $noAuth = true;

 

Share this post


Link to post
Share on other sites

For DSM 6.1.4

 

I can install vbox from diablos 5.0.40 spk on 6.1.4 and got my vm working, just by replacing the 15152 value with 15217 in *.sh files and renaming kernel folder 15152 to 15217

 

can someone  send me a link to the vbox 5.1.30 spk, it was working much better and faster with win10 guests ... Please tell me someone dl it, as spk.diablos removed it :'(

 

please please please someone have 5.1.30 spk ?

Share this post


Link to post
Share on other sites
1 hour ago, ygor said:

someone have 5.1.30 spk ?

 

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.

Share this post


Link to post
Share on other sites

Changelog: Version: 5.1.30-118389-1. Changes made by DI4bI0 1. Updated VirtualBox to version 5.1.30 r118389.

 

I had it running on 6.1.3, now i updated to dsm 6.1.4, and only 5.0.40 is available in the repo. I had to reinstall vbox after update :(

 

Now running with 5.0.40 is OK but not performing as good.

Edited by ygor

Share this post


Link to post
Share on other sites

here it is:

 

http://webcache.googleusercontent.com/search?q=cache:PRLky4kQMAgJ:spk.diablos-netzwerk.de/---%3Fchannel%3Dall%26arch%3Devansport%26package%3Dvirtualbox+&cd=2&hl=fr&ct=clnk&gl=be

 

 

Release: Stable

Beschreibung:

VirtualBox ist ein mächtiges x86 und AMD64/Intel64 Virtualisierungs-Programm für Unternehmen als auch für Heimanwender. Als Frontend wird phpVirtualBox benutzt, wenn die Authentifizierung für phpvirtualbox benutzt wird, ist der standart Login admin/admin.

Package:virtualbox

Version:5.1.30-118389-1

Minimum DSM verison:6.1-15152

Maintainer:seba/dodo-dk/DI4bI0

Distributor:Diablos-Netzwerk

Arch:x86 cedarview bromolow evansport avoton braswell grantley broadwell apollolake

size:5.29 MB

md5:545e04245a68cdb5b957d3b793332900

sha1:6ad8ecd3eba2ca9c0d175c3471fcb94325069596

Signed:Yes

Downloads:42595

 

Changelog:

Version: 5.1.30-118389-1
Changes made by DI4bI0
1. Updated VirtualBox to version 5.1.30 r118389
2. Updated Kernel Modules (3.10.102) DSM 6.1-15152 to version 5.1.30 r118389
2.1 x86_64 (pineview) version 5.1.30 r118389
2.2 cedarview version 5.1.30 r118389
2.3 bromolow version 5.1.30 r118389
2.4 avoton version 5.1.30 r118389
2.5 braswell version 5.1.30 r118389
2.6 grantley version 5.1.30 r118389
2.7 broadwell version 5.1.30 r118389
3. Updated Kernel Modules (3.2.40) DSM 6.1-15152 to version 5.1.30 r118389
3.1 evansport version 5.1.30 r118389
4. Added Kernel Modules (4.4.15) DSM 6.1-15152 version 5.1.30 r118389
4.1 apollolake version 5.1.30 r118389
5. Some other small changes

 

Versions History:

 

 

 

 

 

Edited by ygor

Share this post


Link to post
Share on other sites

Working :

 

DSM 6.1.4-15217 and the package from google cache : 5.1.30

 

download the package

edit 2 files in scripts folder:

installer.sh

vboxdrv.sh

replace: REQUIRED_KERNEL_BUILD="15152" with REQUIRED_KERNEL_BUILD="15217"

 

open path : VirtualBox_x64_5.1.30-118389-1.spk\package.tgz\package.tar\kernel_module\

rename folder: 15152 with 15217

 

all done with 7zip to open spk and edit the files & save, windows 10 guest and linux guests up and running in vbox in DSM 6.1.4 

 

much better performance for windows10 guest in my case on HP N54L

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now