Jump to content
Randall8686

Xpenology VM any one running this ?

111 posts in this topic Last Reply

Recommended Posts

27 minutes ago, eleazar said:

Hey guys, I'm trying to get my xpenology setup updated to 6.2.1, so I'm setting up a test VM before trying to update my live VM.  I'm struggling with being able to find it with synology assistant. I'm using CentOS template, the 1.03b for DS3617xs bootloader, changed mac to actual, and changed from virtio to e1000. 

 

I was thinking maybe I need to update the VID/PID/Serial/MAC info in the boot image.  I updated the serial and MAC without any issues, but I'm not really sure how to find the VID/PID for a virtual USB drive 😕 @AKPanda can you help me with the process you followed to get the VID/PID to use?

 

Also, did you guys settle on booting as "baremetal" with the loader, or do you choose the ESXI/VM option?

 

 

Just boot as VM and vid/pid makes no problems. I did not figure out how to get the vid for the virtual usb. Jf anybody knows please share. And also try 1.0.4. That worked for me

 

 

Edited by AKPanda

Share this post


Link to post
1 hour ago, AKPanda said:

Just boot as VM and vid/pid makes no problems. I did not figure out how to get the vid for the virtual usb. Jf anybody knows please share. And also try 1.0.4. That worked for me

 

 

Thank you for the quick response :)

 

Unfortunately it's still not working for me.  I've spent a few hours on this today, and I'm stuck at not being able to even find the VM with Synology Assistant (or find.synology.com)

 

I'll post the steps I followed below, could you let me know if I missed something?  I included my full XML below.

 

  • Use CentOS as the VM template
  • Use the 918+ 1.04b bootloader (i also tried the ds3617 1.03b bootloader, and the ds3615 1.03b, with no luck)
  • Change the ethernet model-type to e1000 in the VM XML
  • Update MAC address in the synoboot image to the MAC the VM assigned
  • Generate serial number, update it in the synoboot image (this only applied to the ds3617, since I couldn't find a generator for the 918, but i don't think that would stop it from even showing up on the network)
  • Boot using the VMare/ESXI option (I also tried the bare metal option)

 

I can't think of anything else to try at the moment, and would really appreciate any help :) 

 

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='18'>
  <name>Syno-6.2Test</name>
  <uuid>b94cda6c-xxxx-59e3-36ee-xxxxxxd30d10</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="CentOS" icon="centos.png" os="centos"/>
  </metadata>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
    <vcpupin vcpu='2' cpuset='2'/>
    <vcpupin vcpu='3' cpuset='3'/>
    <vcpupin vcpu='4' cpuset='4'/>
    <vcpupin vcpu='5' cpuset='5'/>
    <vcpupin vcpu='6' cpuset='6'/>
    <vcpupin vcpu='7' cpuset='7'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-q35-3.0'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/b94cda6c-xxxx-59e3-36ee-xxxxd30d10_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/isos/synoboot-ds918/synoboot.img'/>
      <backingStore/>
      <target dev='hdc' bus='usb'/>
      <boot order='1'/>
      <alias name='usb-disk2'/>
      <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/Syno-6.2Test/vdisk2.img'/>
      <backingStore/>
      <target dev='hdd' bus='sata'/>
      <alias name='sata0-0-3'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <alias name='usb'/>
      <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'>
      <alias name='usb'/>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <alias name='usb'/>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='sata' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'>
      <alias name='pcie.0'/>
    </controller>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <alias name='pci.1'/>
      <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'/>
      <alias name='pci.2'/>
      <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'/>
      <alias name='pci.3'/>
      <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'/>
      <alias name='pci.4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:5a:7b:f2'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='e1000'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/0'/>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/0'>
      <source path='/dev/pts/0'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-18-Syno-6.2Test/org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
      <address type='usb' bus='0' port='2'/>
    </input>
    <input type='mouse' bus='ps2'>
      <alias name='input1'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input2'/>
    </input>
    <graphics type='vnc' port='5900' autoport='yes' websocket='5700' 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'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+0:+100</label>
    <imagelabel>+0:+100</imagelabel>
  </seclabel>
