Jump to content
Randall8686

Xpenology VM any one running this ?

98 posts in this topic Last Reply

Recommended Posts

On 10/22/2019 at 3:23 PM, Magnetio said:

Now running 1.02 on 6.1.7 VIRTIO in stead of e1000e btw.
Seems the network is more stable and speed of mounted shares to unraid less or close to zero cap...
Fixed there is no more need editing the xml e1000e, sata controller, NFS/CIFS network cap, and unexplained constant high network load in DSM.
Also much faster... guess the only plausible explanation is needs to work less harder on VIRTIO compared to e1000e...

 

This is probably a dumb question, but I'm assuming you're running 6.1.7, because it won't boot with anything higher while using 1.02 bootloader?

 

I'd love to not have to change from e1000e, and fix the weird high network load in DSM, but at the same time, I like being on the more recent versions of DSM. 😕

Share this post


Link to post
3 hours ago, eleazar said:

 

This is probably a dumb question, but I'm assuming you're running 6.1.7, because it won't boot with anything higher while using 1.02 bootloader?

 

I'd love to not have to change from e1000e, and fix the weird high network load in DSM, but at the same time, I like being on the more recent versions of DSM. 😕

Not a dumb question... Yes running 6.1.7 as max version on 1.02b
Tried them all. This is definately the most stable
You can get VIRTIO to work with a kernel extract, plenty of guide's around. As long as not above kernel 3.11* (not sure, just google it)
But I did not manage to get it to work.

Share this post


Link to post
15 minutes ago, Magnetio said:

Not a dumb question... Yes running 6.1.7 as max version on 1.02b
Tried them all. This is definately the most stable
You can get VIRTIO to work with a kernel extract, plenty of guide's around. As long as not above kernel 3.11* (not sure, just google it)
But I did not manage to get it to work.

Thanks for the quick response!

 

I think I'm going to wipe my 6.2.x VM and start over with 1.02 and 6.1.7. 

 

Just to clarify, you didn't have to do anything special? Just use 1.02 bootloader, and install 6.1.7 and it works "out of the box" without having to adjust network adapter?  For example, same settings for the VM as your post here (minus the virtio change):

 

Share this post


Link to post
1 minute ago, eleazar said:

Thanks for the quick response!

 

I think I'm going to wipe my 6.2.x VM and start over with 1.02 and 6.1.7. 

 

Just to clarify, you didn't have to do anything special? Just use 1.02 bootloader, and install 6.1.7 and it works "out of the box" without having to adjust network adapter?  For example, same settings for the VM as your post here (minus the virtio change):

 

Yes you should....
Nope... won't work out of the box
You need the 1.02b bootloader with VIRTIO drivers
Else it won't be any different ;)

Share this post


Link to post

Thanks to this thread, running Synology 6.2.

 

I needed 6.2 for the Moments feature, which is what took me so long to migrate to UnRaid. The moments feature is just second to none. The other cloud, self hosting apps on UnRaid, I had nothing but headaches with, and that doesn't fly with some of my friends. 

 

Thanks everyone for your work!!

Edited by Viper359

Share this post


Link to post

Anyone able to activate their camera license keys? I can't seem to. It says no connection to the internet when trying to activate them.   I've got the network working, able to update apps and shared folders all work.  I'm migrating from my actual Synology DS1010+ to a virtualized setup.  My DS1010+ is getting quite old (10 years old ...) and I can't justify spending that amount of cash on a newer unit.  VM (on EXSI) is working fine.. and also have it on my unraid server.

Edited by mistah

Share this post


Link to post
On 12/20/2019 at 7:45 PM, mistah said:

Anyone able to activate their camera license keys? I can't seem to. It says no connection to the internet when trying to activate them.   I've got the network working, able to update apps and shared folders all work.  I'm migrating from my actual Synology DS1010+ to a virtualized setup.  My DS1010+ is getting quite old (10 years old ...) and I can't justify spending that amount of cash on a newer unit.  VM (on EXSI) is working fine.. and also have it on my unraid server.

Don't know how, didn't get this to work the proper way....
Got 8.2.6-6009 with 25 camera's running with the help of someone I've been in contact over the years and is much appreciated ;)

