Jump to content
XPEnology Community

TBK

Member
  • Posts

    82
  • Joined

  • Last visited

Posts posted by TBK

  1. By the way I just install latest iLo 2.4 which is not released yet. HP site showing 1 April for release. If anyone interested here is the link.

     

     

    You might not know this, but the iLO update only updates the iLO chip, not the BIOS. For that you need the Service Pack for ProLiant (SPP).

     

     

    You can get the latest version here (2015.10.0): ftp://ftp.hp.com/pub/softlib2/software1 ... 8/v113584/

     

    Burn the iso to a USB or DVD and boot it, select the auto update and the software on the iso does the rest.

     

    The SPP contains many fixes for all sorts or issues, also for ESXi:

    (Revision) VMware - Recovered Paths Are Not Restored When Using an HPE Smart Array Controller Connected to a Shared Storage RAID Enclosure on VMware ESXi 5.0, ESXi 5.1, ESXi 5.5 or ESXi 6.0

    Source: http://h17007.www1.hp.com/us/en/enterpr ... x#tab=TAB2

  2. I have never used ESXi for a DSM setup, I have used Hyper-V, VirtualBox, Vmware Workstation, Xen, KVM and bare metal.

     

    People are running the ESXi setup you are describing, but apparently there is a issue with ESXi, XPEnoboot and NFS.

     

    As long as you have network connection to your VMs you can transfer files, so transferring files back and forth will not be an issue.

     

    I can not answer question 3., try to find a guide here on the forum or elsewhere for ESXi and XPEnoboot.

     

    My focus is at the moment on DSM 6 :smile:

  3. I will try the processor changes and look up the link tomorrow it is late here in Australia right now.

    I was in Australia a few days ago :razz: right now I am in the Pacific Ocean near NZ, will be back to AU in few weeks :grin:

     

     

    Just to get the basic compatibility right what versions of XPEnoboot, DSM and PhpVirtualbox are known to work together inside VMware?

    Latest.

     

     

    I am confused on the downloads page (http://xpenology.me/downloads/) there is the top section for DSM 5.2-5644 DS3615xs .pats then there is a section below that called Synology DSM (based on GNU Open Source) and DSM 5.2-5644 (Only vs XPEnoboot 5644)

     

    Which of these ,pats do I use? the top section DSM .pat or the GNU open source DSM .pat? or a Synology 5.2 DSM .pat?

    Ignore the "Synology DSM (based on GNU Open Source)" and "DSM 5.2-5644 (Only vs XPEnoboot 5644)" section further down the http://xpenology.me/downloads page, the latest DSM & XPEnoboot versions are always listed at the top.

     

    Grab the XPEnoboot 5.2-5644.5 boot media you want to use (img, iso, vmdk), mount it in your VM, start the VM, access the webpage http://:5000, do a manual install, browse to the pat file.

     

    First you install the "base pat" http://download.synology.com/download/D ... s_5644.pat and then update to latest patch http://download.synology.com/download/D ... 3615xs.pat

     

    Get the latest phpvirtualbox version from here http://spk.diablos-netzwerk.de/download ... &t=regular

     

     

    Do you have to install the DSM .pat updates incrementally one by one that is from 5644 to 5644.1 then 5644.2 then 5644.3 and so on to 5644.5 or can I apply 5644.5 to 5644 directly?

    You can apply 5644.5 to directly to 5644.

  4. Just to clarify you have installed DSM in a Vmware virtual machine, then installed PhpVirtualbox (Oracle VM Virtualbox), created a VM with PhpVirtualbox for Windows 7, am I understanding it correctly?

     

    If what I describe above is the case, then I would recommend that you alter your setup. It is possible to run nested hypervisors (= PhpVirtualbox inside a Vmware VM), but it is highly unadvised since it eats up a lot of performance.

     

    If you still need it, then in the Vmware VM change the settings for "Processors" and enable "Virtualize Intel VT-x/EPT or AMD-V/RVI" and "Virtualize CPU performance counters". This page might also be of help https://4sysops.com/archives/how-to-run ... rkstation/

  5. I think so. You can always extract the INFO file from the package and see what arch's the package supports.

     

    I do not't know why Synology has changed their build practices. It might have to do with DSM 6 being x64.

     

    64-Bit Architecture

     

    DSM 6.0 has been optimized for all models based on Intel 64-bit processors to improve general performance.

     

    Supports over 4GB memory allocation for one single process to deploy large scale application.

    https://www.synology.com/en-global/dsm/6.0beta/ReleaseNote

  6. There are github repos with older versions (5.0 and 5.1... builds - nanoboot...) available where you can see the patches to the kernel code and how the initrd (rd.gz) is made.

    E.g. https://github.com/Jman420/nanoBoot-DSM5.1/

     

    DSM relies on a closed source kernel module called synobios.ko, this file you have to either patch yourself (grab it from a Synology pat file) or extract a already patched version from a xpenology build.

×
×
  • Create New...