</domain>

 

 

 

 

Share this post


Link to post
33 minutes ago, eleazar said:

Thank you for the quick response :)

 

Unfortunately it's still not working for me.  I've spent a few hours on this today, and I'm stuck at not being able to even find the VM with Synology Assistant (or find.synology.com)

 

I'll post the steps I followed below, could you let me know if I missed something?  I included my full XML below.

 

  • Use CentOS as the VM template
  • Use the 918+ 1.04b bootloader (i also tried the ds3617 1.03b bootloader, and the ds3615 1.03b, with no luck)
  • Change the ethernet model-type to e1000 in the VM XML
  • Update MAC address in the synoboot image to the MAC the VM assigned
  • Generate serial number, update it in the synoboot image (this only applied to the ds3617, since I couldn't find a generator for the 918, but i don't think that would stop it from even showing up on the network)
  • Boot using the VMare/ESXI option (I also tried the bare metal option)

 

I can't think of anything else to try at the moment, and would really appreciate any help :) 

 


<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='18'>
  <name>Syno-6.2Test</name>
  <uuid>b94cda6c-xxxx-59e3-36ee-xxxxxxd30d10</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="CentOS" icon="centos.png" os="centos"/>
  </metadata>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
    <vcpupin vcpu='2' cpuset='2'/>
    <vcpupin vcpu='3' cpuset='3'/>
    <vcpupin vcpu='4' cpuset='4'/>
    <vcpupin vcpu='5' cpuset='5'/>
    <vcpupin vcpu='6' cpuset='6'/>
    <vcpupin vcpu='7' cpuset='7'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-q35-3.0'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/b94cda6c-xxxx-59e3-36ee-xxxxd30d10_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/isos/synoboot-ds918/synoboot.img'/>
      <backingStore/>
      <target dev='hdc' bus='usb'/>
      <boot order='1'/>
      <alias name='usb-disk2'/>
      <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/Syno-6.2Test/vdisk2.img'/>
      <backingStore/>
      <target dev='hdd' bus='sata'/>
      <alias name='sata0-0-3'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <alias name='usb'/>
      <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'>
      <alias name='usb'/>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <alias name='usb'/>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='sata' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'>
      <alias name='pcie.0'/>
    </controller>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <alias name='pci.1'/>
      <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'/>
      <alias name='pci.2'/>
      <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'/>
      <alias name='pci.3'/>
      <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'/>
      <alias name='pci.4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:5a:7b:f2'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='e1000'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/0'/>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/0'>
      <source path='/dev/pts/0'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-18-Syno-6.2Test/org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
      <address type='usb' bus='0' port='2'/>
    </input>
    <input type='mouse' bus='ps2'>
      <alias name='input1'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input2'/>
    </input>
    <graphics type='vnc' port='5900' autoport='yes' websocket='5700' 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'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+0:+100</label>
    <imagelabel>+0:+100</imagelabel>
  </seclabel>
</domain>

 

 

 

 

Can you log into your router and see if it gets an ip address? Because at firs I couldnt find it with find.synology but I could access it directly on the ip

Share this post


Link to post
2 hours ago, AKPanda said:

Can you log into your router and see if it gets an ip address? Because at firs I couldnt find it with find.synology but I could access it directly on the ip

Unfortunately it's not showing up in the list of devices on the router. :( I'm not sure what else to try

Share this post


Link to post

Anyone got Jun's Loader v1.04b DS918+ working?
 

I can get 1.02b with ds3615xs working with the settings stated in the earlier threads but if I use the same settings for v1.04b, find Synology won't pick anything up and VM isn't picking up an IP from DHCP.

 

Thoughts?

 

Edit:  This information is really good to know... to figure if something may or may not work on your unraid server.

