James Campbell

Members
  • Posts

    2
  • Joined

  • Last visited

Everything posted by James Campbell

  1. Yes, I have a similar set up. But I'm using an "unassigned device" 4TB HDD passing through to Synology. I have the same as you with the HDD driver quirk. I think the speed you're getting is consistent to the speeds I'm seeing from my synology VM. The main limitation is that the e1000 emulated NIC requires a lot of CPU, the rtl8139 (or something like that) emulated NIC is worse still. I would love to not have to use the emulated NIC with synology, but no idea how to install the drivers into synology, I'm sure it's possible, but my *nix skills are no where near that level. I have a significantly more powerful CPU than you, and get around 1.5gbit with the CPU sitting at full load. I'm okay with that for my usage scenario. I applaud your ethos of the low power consumption system though, How many watts is it eating?
  2. If anyone is still wanting to do this, I've had this working fine on unraid 6. I have the main storage HDD as an unassigned device in the unraid configuration. Drive hibernation is working okay after running hdparm -S 100 /dev/sdc which will set standby to 8min20sec, so I'm very happy with the configuration. I wanted Synology has I love the backup functionality it has - I do nightly off site backups to my mates house, the functionality where my phone with DS photo auto backs up photos when I walk into the house and it finds wifi, and DS Audio is very nice for playing music when I'm working and the USB passthrough for shared printer is working well. I'm sure unraid does these things too with docker maybe, but my learning didn't get that far yet, sorry. I don't like the Synology webserver, so I'm using a bitnami NGINX ubuntu VM for that, which is excellent so far. Bad points for me : I'm using the qemu e1000 emulated NIC. It's no where near as fast as the synthetic NIC that my Windows 10 VM is using on the same hardware. It does around 2gbit, but then gets bottlenecked by the CPU in my totally unscientific testing. I don't see how Synology could read from the UNRAID array though directly, I need to think about that. So I agree it is a weird setup, it's not really taking advantage of UNRAID's core strengths. Here is the XML for the VM. I'm no expert, feel free to suggest improvements. Thanks to Jon for making what I consider to be an excellent system in Unraid. I've enjoyed my playtime. <domain type='kvm'> <name>Synology 5.0</name> <uuid>123264dc-b7cc-d74f-b2d9-eb766dd97033</uuid> <description>Synology 5.0</description> <metadata> <vmtemplate name="Custom" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='1'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disk1/isos/XPEnoboot_DS3615xs_5.1-5055.1.img'/> <target dev='hda' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disk1/vdisks/Synology 5.0/vdisk2.img'/> <target dev='hdb' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-ST4000DM000-1F2168_Z301MJJ6'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:08:60:d9'/> <source bridge='br0'/> <model type='e1000'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Synology 5.0.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x07' function='0x0'/> </memballoon> </devices> </domain>