Balrog

I think it works as the partitioning of the harddisks are not changed. For a test I pulled all harddisks out of my production machine (bare metal) into the test machine (virtual under esxi) and all data were still intact.

It works very well! Now the log is shown. Thanks again for posting the fix!

Thank you very much for the infos. I will be looking tomorrow at my phpvirtualbox installation and fix this too.

One important hint: Change immediatly after the installation the "Default Machine Folder" away from "/root/VirtualBox VMs" to an accessible shared folder with enough free space (e.g. "/volume1/VirtualBox_VMs"). In my case the first boot volume runs out of space as the Test-VM under /root/VirtualBox VMs/... uses all available diskspace. The DSM-Partition is only 2.3 GByte big with around 1.7 GByte free space so its not that difficult to eat up all free space. I must boot with a Linux-Live CD, move the VM-files away from "/root/VirtualBox VMs" (I moved them to a network share) and have to repair a few other important files that get corrupt due to low disk space (e.g. /etc/rc.local has no rights anymore (000) and I have to set it back to 755).

You have to install/enable ipkg https://xpenology.com/forum/topic/1342-install-ipkg-on-dsm-50 and then install the package "cpufrequtils": ipkg install cpufrequtils

Thank you very much for the new version! The update runs straight as you have described. This time I don't even have to clear the browser cache. I installed a Debian 8 (Jessie) as Test and it works like a charm. Here is how I installed the guest additions: #connect to vm via ssh and logon as root #install required packages apt-get install dkms build-essential linux-headers-$(uname -r) #in phpVirtualBox click on the vm on "settings" - "Install Guest Additions" #the first time this gives an error that the automatic update don't work and you have to install the guest additions manually #mount the iso in the vm mount /dev/cdrom /mnt/ #install Guest-Tools bash /mnt/VBoxLinuxAdditions.run #unmount iso umount /mnt Cheers Balrog

Thank you very much for the two versions!! First I tried a version for "Real Synology" on a XPEnology-System and ran into problems with the network (no DHCP and buggy connections (only 2 from 4 pings come back)). With the version for XPEnology network connections in VMs are working very well.

I don't know why you have such problems. I'm running Xpenology very well on my HP Gen8 baremetal with the actual boot-image "XPEnoboot 5.1-5022.3" and the corresponding "DSM 5.1-5022 Update 3". I installed it like in this manual http://www.xpenology.nl/installation-dsm-5-1/

I have the answer for the HP Microserver Gen8! The trick is to set the power setting in the Bios to "OS controlled" (and don't forget to save this setting as "User-default". Otherwise it will be resetted at the next reboot caused by the "bios reset bug") After the next boot all power-settings are accessible without loading any additional modules. Thanks for the script to set the conservative governor at boot. It works very well!

Which module I must load for an Intel-Cpu? I have a HP Microserver Gen 8 with a Celeron G1610 CPU and get the error "no or unknown cpufreq driver is active on this CPU" if I run "cpufreq-info". I am also not able to set the cpu governor as the entries under /sys/devices.... don't exists (this makes sense as the driver is not loaded). Maybe someone can point me to the correct module to load.

Thank you very much for the new vmtools!! I just updated coming from "open-vm-tools-bromolow-9.4.0-1280544-50.spk" to your new version "5.1_9.4.6-1770165-3" (of course with first deinstall the old tools and afterwards install the new tools). The vm is already on the newest XPEnoboot 5.1-5022.2 with the latest Update "DSM 5.1-5022 Update 2". It works out of the box without a reboot of the vm. Now the IP-Address and DNS-Name from the vm is shown correctly in the vsphere client and as OS there is now "Linux 3.2.40 XPenology DSM". Restarting and Poweroff from the vsphere client works like a charm. Very good work! *thumbs up*

If you have installed Xpenology on esxi 5.5 you must first make sure that the usb ports are enabled in the Bios. For support for usb 3 you can have a look here: http://www.v-front.de/2014/11/vmware-silently-adds-native-usb-30.html I have tried it with a Windows 2012-vm and it works fine.

If you have installed Xpenology on esxi 5.5 you must first make sure that the usb ports are enabled in the Bios. For support for usb 3 you can have a look here: http://www.v-front.de/2014/11/vmware-silently-adds-native-usb-30.html I have tried it with a Windows 2012-vm and it works fine.

Für alle, die auch mal vor dem Problem beim HP Microserver Gen 8 stehen, dass bei einem Neustart durch Xpenology das CMOS korrumpiert wird und alle Einstellungen resettet werden, sieht die Lösung im einzelnen wie folgt aus: - Ins BIOS gehen mit F9 - Einstellungen wie gewünscht machen (z.B. Netzwerkboot bei erster Netzwerkkarte ausschalten und RAID-Controller auf AHCI-Modus einstellen) - "System Default Options" - "User Default Options" - "Save User Defaults" auswählen => Damit werden die aktuellen Einstellungen als neue Grundeinstellungen gesetzt. Der Server startet instant neu und die neuen "Default Settings" überleben das korrumpieren des CMOS beim Herunterfahren/Neustarten von XPenology! Das Datum ist beim Neustart natürlich weiterhin auf 06.06.14 gesetzt, kann aber ganz leicht innerhalb des XPenologys per NTP-Einstellungen automatisch wieder korrekt gesetzt werden. So dauert das booten nur minimal länger, da auch die RAM-Bestückung neu erkannt wird und ganz kurz der weiße Bildschirm mit "habe neuen RAM entdeckt und teste ihn" angezeigt wird, aber der Server bootet nun ohne jeden weiteren Eingriff/Eingaben das XPenology!!

Workaround for BIOS Reset for HP Microserver Gen8 - Press F9 at boot to enter BIOS - Make your settings as desired (e.g. disable network boot and set the RAID-Controller into AHCI-Mode) - Choose "System Default Options" - "User Default Options" - "Save User Defaults" => this makes the actual settings to the new default settings. The Server starts instantly new and the new "Default Settings" are surviving the CMOS corruption forced by Xpenology at the shutdown or restart-process. The Date is of course false and set to 06.06.14 but this can be managed easily within Xpenology where you can set a NTP-Server as clock-source. Then the date will be corrected after the boot. I write this for all users as this bug costs me about 2 days....