https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/

 

Another edit:  Been trying for the past few hours, been trying to install and this is what i found.

 

 - on my hardware, only loader ds3617 will actually boot and install. (e1000/seabios).  and only using dsm at version 6.2 only.  6.2.1 and won't finish install after the first reboot.

- i read and seems that ds3617 is more compatible. YMMV

- 6.2.1 and higher just won't work under unraid as far as i can tell. (they are now at 6.2.2 and i tired that with ds918 with no luck).  Even if i installed 6.2 and upgraded within, fails after first reboot.

 

 

Edited by bmac6996

Share this post


Link to post
11 hours ago, bmac6996 said:

Anyone got Jun's Loader v1.04b DS918+ working?
 

I can get 1.02b with ds3615xs working with the settings stated in the earlier threads but if I use the same settings for v1.04b, find Synology won't pick anything up and VM isn't picking up an IP from DHCP.

 

Thoughts?

 

Edit:  This information is really good to know... to figure if something may or may not work on your unraid server.

https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/

 

Another edit:  Been trying for the past few hours, been trying to install and this is what i found.

 

 - on my hardware, only loader ds3617 will actually boot and install. (e1000/seabios).  and only using dsm at version 6.2 only.  6.2.1 and won't finish install after the first reboot.

- i read and seems that ds3617 is more compatible. YMMV

- 6.2.1 and higher just won't work under unraid as far as i can tell. (they are now at 6.2.2 and i tired that with ds918 with no luck).  Even if i installed 6.2 and upgraded within, fails after first reboot.

 

 

It sounds like you're running into exactly what I ran into. :( I tried pretty much every combination and as soon as I attempted anything above 6.2.0, it failed.

 

I'm not sure how the other 2 people in this thread got 6.2.1 to boot successfully.

Share this post


Link to post

I have no idea how it works for me and not you that is why I posted my xml above. I just confirmed I am running DSM 6.2.1-23824 Update 4 and thinking of upgrading to Update 6 but after your problems I am very apprehensive. I will try and do a second install and document it step by step and see if I am doing anything differently. It might take me 3-4 days because of work. All that I can think of is that I have an original MAC and serial combo from another Synology box and started the bootloader as virtual

Edited by AKPanda

Share this post


Link to post
11 hours ago, bmac6996 said:

- 6.2.1 and higher just won't work under unraid as far as i can tell. (they are now at 6.2.2 and i tired that with ds918 with no luck).  Even if i installed 6.2 and upgraded within, fails after first reboot.

 

 

I just checked my install, I guess I was stuck on 6.1.7 Update 2.  I'll try getting 6.2 working with your setup now 😀

1 minute ago, AKPanda said:

I have no idea how it works for me and not you that is why I posted my xml above. I just confirmed I am running DSM 6.2.1-23824 Update 4 and thinking of upgrading to Update 6 but after your problems I am very apprehensive. I will try and do a second install and document it step by step and see if I am doing anything differently. It might take me 3-4 days because of work

That would be amazing! 😍 

Share this post


Link to post
3 hours ago, AKPanda said:

I have no idea how it works for me and not you that is why I posted my xml above. I just confirmed I am running DSM 6.2.1-23824 Update 4 and thinking of upgrading to Update 6 but after your problems I am very apprehensive. I will try and do a second install and document it step by step and see if I am doing anything differently. It might take me 3-4 days because of work. All that I can think of is that I have an original MAC and serial combo from another Synology box and started the bootloader as virtual

What bootloader version did you use? for which synology hardware device?  What DSM version did you originally install?  did you update to 6.2.1 update 4  and was at a lower version or were you already there when you originally installed it?

 

Having the original mac and serial combo could one of those X factors though.. can't rule it out.

 

I know 6.2.2 people are having issues, so i defin wouldn't jump to there.  

 

And it all could be hardware that we are using that could be when why some can get it working and some cannot. 


This is what i'm running.


