arkilee

For those, who wants to passtrough several harddrives, please just buy a sata controller 4/6 ports (20$ - 30$ , check in this forum for compatible an positive feedback) and then just passthrough this "sata controller" card to the VM with proxmox. This way, all your disks : - will be compatible to real synology hardware, in case of you may plan to migrate to it in the future - will be able to perform SMART test and get SMART info/error (and temp) from Xpenology - I think sleep/hibernate HDD works better and save you electric ... Well, just go for it if you plan to use it as our main NAS.

I did few quick tests and it doesn't work for me either.

You can ignore this, but if you want to be sure about network speed you can test with iperf (check post before)

Maybe, try to read the article website I just gave you ... and you should find your answer for usb disk at least. But sata disk, i'm not sure how to find vid/pid if it exists.

As I said in my posts before, I cannot run a 918+ vm with my hardware ... so i wasn't really able to test or troubleshoot this one. So i dont know for ds918+ vm, but I know virtio works pretty good on ds3615xs. But to check if virtio network speed, you can test with iperf3 between the host and vm. You can find iperf spk here: http://www.jadahl.com/iperf-arp-scan/DSM_6.2/iperf_geminilake-6.2_3.9-1.spk

Well I not really knows for bootloader as sata disk, maybe it works the same as usb ... but with bootloader as usb disk, you will need to change vid/pid to match the usb disk bootloader to be able to get the update working. You can find instruction how to change to usb disk bootloader, or how to change vid/pid and SN in this website: https://www.uxora.com/other/virtualization/55-install-xpenology-dsm-6-2-x-on-proxmox

Well I found this tutorial which explains how to install xpenology dsm 6.2.3 on proxmox that may interest you: https://www.uxora.com/other/virtualization/55-install-xpenology-dsm-6-2-x-on-proxmox For hdd hotplug: I've never used hotplug disk so cannot really help on it. It may be working with a passtrough controller disk device which support hotplug and recognised by xpenology. I saw a option "HddHotplug=0" in the grub.cfg that may be needed to be changed to make it work. For 10Gb nic : You can do a passtrough device if you want a dedicated nic to xpenology. Otherwise just add a virtio network to vm which is bridge to this nic, like this it can be used by several vm. If you had the hotplug stuff working please share. :)

To make it easier, and you can now find this repository all jun's bootloaders with virtio/9p loaded for all dsm version: - synoboot_103b_ds3615xs_virtio_9p.img - synoboot_103b_ds3617xs_virtio_9p.img - synoboot_104b_ds918plus_virtio_9p.img HTH

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7 - Loader version and model: Jun's Loader v1.03b DS3615XS with virtio/9p loaded - Using custom extra.lzma: Yes, v0.11_test by IG88 - Installation type: VM - Proxmox 6.2-11 with PCI sata controller passtrough (with 4 disks attached) - Additional Comment: Bootloader boot as usb disk, Migration with keeping setting/data BREAKS my xpenology (maybe coz of chroot and other tiers apps) but it works back well once I did a new install migration with keeping data only (so needed to reinstall all apps)

Ok, great ... I just upgraded my vm xpenology ds3615xs dsm 6.1 with pci sata controller passtrough (4 disks attached to it) to dsm 6.2.3. Got some trouble with migration (keeping setting and data) which was slow/freezing and unreliable ... but it works great once I did a new install Migration resetting setting to default with keeping data only. Just painful that I still need to reinstall all apps and all stuffs. Indeed, for ds918+, I got old 6 yo AMD FX-8320E to run my VMs and it didnt work. But I can make work this ds918+ docker in a i7 linux laptop from this thread . So maybe, you're right about that works better with intel cpu or newer cpu. By the way, in this same thread, you can already find a ds918+ bootloader with virtio/9p that you can use to do backup template for ds918+. HTH