Share this post


Link to post

Hi everyone

 

I seem to be stuck - the "find.synology.com" dosent work? but if I go to my router I can see a new Diskstation with a IP that I cant access?

Have read this thread over and over again and the solution eludes me?

 

I am using the standard bridge? (And my Unraid server works perfectly with other VM's)

 

I also need to pause and do a force stop - normal stop of the VM doesn't work? is this normal?

 

BTW: I also tried changing the Bus to 4

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
  <name>XPEnology</name>
  <uuid>027c5da5-0973-5a2c-a9d5-d93baed45c62</uuid>
  <description>XPEnology</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="CentOS" icon="centos.png" os="centos"/>
  </metadata>
  <memory unit='KiB'>1048576</memory>
  <currentMemory unit='KiB'>1048576</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='6'/>
    <vcpupin vcpu='2' cpuset='1'/>
    <vcpupin vcpu='3' cpuset='7'/>
    <vcpupin vcpu='4' cpuset='2'/>
    <vcpupin vcpu='5' cpuset='8'/>
    <vcpupin vcpu='6' cpuset='3'/>
    <vcpupin vcpu='7' cpuset='9'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-4.1'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/027c5da5-0973-5a2c-a9d5-d93baed45c62_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='4' threads='2'/>
  </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/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/XPEnology/synoboot.img'/>
      <target dev='hdc' bus='usb'/>
      <boot order='1'/>
      <address type='usb' bus='0' port='1'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/XPEnology/vdisk2.img'/>
      <target dev='hdd' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x11'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x12'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0x13'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <interface type='bridge'>
      <mac address='xx:xx:xx:xx:xx:xx'/>
      <source bridge='br0'/>
      <model type='e1000'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <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'>
      <address type='usb' bus='0' port='2'/>
    </input>
    <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='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
</domain>

 

Share this post


Link to post
Posted (edited)
3 hours ago, casperse said:

Hi everyone

 

I seem to be stuck - the "find.synology.com" dosent work? but if I go to my router I can see a new Diskstation with a IP that I cant access?

Have read this thread over and over again and the solution eludes me?

 

I am using the standard bridge? (And my Unraid server works perfectly with other VM's)

 

I also need to pause and do a force stop - normal stop of the VM doesn't work? is this normal?

 

BTW: I also tried changing the Bus to 4


<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
  <name>XPEnology</name>
  <uuid>027c5da5-0973-5a2c-a9d5-d93baed45c62</uuid>
  <description>XPEnology</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="CentOS" icon="centos.png" os="centos"/>
  </metadata>
  <memory unit='KiB'>1048576</memory>
  <currentMemory unit='KiB'>1048576</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='6'/>
    <vcpupin vcpu='2' cpuset='1'/>
    <vcpupin vcpu='3' cpuset='7'/>
    <vcpupin vcpu='4' cpuset='2'/>
    <vcpupin vcpu='5' cpuset='8'/>
    <vcpupin vcpu='6' cpuset='3'/>
    <vcpupin vcpu='7' cpuset='9'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-4.1'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/027c5da5-0973-5a2c-a9d5-d93baed45c62_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='4' threads='2'/>
  </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/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/XPEnology/synoboot.img'/>
      <target dev='hdc' bus='usb'/>
      <boot order='1'/>
      <address type='usb' bus='0' port='1'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/XPEnology/vdisk2.img'/>
      <target dev='hdd' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x11'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x12'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0x13'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <interface type='bridge'>
      <mac address='xx:xx:xx:xx:xx:xx'/>
      <source bridge='br0'/>
      <model type='e1000'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <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'>
      <address type='usb' bus='0' port='2'/>
    </input>
    <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='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
</domain>

 

OK finally managed to get it found by using the actual IP

But any package I try to install I get this:

image.png.17a90b26a7b605dc91353141a8247801.png

 

Do you have any special setup for inputting a VID and PID? (if then how?)

(I also added the serial generated and I added the mac address to the synoboot.img still get the same error?

Only thing I didn't couldn't update was the VID and PID (Is this needed on a virtual USB stick?)

 

Edited by casperse

Share this post


Link to post

Ok after contacting the Xpenology forum I decided to go back to DSM 6.1.7 and it works!

 

https://xpenology.com/forum/topic/24168-dsm-621-on-unraid-vm/?tab=comments#comment-129798

 

But any attempt to use any of the loaders used for DSM 6.2.X gives above error?

I have looked through all the XML files and havent found any "Smoking" gun

 

PLEASE: Anyone who has the new 6.2 working under Unraid 6.8.0 could you please share your:

 

loader

XML

and what PAT file you initial installed...

 

Seem to be the key to get this working :-)

Share this post


Link to post
Posted (edited)
On 12/8/2019 at 11:14 PM, Viper359 said:

Thanks to this thread, running Synology 6.2.

 

I needed 6.2 for the Moments feature, which is what took me so long to migrate to UnRaid. The moments feature is just second to none. The other cloud, self hosting apps on UnRaid, I had nothing but headaches with, and that doesn't fly with some of my friends. 

 

Thanks everyone for your work!!

You got 6.2 working? and its still running under Unraid 6.8 could you share what you have used:

 

XML

Bootloader

PAT - dsm installation initial version?

 

UPDATE: I got it working now! on the latest and greatest DSM! :-)

 

For others I missed the timeout in the bootloader set it to 10 sec and select VM when you boot in the VNC

Also I changed the Set machine as Q35-3.0? and it works!

Edited by casperse

Share this post


Link to post
On 12/23/2019 at 9:14 PM, Magnetio said:

Don't know how, didn't get this to work the proper way....
Got 8.2.6-6009 with 25 camera's running with the help of someone I've been in contact over the years and is much appreciated ;)

