casperse Posted January 2, 2020 Share #1 Posted January 2, 2020 Hi All I finally got the VM working (Unraid forum) my question is to the installation on a virtual VM and the VID & PID Information: I am using the loader: synoboot-ds918_1.04b And the DSM: DSM_DS918+_23824_(6.2.1).pat I have updated the Mac & license generated So after "find.synology.com" and the installation I keep getting the: Since this is a virtual USB I dont have a VID & PID Anyone else who have had this problem? To other Unraid users the post for setting this up is located here: https://forums.unraid.net/topic/71316-xpenology-vm-any-one-running-this/ Best regards & a happy New year! Casperse Quote Link to comment Share on other sites More sharing options...
IG-88 Posted January 2, 2020 Share #2 Posted January 2, 2020 does that help? https://xpenology.com/forum/topic/19925-9th-gen-intel-cpu/?do=findComment&comment=119001 Quote Link to comment Share on other sites More sharing options...
casperse Posted January 2, 2020 Author Share #3 Posted January 2, 2020 @IG-88 Thanks I needed to verify my settings and I can confirm it works with DS3615xs 6.1 Jun's Mod V1.02b.img I installed the DSM_DS3615xs_15047_6.1_15047 and updated inside DSM to DSM_DS3615xs_15284_6.1.7_15284.pat But any attempt to use the new loader to get to 6.2 give above error every time... I just tried with 918+ starting with DSM_DS918+_23739_6.2_23739.pat and got the again.... Quote Link to comment Share on other sites More sharing options...
IG-88 Posted January 2, 2020 Share #4 Posted January 2, 2020 unraid seems to use qemu if you google for qemu set vid pid you will find things like https://lists.gnu.org/archive/html/qemu-discuss/2015-07/msg00072.html so you should be able to set the vid/pid to the values you already have in the grub.cfg or you can set anything you want and then set the same in grub.cfg Quote Link to comment Share on other sites More sharing options...
casperse Posted January 2, 2020 Author Share #5 Posted January 2, 2020 That's very interesting would have to read up on that But at least for loaders before 6.2 it doesn't matter what VID and PID are set to, it just works I don't know how to get the VID PID from a virtual USB in Unraid, in windows it easy.... I think it's something to do with the network "e1000e" or "e1000" tried both same result, also changed controller bus for vdisk and usb no difference Something has changed in the new loader that require different settings? Quote Link to comment Share on other sites More sharing options...
casperse Posted January 2, 2020 Author Share #6 Posted January 2, 2020 Stupid me! Seems you need to alter the time out to 10s in order to select the VM option in the loader.... I didn't know it just auto selected the first line before I opened the VNC! 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 Quote 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 Quote 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 Quote 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 Quote Link to comment Share on other sites More sharing options...
khile Posted January 24, 2020 Share #7 Posted January 24, 2020 would you be able to share your XML file as i cant get 6.2 to show up on unraid 6.8.1 no matter what i do using loader 1.04b and selecting vm option never appears on network Quote Link to comment Share on other sites More sharing options...
casperse Posted January 27, 2020 Author Share #8 Posted January 27, 2020 I used the one in the link above, works! Quote Link to comment Share on other sites More sharing options...
csuno Posted April 8, 2020 Share #9 Posted April 8, 2020 Hope you can help me... i have two Workstations with UNRAID (both 6.8.3) running. my first rig loads the xpenology whithout any problems... (changes nic from virtio to e1000, nothing else) Intel® Core™ i7-7700K, Gigabyte Z270-HD3P-CF On a second rig, i dont get a network connection, it doesnt get an IP from DHCP and i cant find with SynoAssistant or find.synology.com Intel® Xeon® CPU E3-1220 V2, D3034-B1 So, with same VM XML, same Loader (for DS918+) - v1.04b, 🤨 Even when i try to pass through a pcie nic, it doesnt see my LAN!? Does anyone have a advice? Quote Link to comment Share on other sites More sharing options...
User913849149 Posted July 3, 2020 Share #10 Posted July 3, 2020 On 4/8/2020 at 10:46 PM, csuno said: Hope you can help me... i have two Workstations with UNRAID (both 6.8.3) running. my first rig loads the xpenology whithout any problems... (changes nic from virtio to e1000, nothing else) Intel® Core™ i7-7700K, Gigabyte Z270-HD3P-CF On a second rig, i dont get a network connection, it doesnt get an IP from DHCP and i cant find with SynoAssistant or find.synology.com Intel® Xeon® CPU E3-1220 V2, D3034-B1 So, with same VM XML, same Loader (for DS918+) - v1.04b, 🤨 Even when i try to pass through a pcie nic, it doesnt see my LAN!? Does anyone have a advice? Also got problems getting recongnized in LAN. After I switched from DS918+ to DS3615 synoboot.img (v1.03b) it worked fine. Quote Link to comment Share on other sites More sharing options...
LittleLama Posted February 21, 2021 Share #11 Posted February 21, 2021 (edited) Hi ! Thank you all for this amazing thread. Thank you caperse for the tips, and thank you again IG-88 for your science of xpenology and your time spent to help in so many threads. Big up for you two. I was able to start a VM with DSM 6.2.3 on it. First step : customize the bootload. Download the 1.04b jun's bootloader for DS918+ (at bottom of this thread you'll find a link to virtio bootloader, you can give it a try) Grab a bloc note and chose : - a virtual mac adress (create it) - a serial number https://xpenogen.github.io/serial_generator/index.html Mount the bootloader.img with OSFMount, partition 0, readable (unselect read only). Edit in grub directory the grub file with your favorite text editor. Change MAC, SN, and at the end, where there is the menu (Baremetal, ...) add # at the begin of each line except the last option "ESXI" like this : Citation #menuentry "DS918+ 6.2.1/6.2 Baremetal $VERSION" --class os { # set img= # savedefault # loadlinux 918 usb # loadinitrd # showtips #} #menuentry "DS918+ 6.2.1/6.2 Baremetal $VERSION Reinstall" --class os { # set img= # loadlinux 918 usb mfg # loadinitrd # showtips #} menuentry "DS918+ 6.2.1/6.2 VMWare/ESXI $VERSION" --class os { set img= savedefault loadlinux 918 sata loadinitrd showtips } Save, unmount and upload it to your server. Second step : create the VM It's far inspired from the ESXI tutorial. Create a CentOS VM Give it as CPUs and memory you want Select Machine Q35-3.0 BIOS : SeaBIOS USB Controller : 2.0 EHCI OS Install : None Primary vDisk Location : - Manual : choose the bootloader you uploaded just before - Type qcow - You have to select the bus SATA, not USB (because USB need to have VID and PID, baremetal option, and we dont know how to set them). Secondary vDisk Location : - Manual, chose a place and a size (20G, 50G, 500G as you want). Just remember that you won't be able to mount host shares by NFS protocol to crypted shared folder, and that P9/virtio mounting is not installed in this bootloader so chose a a good size, but you will be able to add somes after. So just measure a size for OS, Apps, and some data on it. This step will create the vdisk img file (what you can't do by writing directly the XML). You can either place it to a /mnt/disk#/ to avoid caching it. - SATA of course Unraid share : use like you want, I didn't found how to use it at this time ......... Network mac : the mac adress you created at first step Network bridge : br0 (I think this is mandatory, you can try other options). SAVE WITHOUT RUNNING. Third step : magic options Edit the VM, and switch to XML options. Search inside the devices tag, the second disk and change in adress tag the controller value to 1 Go to interface tag and change model to e1000e SAVE and RUN !! GERONIMOOOOO ! Install DSM Go to find.synology.com and begin install Go download manually the dsm 6.2.3 for 918+ Few minutes later, your xpenology is up. Suggestions and issues Watch your cache, move your vdisk to a disk if its too big or you will have problems ! I did a chmod 7777 to the place where the vdisk is stored. That can fix some format failures at DSM installation. If you have suggestions to mount host shares into DSM another way than NFS, feel free to share I didn't succeed to make a thing of the unraid share. I didn't either succeed in adding a second share, or to passthrough a usb drive. Maybe trying to use virtio bootloader can make a good stuff to mount shares, I ll give it a try : https://mega.nz/folder/zNwiBQjb#blyyBTYV0BrknP886P0yvg XML (just for fun, do it like said before) Citation <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='8'> <name>Xpenology DS918+</name> <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='1'/> </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='1'/> <cache mode='passthrough'/> </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/xpenology/bootloaders/synoboot-104b.img' index='2'/> <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='qcow2' cache='writeback'/> <source file='/mnt/disk1/xpenology/Vdisk-Xpenology-DS918-Prod.img' index='1'/> <backingStore/> <target dev='hdd' bus='sata'/> <alias name='sata1-0-3'/> <address type='drive' controller='1' bus='0' target='0' unit='3'/> </disk> <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='0x05' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x15'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </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> <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> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/appdata/xpenology/datashare/'/> <target dir='surv'/> <alias name='fs0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='XX:XX:XX:XX:XX:XX'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='e1000e'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/8'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/8'> <source path='/dev/pts/8'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-8-Xpenology DS918+ Pro/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='fr'> <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> Edited February 21, 2021 by LittleLama 1 Quote Link to comment Share on other sites More sharing options...
Valiran Posted March 17, 2021 Share #12 Posted March 17, 2021 Hello! I'm currently installing XPE on my Unraid tower. I don't understand why you create a secondary SATA HDD. From my understanding, DSM install himself on each HDD installed inside the NAS, so why do we need a separate HDD for him? Can't we just put the usb synoboot.img and then passthrought all HDD we wan't, and THEN start installing DSM? Quote Link to comment Share on other sites More sharing options...
LittleLama Posted March 17, 2021 Share #13 Posted March 17, 2021 Hi. I didn't read anything this way. If you try it it would be interesting. Quote Link to comment Share on other sites More sharing options...
gadreel Posted March 28, 2021 Share #14 Posted March 28, 2021 On 3/17/2021 at 6:51 PM, Valiran said: Hello! I'm currently installing XPE on my Unraid tower. I don't understand why you create a secondary SATA HDD. From my understanding, DSM install himself on each HDD installed inside the NAS, so why do we need a separate HDD for him? Can't we just put the usb synoboot.img and then passthrought all HDD we wan't, and THEN start installing DSM? You do not have to create a secondary SATA HDD (unless you want to use Vdisks). As you said you can pass-though your drives from Unraid. Quote Link to comment Share on other sites More sharing options...
tvon Posted April 14, 2021 Share #15 Posted April 14, 2021 I was able to get through all the steps, did the find and it found it. I did the install and after it rebooted.. i can't connect. I see the VM up and running but nothing. I see it on the network,but i cannot connect via web and the finder doesnt find it anymore.. suggestions? Quote Link to comment Share on other sites More sharing options...
LittleLama Posted April 14, 2021 Share #16 Posted April 14, 2021 After installation the finder won't work. Did you well changed the network adapter in the xml ? You can give it a try by setting back the adapter as its default value (e1000). Did you well tried connecting to DSM through the ip (with http) with default port 5000 ? Quote Link to comment Share on other sites More sharing options...
tvon Posted April 16, 2021 Share #17 Posted April 16, 2021 (edited) On 4/14/2021 at 4:18 PM, LittleLama said: After installation the finder won't work. Did you well changed the network adapter in the xml ? You can give it a try by setting back the adapter as its default value (e1000). Did you well tried connecting to DSM through the ip (with http) with default port 5000 ? Hi there - I did initially set the adapter to e1000 and i tried using http port 5000. Maybe i should try your whole xml just to see if that works? also, how do i create a mac address? just pick something? Edited April 16, 2021 by tvon Quote Link to comment Share on other sites More sharing options...
tvon Posted April 17, 2021 Share #18 Posted April 17, 2021 okay update. i can get to the web assistant. but its a blank screen and does nothing. Quote Link to comment Share on other sites More sharing options...
WowaDriver Posted August 3, 2021 Share #19 Posted August 3, 2021 Big problem, need urgent help! Due to my stupidity I tried to update my Xpenology VM from the running version DSM 6.2.3-25426 to the newest DSM 6.2.4-25556. As bootimage I use 1.03b for a DS3617. The end of the story is, the VM was no longer responsive => Brick! I had under Unraid passthrough to the VM a DUAL Intel Nic and a LSI SAS2008 PCI-Express Fusion-MPT SAS-2 controller (LSI 9211-8i / Dell H310 HBA in IT-Mode) to which 6x WD 6TB hard disks are connected as RAID5. So I rebuilt the VM and reinstalled the DSM 6.2.3-25426 version, again. I now have the problem that when I passthrough the LSI controller with the 6x hard drives they show up as 6x external hard drives and no longer as RAID5. Please help me, I don't know how to get back the RAID5. A backup is unfortunately not available, I never thought that the RAID5 could be broken by the update. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='9'> <name>Xpenology - VM</name> <uuid>a454f1e6-fe15-df14-0475-fceadd9fb72d</uuid> <description>DS3617xs - File Server</description> <metadata> <vmtemplate xmlns="unraid" name="CentOS" icon="default.png" os="centos"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='5'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='6'/> </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' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='2'/> <cache mode='passthrough'/> </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' index='2'/> <backingStore/> <target dev='hdc' bus='usb'/> <boot order='1'/> <alias name='usb-disk2'/> <address type='usb' bus='0' port='2'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-SanDisk_SDSSDHII120G_154682400434' index='1'/> <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='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-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x16'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0x17'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x7'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0x18'/> <alias name='pci.9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='10' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='10' port='0x19'/> <alias name='pci.10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> </controller> <controller type='pci' index='11' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <alias name='pci.11'/> <address type='pci' domain='0x0000' bus='0x01' 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='0x0b' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:24:c4:10'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='e1000e'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-9-Xpenology - VM/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='5901' autoport='yes' websocket='5701' listen='0.0.0.0' keymap='de'> <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> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> Quote Link to comment Share on other sites More sharing options...
nitrolin Posted September 20, 2022 Share #20 Posted September 20, 2022 On 2/21/2021 at 5:10 PM, LittleLama said: Hi ! Thank you all for this amazing thread. Thank you caperse for the tips, and thank you again IG-88 for your science of xpenology and your time spent to help in so many threads. Big up for you two. I was able to start a VM with DSM 6.2.3 on it. ... Thank you very much for this excellent tutorial. It worked like a charm! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.