marigo

Members
  • Content count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About marigo

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. marigo

    DSM 6.2 Loader

    Not really a different setup. Just use SATA disks to setup the VM. Edit the grub.cfg to your needs. copy the synoboot.img to your VM and rename it to the SATA bootdisk. Here is my config: root@proxmox2:/etc/pve/qemu-server# cat 112.conf boot: c bootdisk: sata0 cores: 4 memory: 512 name: DSM6.2 net0: e1000=8A:9D:C6:25:F4:C3,bridge=vmbr0,tag=101 numa: 0 ostype: l26 sata0: local:112/vm-112-disk-2.raw,size=50M sata1: local:112/vm-112-disk-1.qcow2,size=10G scsihw: virtio-scsi-pci smbios1: uuid=3f77ff8c-6c22-4503-8fc4-863df965f9ef sockets: 1
  2. Or just install xpenology twice
  3. marigo

    DSM 6.2 Loader

    Successfully migrated my Proxmox VM from 6.2 (918+) to 6.2 (DS3615XS) with the new (1.03b) loader! Great work Jun!
  4. Yes, this is possible but indeed don't use the serials at the same time. Synology may block these serials. I think your friend will not be amused.
  5. marigo

    DSM 6.1.7-15284

    - 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: Proxmox KVM - Additional comments: REBOOT REQUIRED
  6. marigo

    DSM 6.1.4-15217 Update 5

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 3 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: KVM Proxmox 5.0 on Asrock Q2900-ITX - Additional comments: Requires reboot
  7. marigo

    DSM 6.1.3-15152 Update 4

    Updated to update 4 on Proxmox (5.0) KVM. Everything is still up and running.
  8. marigo

    DSM 6.1.x Loader

    Installed update 8 on VM in Proxmox. After 2 minutes online again. Everything seems to be working fine.
  9. marigo

    DSM 6.1.x Loader

    I choose the first option to boot the image. (synoboot.img) Are you using the correct *.img? It's about 50MB. "booting the kernel" is all I see too. Did you set the virtual NIC to "E1000"? Do you see that your DHCP server assinged an IP address to your VM? It should work with these settings I provided. Synology assistent should be in the same broadcast domain to search for "diskstation's" But I guess you already knew this.
  10. marigo

    DSM 6.1.x Loader

    Create a new VM in Proxmox. I used a IDE (0) harddisk (raw) device with 1GB storage. 512MB RAM, No CD-ROM, network E1000. When the VM is created, use the "synoboot.img" located in this thread and use it to boot the VM. rename the "synoboot.img" to the IDE disk. example: When VM "112" is created /var/lib/vz/images/112# ls synoboot.img vm-112-disk-1.raw /var/lib/vz/images/112# cp synoboot.img vm-112-disk-1.raw Boot the VM and search for the installer via the Synology Assistant. Manual install the DSM_DS3615xs_8451.pat After installing I could apply update 7 via the webinterface at this time of writing.
  11. marigo

    DSM 5.2-5644 Update 5

    Just updated to 5 running XPEnology as a guest on Proxmox. Only network services will do a restart. Everything looks fine. Bootloader: XPEnoboot DS3615xs5.2-5644.5 What happened to update 4?
  12. marigo

    DSM 5.2-5644 Update 3 safe?

    Did upgrade on guest KVM running on Proxmox. Everything looks fine.
  13. Here another succesfull update to 5.2-5644 running on Proxmox 4.0 as a guest KVM. No unmounted drives and everything seems to work. Maybe need to see if it's running after a period of time.
  14. Как вам удалось получить работу пакет? И как я могу получить пароль для загрузки патча? С уважением, Marigo
  15. marigo

    Asrock Q1900-ITX/Q1900DC-ITX

    I have installed Proxmox on the platform, which runs fine, but the usb pass through doens't work as good like Vmware does. Xpenolgy on the other hand runs flawlessly as guest in Proxmox. Does anyone know why ESXi can't be installed? Is it the "onboard" video that is aborting the installation of ESXi like Schnapps said in his reply?