M/B: Supermicro - X9SRH-7F/7TF
CPU: Intel® Xeon® CPU E5-2690 v2 @ 3.00GHz
Memory: 32 GB Multi-bit ECC 

 

 

Share this post


Link to post

My setup:

 

Dell r730 (Dell 599V5 Mobo)

CPU: Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz

Memory: 48 GB ECC DDR4

NIC (1): Integrated Broadcom Gigabit Ethernet BCM5720 (in use by Xpenology)

NIC (2): PCIe NetXtreme BCM5720 Gigabit Ethernet (not currently used with Xpenology)

Share this post


Link to post

 

20 hours ago, bmac6996 said:

 - on my hardware, only loader ds3617 will actually boot and install. (e1000/seabios).  and only using dsm at version 6.2 only.  6.2.1 and won't finish install after the first reboot.

- i read and seems that ds3617 is more compatible. YMMV

- 6.2.1 and higher just won't work under unraid as far as i can tell. (they are now at 6.2.2 and i tired that with ds918 with no luck).  Even if i installed 6.2 and upgraded within, fails after first reboot.

Quick update.  I tried your config: ds3617, e1000/seabios (i had never tried seabios before). 

 

I was able to successfully install and boot 6.2, but as soon as I attempt to install 6.2.1-23739, it never comes back online after the install.  So it looks like you and I are in the same boat.

Edited by eleazar

Share this post


Link to post

Update:

Was able to install 6.2.2-24922 DSM as a VM.

 

This is what I did:

 

- Used bootloader 1.03b.

- Used DS3615

- Installed DMS version 6.2.2-24922 (also tried DSM 6.2.1-23824 Update 6 and that worked too!)

- Created VM as "CentOS".  Used Seabios and highest version of machine (Q35-3.0)

- After I configured the bootloader, I loaded the img as the first bootable primary vdisk first but set the type to "USB".   (doing it this way, as "usb", DSM won't see the bootloader image file as a hard drive and will show only your other vdisks attached)

- I created a vdisk, and used qcow (other type could be used, but I didn't try).  Must be at least 5gb I found.  (anything less it won't see and/or will fail during setup)

- The main part!!  --  manually go into the XML and change the nic to "e1000e".

 

This worked for me on my Supermicro - X9SRH-7F E5-2690 v2.

YMMV.

 

Good luck.

  • Like 4
  • Thanks 1

Share this post


Link to post

 

Hi Guys,

Has anyone succeeded in going through a real hard drive or SATA controller? I'm stuck here, it does not boot anymore with passthrough disks, I'm stuck in the Seabios boot screen with the Passthrottle controller, Did anyone get lucky to boot in UEFI mode?

Many Thanks

best regards

ps: sorry for my bad english

pps: how can i connect to the serial port to see the kernel 

Edited by DaCapone

Share this post


Link to post

update

 

 Got it WORKING

DS3615 1.03b bootloader with passtrough hdd

my XML ;-) 

 

 

attention !!! when you edit your VM in unraid not in XML , unraid will overwrite your network config to virtio, this took me days to find out