lucky!

Share this post


Link to post
On 11/12/2019 at 8:35 PM, Magnetio said:

Not a dumb question... Yes running 6.1.7 as max version on 1.02b
Tried them all. This is definately the most stable
You can get VIRTIO to work with a kernel extract, plenty of guide's around. As long as not above kernel 3.11* (not sure, just google it)
But I did not manage to get it to work.

Could you share how to get the Network activity down and getting VIRTIO to work?

the e1000e is not so efficient 

Share this post


Link to post
On 1/2/2020 at 8:04 PM, casperse said:

Ok after contacting the Xpenology forum I decided to go back to DSM 6.1.7 and it works!

 

https://xpenology.com/forum/topic/24168-dsm-621-on-unraid-vm/?tab=comments#comment-129798

 

But any attempt to use any of the loaders used for DSM 6.2.X gives above error?

I have looked through all the XML files and havent found any "Smoking" gun

 

PLEASE: Anyone who has the new 6.2 working under Unraid 6.8.0 could you please share your:

 

loader

XML

and what PAT file you initial installed...

 

Seem to be the key to get this working 🙂

6.8.0 should not make any difference to prior Unraid version (at least untill 6.2.2 24922), kernel version does indeed
VIRTIO will not work unless you have a modified bootloader, e1000e, vmxnet3, e1000 should in any case and play around....

Share this post


Link to post

Anyone else having issues I'm in 6.8.1 and now my Synology will not come up I was running e1000e as model but not finding it in network now

Edited by khile

Share this post


Link to post
On 1/3/2020 at 9:26 AM, casperse said:

Could you share how to get the Network activity down and getting VIRTIO to work?

the e1000e is not so efficient 

If anyone is running Xpenology on Unraid 6.8.2 I would really appreciate knowing the loader/.pat versions and some basic VM setup info (MAC used, disk setup, etc).

 

I tried using the steps from https://xpenology.com/forum/topic/24168-dsm-621-on-unraid-vm/?tab=comments#comment-129798 and from other posts in this thread. With e1000 set to bridge I can only get a 169.254.* IP address on my VM.

 

Any clues on getting this to work?

I am using the loader: synoboot-ds918_1.04b

And the DSM: DSM_DS918+_23824_(6.2.1).pat

I have updated the MAC to my Unraid host MAC & SN is generated in the synoboot.img

 

