Jump to content
XPEnology Community

cookie

Transition Member
  • Posts

    5
  • Joined

  • Last visited

Recent Profile Visitors

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

cookie's Achievements

Newbie

Newbie (1/7)

0

Reputation

  1. - Outcome of the update: SUCCESSFUL - DSM version prior to update: DSM 6.2.1-23824U6 - Loader version and model: Jun v1.04b - DS918 - Using custom extra.lzma: NO - Installation type: VM - Proxmox - KVM
  2. Works great for me. Here's my config: args: -device ich9-usb-ehci1,id=usb,multifunction=on,bus=pci.0,addr=0xa -drive file=/mnt/pve/templates/template/qemu/synoboot-test.qcow2,format=qcow2,if=none,id=drive-usb-disk2,cache=writeback -device usb-storage,bus=usb.0,port=2,drive=drive-usb-disk2,id=usb-disk2,bootindex=1,removable=off -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -realtime mlock=off -machine pc-i440fx-2.9,accel=kvm,usb=off,vmport=off,dump-guest-core=off -cpu kvm64,+kvm_pv_unhalt,+kvm_pv_eoi boot: nc bootdisk: sata0 cores: 2 cpu: kvm64 memory: 1024 name: test net0: e1000=A6:F0:EF:B7:91:45,bridge=vmbr0 numa: 0 ostype: l26 sata0: local-lvm:vm-114-disk-1,size=10G smbios1: uuid=2dce823b-ffd0-44e5-8914-57feab9873a1 sockets: 1 tablet: 0 vcpus: 2 vga: qxl
  3. cookie

    DSM 6.2 Loader

    Hi. Here's mine which works fine for me: args: -device ich9-usb-ehci1,id=usb,multifunction=on,bus=pci.0,addr=0xa -drive file=/mnt/pve/templates/template/qemu/synoboot-test.qcow2,format=qcow2,if=none,id=drive-usb-disk2,cache=writeback -device usb-storage,bus=usb.0,port=2,drive=drive-usb-disk2,id=usb-disk2,bootindex=1,removable=off -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -realtime mlock=off -machine pc-i440fx-2.9,accel=kvm,usb=off,vmport=off,dump-guest-core=off -cpu kvm64,+kvm_pv_unhalt,+kvm_pv_eoi boot: nc bootdisk: sata0 cores: 2 cpu: kvm64 memory: 1024 name: test net0: e1000=A6:F0:EF:B7:91:45,bridge=vmbr0 numa: 0 ostype: l26 sata0: local-lvm:vm-114-disk-1,size=10G smbios1: uuid=2dce823b-ffd0-44e5-8914-57feab9873a1 sockets: 1 tablet: 0 vcpus: 2 vga: qxl Of course, you have to change the path to your synoboot image file. I use the qcow2 format, just as it's a bit smaller. Otherwise you can use the synoboot.img file directly. Just rename the suffix to '.raw' as already mentioned. I currently run 6 different virtual xpenology machines on just one tiny NUC (with 16GB memory) in a Proxmox cluster. The harddrives are mounted indirectly via iSCSI with the help of Proxmox' storage manager. No RAID inside the machines. RAID is already done on the iSCSI target side. I'm totally happy with this setup. Far more better than running XPenology on baremetal, like my old ReadyNAS.
  4. Working fine on: Netgear ReadyNAS Ultra 4 (RNDU4000) Synoboot 1.02b DSM 6.1.3-15152 Update 4
  5. Well, that's really a pity as some nice Synology products, like the DS414slim, are using the same CPU. I guess, the DS216se is quiet similar to the old ReadyNAS Duo v2. I would like to port the bootloader and the kernel to that machine, if I only would get some information on how these thing are crosscompiled and packaged correctly. Greetings
×
×
  • Create New...