jarugut

Do you have enough space to create a new DSM for a test purpose? I'm not sure but I think that if you extend directly de virtual disk later from the Storage DSM you can extend the basic disk and the volum. But to be sure you can create a new dsm in the ESX with a small disk like 10 GB create the disk and volum and later extend the disk to 20 GB from the ESX, with this test you are going to be sure what is the correct procedure and if the DSM allows you.

what versión of dsm are you using? check this foro... if the versión 5.1.30 not works try with the 5.0.40, I´ve left upload different versions of package.

DSM guarda en el mismo disco el sistema operativo en una partición propia de 2 GB y el resto del disco son datos. No debes preocuparte por los datos en caso que una actualización falle, eso nunca se pierde, en el foro verás que es posible reinstalar sin perder ningún dato.

The vitualbox spk is in the following link https://github.com/seba76/virtualbox4dsm/releases and the phpvirtualbox to manage the native virtualbox service is in the following link https://github.com/seba76/phpvirtualbox4dsm/releases when you install the both package you must to define the same password to be able to comunicate the phpvirtualbox with the virtualbox itseft.

Thank you a lot Seba, it's working fine the both package!

Hi Kingsokar, I attach you the virtualbox that works with version DSM 6.1.7, I have running this virtualbox on my N54L Gen7 server without problems. Note: Not upgrade to DSM 6.2 , if you upgrade your xpenology then it will not works anymore, the kernel is different. VirtualBox_x64_5.0.40-115130-1_6.1.7.spk

you only swap the USB boot drive to the new machine, it's not necessary to create a new one. And leave the hard drives in the same position than the older machine.

That is the problem! I was investigating but only exist for version 6.1 with kernel 3.10.102 not for 3.10.105. Maybe Jun could help to us in that topic. The important think is that the people must to have in mind if they would like to keep the PHPvirtualbox running then, keep in 6.1.7 version, Synology is going to continue giving us support.

This is the problem It's compilet for kernel 3.10.102 and the 6.2 version use the 3.10.105. I don't know if somebody could recompile the kernel modules that are in the following path of the package.tgz compress file. \package.tgz\package.tar\kernel_module\23739\bromolow\3.10.105\ package.tgz In the src.zip file there are the source of the modules to use to compile. src.zip

I've tested the package in a new 6.2 xpenology over ESX without sucess. The problem is that the internal services are not running, it's seems like the libraries are not compilet to 3.10.105, only for 3.10.102. That means that we can't use this package if we upgrade from 6.1 to 6.2 until somebody create a new package for it. 😞

I've modified the installer file from requiere kernel 3.10.102 by 3.10.105. maybe it will works! VirtualBox_x64_5.0.40-115130-1_6.2 only kernel 3.10.105.spk

I've modified the previous packages for the 6.2 version only for the kernel 3.10 the Jun 1.03b loader version for 3615/3617. I've not tested yet, I hope works well. VirtualBox_x64_5.0.40-115130-1_6.2 only kernel 3.10.spk

If you have a N54L forget it, it's not works. For the N54L you must to use the PHPvirtualbox. https://xpenology.com/forum/applications/core/interface/file/attachment.php?id=3042

Hello Boltinvader, In the forum there are everything, use the search please

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 - Loader version and model: Jun's loader v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP N54L (AMD) - Additional comments: REBOOT REQUIRED

Hello, First of all, look the forum before update you xpenology. Second, search and read de forum too.

Add in the grub.cfg file the disable_mtrr_trim option.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.6-15266 Update 1 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver G8 - Additional comments: REBOOT REQUIRED, PHPVirtualbox package reinstalled with the following update. VirtualBox_x64_5.0.40-115130-1_6.1.7.spk

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.6-15266 Update 1 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver Gen7 N54L - Additional comments: REBOOT REQUIRED, PHPVirtualbox package reinstalled with the following update. VirtualBox_x64_5.0.40-115130-1_6.1.7.spk

VirtualBox 5.0.40 package updated for the 6.1.7 version. Enjoy! VirtualBox_x64_5.0.40-115130-1_6.1.7.spk

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5 update 1 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Microserver Gen8 - Additional comments: REBOOT REQUIRED, PHPVirtualBox reinstalled with the previous package modified

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5 update 1 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Microserver N54L G7 - Additional comments: REBOOT REQUIRED, PHPVirtualBox reinstalled with the previous package modified. See here

New package full modified for the new version 6.1.6 with kernel build 15266 VirtualBox_x64_5.0.40-115130-1_6.1.6.spk Enjoy!

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (HPE Microserver Gen8, N54L) - Additional comments: No reboot required

Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 5 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (HP Proliant MicroServer gen8) - Additional comments: Requires reboot, Phpvirtualbox working again with the following package VirtualBox_x64_5.0.40-115130-1_6.1.5.spk and Power Button package reinstalled and working.