XML of my VM below, any I appreciate any help with getting this to work. 

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
  <name>Xpenology</name>
  <uuid>af3e8f37-941e-f348-37ae-d27881dbddca</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="CentOS" icon="centos.png" os="centos"/>
  </metadata>
  <memory unit='KiB'>2097152</memory>
  <currentMemory unit='KiB'>2097152</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>2</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='2'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-3.0'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='1' threads='2'/>
  </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/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/isos/synoboot.img'/>
      <target dev='hdc' bus='usb'/>
      <boot order='1'/>
      <address type='usb' bus='0' port='1'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='writeback'/>
      <source file='/mnt/user/domains/Xpenology/vdisk2.img'/>
      <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='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x11'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x12'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0x13'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='pci' index='5' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='5' port='0x14'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
    </controller>
    <controller type='pci' index='6' model='pcie-to-pci-bridge'>
      <model name='pcie-pci-bridge'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <interface type='bridge'>
      <mac address='xx:xx:xx:xx:xx:xx'/>
      <source bridge='br0'/>
      <model type='e1000'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <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'>
      <address type='usb' bus='0' port='2'/>
    </input>
    <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='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
</domain>


 

 

 

 

Edited by ovidiulazarescu

Share this post


Link to post
Posted (edited)

Definitely need a hand from someone. I feel like I'm lost in making virtio_net works, and so as 9p(for mounting unraid shares).

 

