Jump to content
Randall8686

Xpenology VM any one running this ?

111 posts in this topic Last Reply

Recommended Posts

Can the DSM update from inside the gui? When I got it running some time ago it worked until I tried to update it and in the end gave up using it. 

Share this post


Link to post
1 minute ago, DGB said:

Can the DSM update from inside the gui? When I got it running some time ago it worked until I tried to update it and in the end gave up using it. 

It depends on what version you were updating to.  As far as I know, there is no way to run 6.2 right now (I haven't researched it for a while, so I could be wrong).  So if you updated to 6.2, it would break your install and you wouldn't be able to boot anymore.

 

I haven't tried updating yet, but I believe you should be able to install small updates and hot fixes.  

 

You should always check the xpenology forums before installing updates.  They have an entire subforum for update compatibility with the current loaders.

Share this post


Link to post

Just a quick note.  I was able to successfully update to DSM 6.1.7-15284 Update 2.

 

Do not install DSM 6.2.  To my knowledge, there is no way to run 6.2 currently.

Share this post


Link to post
34 minutes ago, eleazar said:

Just a quick note.  I was able to successfully update to DSM 6.1.7-15284 Update 2.

 

Do not install DSM 6.2.  To my knowledge, there is no way to run 6.2 currently.

Thanks for the update I would need to try this again. 

Share this post


Link to post

Has anyone got this working recently? I can get the vm to boot using jun's loader, but it doesn't seem to connect to the network (I've tried e1000 and e1000e as model type).

Share this post


Link to post
12 minutes ago, PlayerOne said:

Has anyone got this working recently? I can get the vm to boot using jun's loader, but it doesn't seem to connect to the network (I've tried e1000 and e1000e as model type).

I'm still running 6.1.7-15284 Update 2 without any problems.  I also installed this for a friend within unRAID recently as well, without any problems.  all i do is change the model from virtio to e1000. Just fyi, if you make the change to the xml, but then at any point later you switch back to basic view to make other changes, the e1000 change will be lost every time.  You have to make your "basic" changes, save it, then go in and edit the xml to change it back to e1000.

Share this post


Link to post
1 minute ago, eleazar said:

I'm still running 6.1.7-15284 Update 2 without any problems.  I also installed this for a friend within unRAID recently as well, without any problems.  all i do is change the model from virtio to e1000. Just fyi, if you make the change to the xml, but then at any point later you switch back to basic view to make other changes, the e1000 change will be lost every time.  You have to make your "basic" changes, save it, then go in and edit the xml to change it back to e1000.

Oh cool. Please could share your xml for the vm and which files you are using where. It's driving me a bit crazy today! I just thought, did you use a centOS pattern for the vm?

 

Share this post


Link to post

Hey, first of all HAPPY NEW YEAR TO ALL

I got the VM setup right as the synology boots up and I can see it on the network. But when I try to install the DSM it formats the drive with no problem but it says the file is corrupt Error 13. I tried downloading the DSM manually and the same thing happens. This used to be a problem when you had the wrong PID and VID for the USB drive. I mounted the synoboot.img as a vDisk USB and second manual vDisk for the main drive. But I cannot figure out how to find the PID/VID for the virtual USB I am mounting to UNRAID. 

Share this post


Link to post
On 1/1/2019 at 2:54 AM, AKPanda said:

Hey, first of all HAPPY NEW YEAR TO ALL

I got the VM setup right as the synology boots up and I can see it on the network. But when I try to install the DSM it formats the drive with no problem but it says the file is corrupt Error 13. I tried downloading the DSM manually and the same thing happens. This used to be a problem when you had the wrong PID and VID for the USB drive. I mounted the synoboot.img as a vDisk USB and second manual vDisk for the main drive. But I cannot figure out how to find the PID/VID for the virtual USB I am mounting to UNRAID. 

I've not encountered Error 13, but I just want to confirm, you're not trying to install a version higher than 6.1.7-15284, right?  You definitely cannot let DSM update itself, or install the latest version, that will always fail, since the bootloader only supports up to 6.1.7-15284.

Share this post


Link to post
11 hours ago, eleazar said:

I've not encountered Error 13, but I just want to confirm, you're not trying to install a version higher than 6.1.7-15284, right?  You definitely cannot let DSM update itself, or install the latest version, that will always fail, since the bootloader only supports up to 6.1.7-15284.

I found my mistake. I had chosen linux instead of centOS for my VM. As soon as I changed this set the ethernet card to e1000 and disk to SATA everything works perfectly. And I am running the latest 6.2.1 23824 update 4 with no problems

 

Share this post


Link to post

I've managed to get the "device" detected in the find.synology.com and it gets IP and so on. No problems there.
But i can not get it to find a HDD in any way, shape or form! It's driving me nuts! I've used hours on this with different locations, sizes, formats and interfaces. It will not show up at all! 
 

    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/disk1/vdisks/XPEnology/vdisk2.img'/>
      <target dev='hdd' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>

Does anyone have any pointers that i am missing out on? Is there something that have to be written to the Synoboot.img ? 
Any pointers is very appreciated !

Share this post


Link to post
On 1/21/2019 at 12:01 AM, AKPanda said:

Stuck on the same step as Baskedk. Everything else working perfect

Well, I got around this now.
After even more trial and error since last time writing here, I skipped trying to get 1.04b loader to work even though i got that far.

I found out that I could get it to recognize the virtual HDD if i used the 1.03b loader instead.

But ONLY if i used the ds3617xs version.

ds3615xs did not work for me at all. Could'n get it to be found on the network.

DS3617xs could though. 

 

So after booting up on loader 1.03b with version ds3617xs and ofc renamed the NIC interface to 'e1000' in the XML editor. 

I got to the part where I should set it up.

At 1st I tried to install automaticly from the synology site with the latest patch/firmware (DSM 6.2.1 version 23824).
This ended up not booting anymore. So that obviously did'n work. 

 

Then I tried installing the previously version (version 6.2 23739) and that booted. 
As of now, I am stuck there when it comes to updates, but it's booting and working. and imo it's a pretty nice enhancement to unRAID to have DSM on top.
I even only allocated 512mb ram to it and there is no problem what so ever.

 

Hope you get it working

 

btw, I found it not to get online if I booted it as VMWARE mode or what it is called. I got it working via the BAREMETAL option.

I uploaded my synoboot.img to MEGA without my serial and mac address in it. if you want to try if it works for you. 
If you need to get a serial for it, use this link: Serial Generator for XPEnology
If you need the .pat file i used, use this link: DS3617XS version 23739 DSM 6.2
If you want my Synoboot.img use this link: synoboot.img file 1.03b for DS3617xs

 

Share this post


Link to post

HEY,

great news. I got the xpenology to recognize the second vdisk. In the xml just change the sata controller number from 0 to 1 and VOILA. So I got the latest DSM with 916+ loader 1.04b and everything working perfectly.

<disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/Surveillance/DSMData.img'/>
      <backingStore/>
      <target dev='hde' bus='sata'/>
      <alias name='sata1-0-4'/>
      <address type='drive' controller='1' bus='0' target='0' unit='4'/>

On the last line change controller from 0 to 1 and it should work

Share this post


Link to post
1 hour ago, AKPanda said:

HEY,

great news. I got the xpenology to recognize the second vdisk. In the xml just change the sata controller number from 0 to 1 and VOILA. So I got the latest DSM with 916+ loader 1.04b and everything working perfectly.


<disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/Surveillance/DSMData.img'/>
      <backingStore/>
      <target dev='hde' bus='sata'/>
      <alias name='sata1-0-4'/>
      <address type='drive' controller='1' bus='0' target='0' unit='4'/>

On the last line change controller from 0 to 1 and it should work

I assume you are reffering to ds918+ since I can't seem to find a 1.04b loader for 916+ but there is one for 918+.

But i can't even get this one to show up on the network. What have you done for it to be discovered on the network? NIC interface e1000 ? What bios? Seabios or OMVF?, Machine: Q35-2.9? What is your settings?

Share this post


Link to post
3 minutes ago, Baskedk said:

I assume you are reffering to ds918+ since I can't seem to find a 1.04b loader for 916+ but there is one for 918+.

But i can't even get this one to show up on the network. What have you done for it to be discovered on the network? NIC interface e1000 ? What bios? Seabios or OMVF?, Machine: Q35-2.9? What is your settings?

Here is my full xml. Hope it helps

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='10'>
  <name>Xpenology</name>
  <uuid>xxx-xxx-9xx-xxxc-8dxxxxxx2a9e</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'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='1'/>
    <vcpupin vcpu='1' cpuset='5'/>
    <vcpupin vcpu='2' cpuset='3'/>
    <vcpupin vcpu='3' cpuset='7'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <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='2' 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'/>
      <backingStore/>
      <target dev='hdc' bus='sata'/>
      <boot order='1'/>
      <alias name='sata0-0-2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/appdata/Xpenology/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>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/Surv/DSMData.img'/>
      <backingStore/>
      <target dev='hde' bus='sata'/>
      <alias name='sata1-0-4'/>
      <address type='drive' controller='1' bus='0' target='0' unit='4'/>
    </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>
    <controller type='sata' index='1'>
      <alias name='sata1'/>
      <address type='pci' domain='0x0000' bus='0x06' slot='0x01' function='0x0'/>
    </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='0x05' slot='0x00' function='0x0'/>
    </controller>
    <filesystem type='mount' accessmode='passthrough'>
      <source dir='/mnt/user/Sur'/>
      <target dir='Sur'/>
      <alias name='fs0'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </filesystem>
    <interface type='bridge'>
      <mac address='00:xx:xx:xx:xx:xx'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='e1000'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x04' 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-10-Xpenology/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='1'/>
    </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>

And yes I meant 918+. 

Share this post


Link to post

Nope. I've replicated everything you have in your XML to the extend possible.

Still no luck.
Could you maybe upload your synoboot.img file for me to DL? without the MAC ofc. 
Btw, for the ds918+, where do you get a serial for that?

I can only find a generator for ds3615xs, ds3617xs and ds916+. Not ds918+
Is it not needed for that one? Or how does that work?

 

And why do you need to have 2 extra hdd's in your setup?

Why not just the boot disk (synoboot.img) and a storage disk? Just curious 

Edited by Baskedk

Share this post


Link to post

@AKPanda,

 

how do you access the 'Sur' folder inside xpenology?

 

Quote

 <filesystem type='mount' accessmode='passthrough'>
      <source dir='/mnt/user/Sur'/>
      <target dir='Sur'/>
      <alias name='fs0'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>

 

I added a Unraid Share mount in my xml, but cant see the folder inside XPEnology. how did you do it?

 

Share this post


Link to post
On 1/21/2019 at 4:43 AM, Baskedk said:

I've managed to get the "device" detected in the find.synology.com and it gets IP and so on. No problems there.
But i can not get it to find a HDD in any way, shape or form! It's driving me nuts! I've used hours on this with different locations, sizes, formats and interfaces. It will not show up at all! 
 


    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/disk1/vdisks/XPEnology/vdisk2.img'/>
      <target dev='hdd' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>

Does anyone have any pointers that i am missing out on? Is there something that have to be written to the Synoboot.img ? 
Any pointers is very appreciated !

did you just add vdisk2.img in the xml?

You will need to physically create the img file. i did that by specifying '2nd Vdisk Location' in the 'Form View'.

When that's done, save and edit again in xml mode to change the 'e1000'.

 

hope this helps, I was stuck at the same step as you...

 

I got xpenology running fine now, but it can't see the Unraid Mount Tag. I can't see the Unraid shares from the xpenology.

Can someone help?

have been playing with mount and fstab... but couldnt get it to work

Share this post


Link to post
On 1/28/2019 at 11:36 AM, Dexmorgan said:

did you just add vdisk2.img in the xml?

You will need to physically create the img file. i did that by specifying '2nd Vdisk Location' in the 'Form View'.

When that's done, save and edit again in xml mode to change the 'e1000'.

 

hope this helps, I was stuck at the same step as you...

 

I got xpenology running fine now, but it can't see the Unraid Mount Tag. I can't see the Unraid shares from the xpenology.

Can someone help?

have been playing with mount and fstab... but couldnt get it to work

I did create the disk 1st. And i have the system running now on loader 1.03b, I just could'n get it to discover the disk on the 1.04b loader. It booted and all. It just did'n discover the 2nd disk somehow. But as said, on the 1.03b it works fine.

I guess it might come down to what hardware ppl are using i guess. unRAID is unraid, but XPEnology can be quite picky on hardware, and maybe that is what screws ppl over in this setup. What works for some, might not work for others.

 

But when it comes to accessing unRAID resources from within DSM you can set up NFS/CIFS shares on unRAID and setup remote folder sharing in FileStation and add the shares there. And then you have a bridge between the two systems. 
It's not paticular fast transfer rates, but it works. It is a virtual environment after all.

Share this post


Link to post
On 1/27/2019 at 10:34 AM, Dexmorgan said:

@AKPanda,

 

how do you access the 'Sur' folder inside xpenology?

 

 

I added a Unraid Share mount in my xml, but cant see the folder inside XPEnology. how did you do it?

 

First of all sorry for the late reply. That was left in my xml from trying to add a share but adding shares directly to Xpenology is not working for me either. 

Share this post


Link to post
On 1/25/2019 at 12:09 PM, Baskedk said:

Nope. I've replicated everything you have in your XML to the extend possible.

Still no luck.
Could you maybe upload your synoboot.img file for me to DL? without the MAC ofc. 
Btw, for the ds918+, where do you get a serial for that?

I can only find a generator for ds3615xs, ds3617xs and ds916+. Not ds918+
Is it not needed for that one? Or how does that work?

 

And why do you need to have 2 extra hdd's in your setup?

Why not just the boot disk (synoboot.img) and a storage disk? Just curious 

Well when I was setting it up I added the boot img and a storage img that was too small. Then when it worked ( which suprised me :D ) I had the choice to expand the original disk or add a new one. That is how the 100GB vdisk2 was born. As for the serials, people get inventive :D. I had an old Synology box and used that serial and mac. But as you will not use the services with the synology account I believe you can use the generators. And my synoboot.img is the original one without any modifications except VID, PID, serial and MAC adress changed.

Edited by AKPanda

Share this post


Link to post
On 2/5/2019 at 3:32 AM, AKPanda said:

 And my synoboot.img is the original one without any modifications except VID, PID, serial and MAC adress changed.

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?

 

 

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.