Don't take this msg seriously. If it's virtio, it can go higher than 10Gbs from vm to vm. First, it's better to check before on this forum to know if the update is working for your system. For minor update, it normally can be done directly with web gui like in normal synology For major update, if the bootloader still works with new dsm version, then it can be done as normal update. If bootloader does not work, then need to get a working bootloader and change the bootloader ... then do a migration update ( same as you change synology machine). I uploaded ds3615xs and ds3617xs to this mega repository : https://mega.nz/folder/PIwmHShI#US9fXR2VBZvg1_I3q0N8ZQ Theses backups have virtio (with rng and ballooning working but without compaction) and 9p. For ds918+ version, I didn't succeed to make it work on proxmox, even with your ds918+ backup ... does it work for you? For me, it just freeze just after the grub menu. So I cannot really make a backup template for this one. For those who wants to make it run the bootloader as usb: - Comment or remove sata0 disk - Then edit your <vm id>.conf by adding args like in this example for id 108 : args: -device 'nec-usb-xhci,id=usb-bus0,multifunction=on' -drive 'file=/var/lib/vz/images/108/vm-108-disk-0.raw,media=disk,format=raw,if=none,id=drive-disk-bootloader' -device 'usb-storage,bus=usb-bus0.0,port=1,drive=drive-disk-bootloader,id=usb-disk-bootloader,bootindex=999,removable=on' Well, bootloader as usb works for me so it may works for you too.

Ok thanks. I mainly use ds3615xs but I will do and test the others when i got some spare time.

I created a proxmox backup template for ds3615xs with virtio drivers added and based on timonych's one. It can be downloaded here: https://mega.nz/file/XZwAwYAC#3kIcZ8C3heA9UBTAUKdora74I7qes6kUVTrXkla3e9w This is the configuration of this backup: Virtio_net network seems to work fine and it can reach 13Gbits/s on my host rig. Virtio_blk seems to work as well, but disk are not recognised by dsm ... and it doesn't really matter because up to some test( on ssd drive) sata disk are as fast as virtio disk. I haven't tried pci/disk passtrough, but it should work with "q35" conf. Well let me know if this has issue. @timonych Please feel free to add this backup to your mega repository.

I dont know, you cannot choose PCI controller in Proxmox but you can choose SCSI controller. Well it doesn't really matter now as disk performance is almost the same in virtio or not. Or maybe my ssd disk, where virtual drives are stored, is not fast enough to make appearing any perf difference.

Only 4 virtual disks: - Sata0 : bootloader : 50MB - Sata1 : Dsm OS : 6GB - Virtio2 : Disk : 16GB - Scsci3 : Disk : 32GB (on virtio_scsi) Just did some dd speed test between disks, and I cannot see any significant speed improvement actually. LoL (Read: 545 MB/s , Write: 63.5 MB/s) So better using virtual sata disk which is recognised by dsm.

Update: - virtio_scsi drive appear in dsm as external esata drive, which cannot be used in dsm storage pool but only as external drive. It seems to work fine as external drive. - virtio_blk drive does appear anywhere in dsm, but it can be seen in linux cmd line and create filesystem on it. As a linux filesystem, it seems to works fine.

Yes, it's to get virtual drive with better io performance than emulated sata/pci drive. Here, I can see virtual drive with fdisk (here 16GiB=Virtio_blk and 32GiB=VirtioScsi) but I cannot see theses drives from dsm gui : $ sudo fdisk -l | grep "^Disk /dev" Disk /dev/sdg: 50 MiB, 52428800 bytes, 102400 sectors Disk /dev/sdh: 6 GiB, 6442450944 bytes, 12582912 sectors Disk /dev/md0: 2.4 GiB, 2549940224 bytes, 4980352 sectors Disk /dev/md1: 2 GiB, 2147418112 bytes, 4194176 sectors Disk /dev/zram0: 148 MiB, 155189248 bytes, 37888 sectors Disk /dev/zram1: 148 MiB, 155189248 bytes, 37888 sectors Disk /dev/vda: 16 GiB, 17179869184 bytes, 33554432 sectors Disk /dev/sdm: 32 GiB, 34359738368 bytes, 67108864 sectors And here virtio network speed with iperf between host and vm: $ iperf3 -c 192.168.0.1 -i 2 Connecting to host 192.168.0.1, port 5201 [ 5] local 192.168.0.25 port 49499 connected to 192.168.0.1 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-2.00 sec 2.74 GBytes 11.8 Gbits/sec 0 3.06 MBytes [ 5] 2.00-4.00 sec 3.07 GBytes 13.2 Gbits/sec 0 3.06 MBytes [ 5] 4.00-6.00 sec 3.07 GBytes 13.2 Gbits/sec 0 3.06 MBytes [ 5] 6.00-8.00 sec 2.97 GBytes 12.7 Gbits/sec 0 3.06 MBytes [ 5] 8.00-10.00 sec 2.95 GBytes 12.7 Gbits/sec 0 3.06 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 14.8 GBytes 12.7 Gbits/sec 0 sender [ 5] 0.00-10.04 sec 14.8 GBytes 12.7 Gbits/sec receiver iperf Done. Great news for 9p driver ... I may try to compile some stuff with 6.2.2 kernel/chaintools aswell and check if it work on 6.2.3. Thanks for your work.