make your changes save then edit agoin in xml cahnge network to e1000e and save again ;-)

 

 

 

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='14'>
  <name>Xpenology DS3615xs</name>
  <uuid>bdc56586-9082-7c17-c38d-587d5ef54241</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="CentOS" icon="centos.png" os="centos"/>
  </metadata>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='8'/>
    <vcpupin vcpu='1' cpuset='20'/>
    <vcpupin vcpu='2' cpuset='9'/>
    <vcpupin vcpu='3' cpuset='21'/>
    <vcpupin vcpu='4' cpuset='10'/>
    <vcpupin vcpu='5' cpuset='22'/>
    <vcpupin vcpu='6' cpuset='11'/>
    <vcpupin vcpu='7' cpuset='23'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-q35-3.1'>hvm</type>
  </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/disk1/appdata/Xpenology-3615/synoboot.img'/>
      <backingStore/>
      <target dev='hdc' bus='usb'/>
      <boot order='1'/>
      <alias name='usb-disk2'/>
      <address type='usb' bus='0' port='1'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-SanDisk_SDSSDHII240G_143456400657'/>
      <backingStore/>
      <target dev='hdd' bus='sata'/>
      <alias name='sata0-0-3'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-SanDisk_SDSSDHII240G_143738401622'/>
      <backingStore/>
      <target dev='hde' bus='sata'/>
      <alias name='sata0-0-4'/>
      <address type='drive' controller='0' bus='0' target='0' unit='4'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-ST8000AS0002-1NA17Z_Z8407M9X'/>
      <backingStore/>
      <target dev='hdf' bus='sata'/>
      <alias name='sata0-0-5'/>
      <address type='drive' controller='0' bus='0' target='0' unit='5'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-ST8000AS0002-1NA17Z_Z8407MA9'/>
      <backingStore/>
      <target dev='hdg' bus='sata'/>
      <alias name='sata1-0-0'/>
      <address type='drive' controller='1' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-WDC_WD4000FYYZ-01UL1B1_WD-WMC130329424'/>
      <backingStore/>
      <target dev='hdh' bus='sata'/>
      <alias name='sata1-0-1'/>
      <address type='drive' controller='1' 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-WDC_WD4000FYYZ-01UL1B1_WD-WMC130360256'/>
      <backingStore/>
      <target dev='hdi' bus='sata'/>
      <alias name='sata1-0-2'/>
      <address type='drive' controller='1' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-WDC_WD4000FYYZ-01UL1B1_WD-WMC130363477'/>
      <backingStore/>
      <target dev='hdj' bus='sata'/>
      <alias name='sata1-0-3'/>
      <address type='drive' controller='1' bus='0' target='0' unit='3'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <alias name='usb'/>
      <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'>
      <alias name='usb'/>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <alias name='usb'/>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'>
      <alias name='pcie.0'/>
    </controller>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <alias name='pci.1'/>
      <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'/>
      <alias name='pci.2'/>
      <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'/>
      <alias name='pci.3'/>
      <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'/>
      <alias name='pci.4'/>
      <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'/>
      <alias name='pci.5'/>
      <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'/>
      <alias name='pci.6'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='sata' index='1'>
      <alias name='sata1'/>
      <address type='pci' domain='0x0000' bus='0x06' slot='0x01' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:64:43:85'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='e1000e'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/0'/>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/0'>
      <source path='/dev/pts/0'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-14-Xpenology DS3615xs/org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
      <address type='usb' bus='0' port='2'/>
    </input>
    <input type='mouse' bus='ps2'>
      <alias name='input1'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input2'/>
    </input>
    <graphics type='vnc' port='5900' autoport='yes' websocket='5700' 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'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+0:+100</label>
    <imagelabel>+0:+100</imagelabel>
  </seclabel>
</domain>
 

 

 

Share this post


Link to post
On 5/6/2019 at 11:48 PM, bmac6996 said:

Update:

Was able to install 6.2.2-24922 DSM as a VM.

 

This is what I did:

 

- Used bootloader 1.03b.

- Used DS3615

- Installed DMS version 6.2.2-24922 (also tried DSM 6.2.1-23824 Update 6 and that worked too!)

- Created VM as "CentOS".  Used Seabios and highest version of machine (Q35-3.0)