First, I started with docker made by segator. The image segator/xpenology:latest somehow works and unless you want to load 9p drivers. I compile the drivers following the github's instruction. Turns out I compile the drivers for newer kernel(3.10.102) and the image is running at 6.0.2-8451 which has a linux kernel of 3.10.77. I went through again with 3.10.77's packages but the progress seems stuck because the source code does not contain a copy of synobios.h.
The newer image(segator/xpenology:6.1.3-15152) stucks at launching from qemu(https://forums.unraid.net/topic/59843-dsm-ui-on-docker-unraid/?do=findComment&comment=816993

 

Then, I came to VM instead of docker. Life seems easier until I go further. I follow the guide to repack virtio* and 9p* drive into boot img. VM stucks at booting if I switch to virtio network adaptor instead of e1000. e1000 is 100% working for normal use I think.

 

9p mount also won't work if I try the mount command from https://github.com/segator/xpenology-docker . As it will said mount: special device blablabla does not exist

 

Funny thing is that those drivers load at boot time

ash-4.3# dmesg|grep 9p
[   10.862020] 9pnet: Installing 9P2000 support
[   10.867318] 9p: Installing v9fs 9p2000 file system support
ash-4.3# dmesg|grep virtio
[   10.848469] virtio_balloon: Unknown symbol balloon_mapping_alloc (err 0)
[   10.859134] virtio_console: Unknown symbol hvc_remove (err 0)
[   10.859149] virtio_console: Unknown symbol hvc_kick (err 0)
[   10.859158] virtio_console: Unknown symbol hvc_alloc (err 0)
[   10.859166] virtio_console: Unknown symbol hvc_poll (err 0)
[   10.859177] virtio_console: Unknown symbol hvc_instantiate (err 0)
[   10.859186] virtio_console: Unknown symbol __hvc_resize (err 0)
[  393.861496] 9pnet_virtio: no channels available
ash-4.3# lsmod|grep virtio
9pnet_virtio            6278  0
9pnet                  38996  2 9p,9pnet_virtio
virtio_scsi             9225  0
virtio_blk              8496  0
virtio_net             17272  0
virtio_mmio             4064  0
virtio_pci              6877  0
virtio_ring             7872  6 virtio_blk,virtio_net,virtio_pci,9pnet_virtio,virtio_mmio,virtio_scsi
virtio                  3506  6 virtio_blk,virtio_net,virtio_pci,9pnet_virtio,virtio_mmio,virtio_scsi

 

Resources I've gone thru:

 

https://forums.unraid.net/topic/59843-dsm-ui-on-docker-unraid

https://forums.unraid.net/topic/71316-xpenology-vm-any-one-running-this/

https://github.com/segator/xpenology-docker

https://xpenology.club/compile-drivers-xpenology-with-windows-10-and-build-in-bash/

https://xpenology.com/forum/topic/7387-tutorial-dsm-6x-on-proxmox/

https://xpenology.com/forum/topic/7884-xpenology-runing-on-docker/

https://xpenology.com/forum/topic/23822-kvm-virtio-network-driver-extension/

 

FYI, I’m using the easiest combination of xpenology img(3615 on 6.1.7 v1.02b) on VM

Edited by Tony_L

Share this post


Link to post
Posted (edited)

Woouu that seems really complicated! Is this to fix the LAN speed?

 

I just followed the guide on this page and on the link here to the Xpenology forum

Yes its trial and error I have tried them all and the highest DSM I could get working was with:

 

XPEnology_3 DSM_DS3615xs_24922 v6.2.2

XPEnology_2 DSM_DS3617xs_23739_6.2

XPEnology DSM_DS3615xs_6.1.7

 

https://xpenology.com/forum/topic/24168-dsm-621-on-unraid-vm/

 

Biggest problem is LAN speed on virtual lan?

Virtual LAN is needed for MAC addresses if you want to use licences with DS Cam

(I have 4 LAN port (HW) ported to the VM, so I thought this might solve the problem but since I need specific MAC address this is a no/go)

 

QUESTION: I would really like to know how people use HD storage with a Xpenology virtual server?

Do you create one large terabyte vdisk2.qcow2 and mount this?

Or do you use a unassigned drive and mount that to the VM?

 

I would like to have:

DS Camera (Nice app low CPU usage) - have bought licenses for my old Synology

DS Photo/Moments

DS Backup tools/DS Cloud

DS Note

 

All have nice apps and low power requirements

 

UPDATE: Ok didnt know about the docker project... https://github.com/segator/xpenology-docker

But what's the advantages? from building your own VM?

Docker: Latest commit3e18362on Mar 8, 2019

 

 

Edited by casperse

Share this post


Link to post

So I went back experimenting with this in Unraid 6.8.3:

And I got the following results:

 

DS3615xs up to DSM_DS3615xs_25423_6.2.3 ! - Performance seem really good even LAN

DS3617xs I can only get to DSM_DS3617xs_23739_6.2.0 anything higher and it breaks?

 

If anyone have had better luck then please share 😏

Share this post


Link to post
Posted (edited)
On 4/20/2020 at 1:46 PM, casperse said:

So I went back experimenting with this in Unraid 6.8.3:

And I got the following results:

 

DS3615xs up to DSM_DS3615xs_25423_6.2.3 ! - Performance seem really good even LAN

DS3617xs I can only get to DSM_DS3617xs_23739_6.2.0 anything higher and it breaks?

 

If anyone have had better luck then please share 😏

Can you post your settings for 3615 6.2.3? I'm getting hard disk not found. I'm using 1.3b bootloader.

Edited by dariusz65

Share this post


Link to post
17 hours ago, dariusz65 said:

Can you post your settings for 3615 6.2.3? I'm getting hard disk not found. I'm using 1.3b bootloader.

Then you forgot to change the controller in the xml (Had the same problem when I started)

change hdd bus sata controller from 0 to 1

    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='writeback'/>
      <source file='/mnt/user/domains/XPEnology_3/vdisk2.img'/>
      <target dev='hdd' bus='sata'/>
      <address type='drive' controller='1' bus='0' target='0' unit='3'/>
    </disk>

 

Share this post


Link to post
Posted (edited)
18 hours ago, casperse said:

Then you forgot to change the controller in the xml (Had the same problem when I started)


change hdd bus sata controller from 0 to 1

    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='writeback'/>
      <source file='/mnt/user/domains/XPEnology_3/vdisk2.img'/>
      <target dev='hdd' bus='sata'/>
      <address type='drive' controller='1' bus='0' target='0' unit='3'/>
    </disk>

 

Thank you. It worked perfectly. One change I had to make was to replace e1000e with e1000. I was getting wrong transmission stats in Xpenology.  Thanks again for help. 

Edited by dariusz65

Share this post


Link to post

Now I need to figure out how to access my Unraid Shares from within Synology

Edited by Viper359

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.