No, I didn't add or removed any drivers. I just used your extra.lzma v0.11 which already have virtio ko drivers compiled. Then edit etc/rc.modules to add under EXTRA_MODULES: virtio virtio_ring virtio_mmio virtio_pci virtio_blk virtio_scsi virtio_net virtio_balloon No, only in proxmox kvm vm. So far, I only see virtio_balloon which is not loading with the following error: "virtio_balloon: Unknown symbol balloon_mapping_alloc (err 0)" Others virtio stuff seems to be ok: - virtio_net reach 13Gbps with iperf3 between host and vm - Virtio_blk disk seems to work as well but it's not recognised by DSM, so I didn't test much - Same for virtio_scsi, which is not recognised by dsm I read that extra drivers, you have compiled for dsm 6.2.2, seems not to work for 6.2.3 ... or maybe I didnt understant what u mean. Well I may try with 6.2.2 then when I have time ... it was to fix virtio ballooning (but it's not a very important) and maybe add 9p net drivers. For now, I am quite happy to get virtio network working on dsm 6.2.3.

Hello, I changed the extra.lzma for loader 1.03b ds3615 from extra3615_v0.11_test.zip to automaticaly load virtio drivers. Virtio_net network seems to works pretty well on Proxmox and dsm 6.2.3 thanks to IG-88 driver extension v0.11_test, where networks speed can reach 13Gbps without any noticeable issue for now. I would like to compile (and test) some more drivers for dsm 6.2.3 on loader 1.03b ds3615, but i cannot find linux kernel source for bromolow dsm 6.2.3 25426 and its chain tools. Where could I find this kernel source ? If not available, Which available older kernel source can I use to compile driver which may work for dsm 6.2.3 ? Thanks for your time to reply. Cheers

Hi, Is anyone of you succeed to make "virtio_net" working on 6.2 and jun's loader 1.03b ? I tried to compile and add modules without any sucess for now.

Nothing's wrong, It means that you already have "button" and "evdev" modules already loaded in the kernel. Maybe your bootloader has it already or you have run "s30acpid.sh start" several times. Try to reboot your xpenology then try to shut it down with Proxmox VE web interface to see if it works.

For those who are interested to be able to power off DSM 6.1.x VM via ACPI and get the shutdown working through Proxmox Virtual Environment, I have recompiled the button.ko and evdev.ko from the poweroff package of this post in order to get this working on dsm 6.1.x/DS3615xs. power-off_dsm61x_ds3615xs_x86.tar.gz

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 5.2 - Loader version and model: Jun's Loader v1.02b - DS3615xs (mod with added virtio) - Installation type: PROXMOX (M5A78L-M/USB3 with 2 SATA controller cards passtrhu) - Additional comments: Requires VM reboot

Yes it works for me now, I can save my bios now. Thanks.

Oh thank you, I just noticed that I didn't create a efidisk which seems to store the bios changes. LoL. Well actually I didn't know about that as I never used OVMF (UEFI) bios before. I think this may solves all the usb boot issue I guess :).