- After I configured the bootloader, I loaded the img as the first bootable primary vdisk first but set the type to "USB".   (doing it this way, as "usb", DSM won't see the bootloader image file as a hard drive and will show only your other vdisks attached)

- I created a vdisk, and used qcow (other type could be used, but I didn't try).  Must be at least 5gb I found.  (anything less it won't see and/or will fail during setup)

- The main part!!  --  manually go into the XML and change the nic to "e1000e".

 

This worked for me on my Supermicro - X9SRH-7F E5-2690 v2.

YMMV.

 

Good luck.

 

Did the above and can confirm that it works. For me at least. 

 

Capture.PNG.3ab9c9f0ddcca3a7bf455f07c6b59927.PNG

 

I too am rocking af supermicro. My board is a X9DAL though with dual E5-2418L Xeons

I've been trying before without luck. Not with the newest version though.

But it is the first time i've tried to set the NIC as "e1000e" and not just "e1000".

If that made the differance or not, I don't know. But if works now for sure. 

Thanks for the pointer

Share this post


Link to post

Just did the same as above on a i7-3770 on a ASRock Z77 Pro4-M today, and following the same procedure I got the same result. 
Works flawlessly. Thx again for the pointer.

Capture.PNG.3b8274b42b237a0598fe4016d141ee8e.PNG

 

I don't know why it says it's an i3-4130, but it works, and that's what matters :) 

Capture2.PNG.f8ce3ecf1d6f3ac4016f756fa60d67db.PNG

Edited by Baskedk

Share this post


Link to post
On 5/7/2019 at 5:48 AM, bmac6996 said:

Update:

Was able to install 6.2.2-24922 DSM as a VM.

 

This is what I did:

 

- Used bootloader 1.03b.

- Used DS3615

- Installed DMS version 6.2.2-24922 (also tried DSM 6.2.1-23824 Update 6 and that worked too!)

- Created VM as "CentOS".  Used Seabios and highest version of machine (Q35-3.0)

- After I configured the bootloader, I loaded the img as the first bootable primary vdisk first but set the type to "USB".   (doing it this way, as "usb", DSM won't see the bootloader image file as a hard drive and will show only your other vdisks attached)

- I created a vdisk, and used qcow (other type could be used, but I didn't try).  Must be at least 5gb I found.  (anything less it won't see and/or will fail during setup)

- The main part!!  --  manually go into the XML and change the nic to "e1000e".

 

This worked for me on my Supermicro - X9SRH-7F E5-2690 v2.

YMMV.

  

Good luck.

Awesome!

 

Have you tried these steps but with the ds3617xs image?

Edited by C-Fu

Share this post


Link to post

Thanks @bmac6996, I owe you a beer!

On 5/6/2019 at 4:48 PM, bmac6996 said:

Update:

Was able to install 6.2.2-24922 DSM as a VM.

 

This is what I did:

 

- Used bootloader 1.03b.

- Used DS3615

- Installed DMS version 6.2.2-24922 (also tried DSM 6.2.1-23824 Update 6 and that worked too!)

- Created VM as "CentOS".  Used Seabios and highest version of machine (Q35-3.0)

- After I configured the bootloader, I loaded the img as the first bootable primary vdisk first but set the type to "USB".   (doing it this way, as "usb", DSM won't see the bootloader image file as a hard drive and will show only your other vdisks attached)

- I created a vdisk, and used qcow (other type could be used, but I didn't try).  Must be at least 5gb I found.  (anything less it won't see and/or will fail during setup)

- The main part!!  --  manually go into the XML and change the nic to "e1000e".

 

This worked for me on my Supermicro - X9SRH-7F E5-2690 v2.

YMMV.

 

Good luck.

Share this post


Link to post

Came across this thread so I thought I’d give it whirl. Used the instructions as posted by @bmac6996 and it worked right out of the box. To clarify, and my experience

  • Download bootloader v1.03b for DS3615xs, extract synoboot.img
  • Add VM -> CentOS
    • BIOS: SeaBIOS
    • Machine: Q35 (3.1 is the latest as of this post)
  • Primary vDisk: point to synoboot.img extracted earlier
    • Primary vDisk Bus: USB
  • 2nd (and additional) vDisk Location: I created a 10G vDisk, Type: qcow2. Someone earlier in the thread passed-through their disks
    • 2nd vDisk Bus: SATA
  • UN-select the ’Start VM after creation’ box at the bottom, then Create.
  • Edit VM in XML View
    • Find <model type=‘virtio’/> and change 'virtio' to 'e1000e'
  • Save and start the VM. If you view VNC it will show the bootloader screen
  • Took about a minute but DiskStation appeared in find.synology.com

From here in out I followed the Synology onscreen installation instructions. It downloaded everything it needed from Synology servers. When I went looking for the bootloader, there was mention of PAF files, etc. I didn't need any of that since it all downloaded automatically.

 

I skipped the link Synology account - QuickConnect part. Not sure if you need to generate a unique serial, but since I’m just playing around I didn’t bother

 

Again, read though the post by @bmac6996. He explained the reasons behind the choices

Share this post


Link to post

I did get this working. I use 10G nics in unraid. I am using e1000e as the nic driver but the speeds are very slow and I cannot seem to connect to the internet from the Xpenology VM.

Share this post


Link to post
1 hour ago, xkraz said:

I did get this working. I use 10G nics in unraid. I am using e1000e as the nic driver but the speeds are very slow and I cannot seem to connect to the internet from the Xpenology VM.

If you can download packages you have internet.

 

You will get a connection error if you try to login to Synology or use certain features like Quickconnect. You need to generate a working serial number to enable them.

Share this post


Link to post
33 minutes ago, positronicP said:

If you can download packages you have internet.

 

You will get a connection error if you try to login to Synology or use certain features like Quickconnect. You need to generate a working serial number to enable them.

I can connect to the VM but I do not have internet. Also, when I try copying a file from the VM, it's really really slow. Where do I put the serial for the VM?

Share this post


Link to post

Been playing around for days and got it working on Unraid VM Xpenology.
DSM 6.2.2, 3615xs 24922 (latest), 1.03b Jun's loader


Step-by-step guide working for me:
Create VM use CENTOS
First scroll down make sure it's set to br0
Either copy MAC and edit synoboot.img , or edit MAC / SN after generation use OSFmount
set time-out in synoboot.img to 10 secs
Copy edited synoboot.img to wanted location and set permissions to 7777
Host Passtrough (i'm on i3-6100)
Choose initial memory
Set machine as Q35-3.0
Use SeaBIOS
Primary vDisk Location eg /mnt/cache/xpenology/synoboot.img (use USB, manual)
2nd vDisk location either /dev/sd*** or create Manual eg /mnt/cache/xpenology/vdisk.img (use SATA, enough gb-space, qcow2)

deselect start VM after creation and click apply
edit created VM, right top corner to XML view
change br0 model type from VIRTIO to e1000e
change hdd bus sata controller from 0 to 1
update and back out to main VM page Unraid
start VM, right after start go to VNC remote
Since you changed timeout to 10 you will now be able to select the bottom line of the loader from 1st option Baremetal to 3rd option VMware
I know you can change default option in synoboot to VMware as well but it might occur your's will only work on Baremetal, this way you don't have to re-edit your'e synoboot.img again...
done and good luck :) , let me know if this worked out for you !

Gr, Marc


 

Edited by Magnetio
Forgot to mention USB for Primary vDisk Location

Share this post


Link to post
2 hours ago, Magnetio said:

Either copy MAC and edit synoboot.img , or edit MAC / SN after generation use OSFmount

Are you able to login to Synology and use Quickconnect?

Share this post


Link to post
On 10/17/2019 at 4:07 AM, positronicP said:

Are you able to login to Synology and use Quickconnect?

Sorry for the late reply, notifications were turned off

Didn't try but from what I have been reading regarding Quickconnect it only worked for some first DSM 6.x versions.
Also original MAC / SN needed to be emulated and only working till certain DSM version.
Last 2 lines not sure though. This is what I remember to have read a few weeks ago on various other forums!

I use my own domain-name pointed directed to Unraid with reverse proxy to dockers and xpeno VM.
Any specific reason you need the Quickconnect to work?

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...

 

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.