hellbondz

Members
  • Content Count

    36
  • Joined

  • Last visited

Community Reputation

1 Neutral

About hellbondz

  • Rank
    Junior Member

Recent Profile Visitors

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

  1. Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 Update 2 - Loader version and model: Jun's v1.03b DS3615sx - Using custom extra.lzma: NO - Installation type: VM - Proxmox 5.3-11 - Additional comments: Changed LAN from e1000 to e1000e
  2. I have older hardware, based on socket 775. From what i know and tested 1.04b does not run on core2duo, it needs at least Haswell CPU. My hardware has much too much power for my DS3615xs setup so i don't see a point in forcing to 1.04b loader and change hardware. Basically for my needs i don't need DS918+ features 😉. Cheers.
  3. Hi everyone. After a grate help from 'dodo-dk' (You're the best man) and a lot of try and errors i managed to run DSM 6.2.1u6 on Proxmox 5.3-11. I'll share my insights and maybe it'll be useful for someone. Proxmox does have 4 LAN cards model to chose from the list, but as we all know Synology dropped drivers for some devices (e1000, vmware3...) so new version of DSM stopped working on Proxmox. But Proxmox allows you to chose different models (not shown in choosing list) , we just have to add it to 'args:' parameters, just like we did with usb boot key. For this to work you need to know few things: 1) This won't work on OVS bridge/bond - it has to be Linux bridge/bond 2) The Linux bridge/bond has to have gateway set When we are adding LAN card from 'args:' it looks like the LAN card chooses bridge/bond on which the gateway is set, so that's why it's needed to be set. First thing you may check it's if e1000e LAN card is available in your kvm. So in Proxmox shell write command: kvm -device help Under 'Network devices' you should see line: name "e1000e", bus PCI, desc "Intel 82574L GbE Controller" The next step is to find your 'args:' parameters. To do this we need to use another command: qm showcmd YOUR-VM-ID YOUR-VM-ID - is ID of your Xpenology machine with added e1000 LAN card. From the output you need to copy two arguments: netdev and device. In my case it looks like this: -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=00:11:32:2c:a7:85,netdev=net0,bus=pci.0,addr=0x12,id=net0' For this to work you have to remove the 'script' parts from 'netdev'' and change model from 'e1000' to 'e1000e' in device argument. you can also remove the " ' " signs. After changes it should look like this: -netdev type=tap,id=net0,ifname=tap100i0 -device e1000e,mac=00:11:32:2c:a7:85,netdev=net0,bus=pci.0,addr=0x12,id=net0 Next you need to add changed arguments in to the VM config file (/etc/pve/qemu-server/YOUR-VM-ID.conf). In my case 'args:' line looks like this: args: -device ich9-usb-ehci1,id=usb,multifunction=on,bus=pci.0,addr=0xa -drive file=/var/lib/vz/images/103/vm-103-USB103b.raw,format=raw,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 -netdev type=tap,id=net0,ifname=tap103i0 -device e1000e,mac=BA:E2:8A:3B:AC:3E,netdev=net0,bus=pci.0,addr=0x12,id=net0 The last thing is to remove the 'net' device from config file, so just comment or remove the line with 'net' device. In Proxmox web interface the LAN device wont be visible, but it will work. So, summing things up, I'm not Proxmox specialist so i didn't knew all of that. One more time thank you 'dodo-dk' for your knowledge and time. God bless all Xpenology enthusiasts, Xpenology devs and Proxmox for being best free virtualization tool i know.
  4. Ok maybe I'm blind or just stupid but i don't know how to add e1000e card to proxmox VM. Can you tell me how You dit it?
  5. From what i know it's not possible for now. Ther's no working lan card model for DSM6.2.1. I tried to insert Virtio drivers to 1.03b loader but with no luck so far. Quicknick maybe you tried it?
  6. hellbondz

    DSM 6.2 Loader

    I'm running Jun 1.03b loader, on Proxmox VM machine. DSM 6.2.1 causes kernel panic for e1000 lan card. Maybe someone knows how to inject drivers to Jun's 1.03b loader?
  7. hellbondz

    DSM 6.2 Loader

    Hi everyone and thanks Jun for your hard work. I have one question because i didn't found an answer on the forum. A lot of people is using loader for DS3615 and DS3617 on their devices. Jun are you planning to update those loaders to support DSM 6.2.1? From my knowledge loader for DS918+ does not work on older devices so for many of us switching to this loader is connected with changing hardware (when old hardware works just fine). It would be grate to know what are your plans in this subject.
  8. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5 15254 Update 1 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: VM - PROXMOX 5.1-46 - Additional comments: REBOOT REQUIRED
  9. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 5 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Proxmox 5.1-43 - Additional comments: Requires reboot
  10. Everything is described in this thread. Use "Proxmox UEFI' bios.
  11. No problem. I'm glad to help. Please let me know if it'll work for You.
  12. Here it is: args: -device 'piix3-usb-uhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/100/vm-100-disk-1.raw,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot' balloon: 128 bios: ovmf boot: c cores: 4 efidisk0: local:100/vm-100-disk-2.raw,size=128K hotplug: disk,usb memory: 3072 name: MxxSN-01 net0: e1000=00:11:32:2C:A7:85,bridge=vmbr1 net1: e1000=00:15:17:7C:F8:66,bridge=vmbr2 numa: 0 onboot: 1 ostype: l26 sata0: /dev/disk/by-id/ata-ST sata1: /dev/disk/by-id/ata-WDC sata2: /dev/disk/by-id/ata-WDC sata3: /dev/disk/by-id/ata-WDC sata5: /dev/disk/by-id/ata- scsihw: virtio-scsi-pci serial0: socket smbios1: uuid=b0081c2c-8ad9-42ae-ab51-9f260e2e946b sockets: 1
  13. Hi. That's weird. I tested it a minute ago. My "bios" doesn't loose it's settings. There's no difference if i reboot or shutdown VM. I even rebooted fully Proxmox server and i checked it in bios. USB is still on first place. And every setting i have made in bios stays that way. Maybe you have some different (older) Proxmox version?