marigo

Members
  • Content count

    24
  • Joined

  • Last visited

Community Reputation

0 Neutral

About marigo

  • Rank
    Junior Member

Recent Profile Visitors

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

  1. marigo

    DSM 6.2.1-23824 - WARNING

    - Outcome of the update: SUCCESSFUL - DSM version prior update: Fresh install on Proxmox 5.2.8 - Loader version and model: Jun's Loader v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: VM - KVM - Additional comments: Used Intel E1000 NIC
  2. marigo

    DSM 6.2 Loader

    Check out some tutorials in the installation section.
  3. Hey, great that you have found the issue. I use the "default" SeaBIOS so that's why I don't had any problem. :) In the meantime you can use 1.03b with a sata drive as the boot disk.
  4. I have no experience with booting from USB inside Proxmox. I think that it should not matter what bootdevice you use. You can try the 50MB Sata loader and see if that will help. With my setup I can access the terminal when booting so somewhere something is different.
  5. root@proxmox2:/etc/pve/qemu-server# cat 103.conf boot: c bootdisk: sata0 cores: 4 memory: 512 name: DSM-test net0: e1000=32:32:66:61:37:30,bridge=vmbr0,tag=101 numa: 0 ostype: l26 sata0: local:103/vm-103-disk-2.raw,size=50M sata1: local:103/vm-103-disk-1.qcow2,size=8G serial0: socket smbios1: uuid=dec697d4-36e6-43de-a2e0-896db9f2dfe1 sockets: 1
  6. Yes, I can confirm. Just tried it seconds ago. No problem. The "qm terminal 101" also gave me the same results. I know I had to switch from "IDE" harddisks to "SATA" with 1.03b loader. So for the migration I had to shutdown the DSM6.1 VM, detach the IDE HD en edit this to SATA. Then add it again and set new bootdisk. Hope this helps you.
  7. For the serial connection to the VM I use this: # in this example VM 101 is our guest to add serial console. # set serial console for VM qm set 101 -serial0 socket # connect to VM from proxmox TTY session socat UNIX-CONNECT:/var/run/qemu-server/101.serial0 STDIO,raw,echo=0,escape=0x0f I don't know if loader 1.03b is also capable of running DSM < 6.2
  8. marigo

    DSM 6.2 Loader

    Right! For a clean install just use the loader, but for a migration there is this /.xpenoboot/ folder in the root directory when applying the 6.2 DSM software. Remove this folder with: rm -r /.xpenoboot/ and reboot the system.
  9. 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
  10. Or just install xpenology twice
  11. 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!
  12. 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.
  13. 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
  14. 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
  15. marigo

    DSM 6.1.3-15152 Update 4

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