boris0n Posted August 24, 2017 Share #1 Posted August 24, 2017 (edited) hi dear cummunity I wrote small instruction for many users, who use hypervisor QEMU\KVM (best for me config in attach "XML") download loader convert synoboot.img to qcow2 qemu-img convert -f raw -O qcow2 synoboot.img synoboot-qcow2.img create VM with $your-name-vm open config file with $your-name-vm virsh edit $your-name-vm edit CPU <cpu mode='custom' match='exact'> <model fallback='allow'>Westmere</model> <vendor>Intel</vendor> <feature policy='require' name='vme'/> <feature policy='require' name='ds'/> <feature policy='require' name='acpi'/> <feature policy='require' name='ss'/> <feature policy='require' name='ht'/> <feature policy='require' name='tm'/> <feature policy='require' name='pbe'/> <feature policy='require' name='pclmuldq'/> <feature policy='require' name='dtes64'/> <feature policy='require' name='monitor'/> <feature policy='require' name='ds_cpl'/> <feature policy='require' name='vmx'/> <feature policy='require' name='est'/> <feature policy='require' name='tm2'/> <feature policy='require' name='xtpr'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='movbe'/> <feature policy='require' name='tsc-deadline'/> <feature policy='require' name='rdrand'/> <feature policy='require' name='arat'/> <feature policy='require' name='tsc_adjust'/> <feature policy='require' name='smep'/> <feature policy='require' name='erms'/> <feature policy='require' name='rdtscp'/> <feature policy='require' name='3dnowprefetch'/> </cpu> edit network interface (for default in loader using this mac address - "00:11:32:2c:a7:85" and Interface type - "e1000"; best for me - "bridge" mode; "enp3s0" interface ) <interface type='direct'> <mac address='00:11:32:2c:a7:85'/> <source dev='enp3s0' mode='bridge'/> <model type='e1000'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> edit Sata Controller loader on QEMU\QVM need 2 Sata controllers: <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='sata' index='1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </controller> 0 - empty controller; 1 - for Sata Drives edit Drives: Sata Drive (target dev - "SDA"; bus - "Sata"; Controller Sata - "1"; best for me: target-"0", unit-"0", and path to qcow2 image) <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/images/Xpenology.qcow2'/> <target dev='sda' bus='sata'/> <address type='drive' controller='1' bus='0' target='0' unit='0'/> </disk> Usb Drive with Loader (type - "USB", bus- "0", port - "1", boot order = "1"; best for me - path to qcow2 synoboot image) <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/home/administrator/VMs/ISO/Xpenology/ds3615/synoboot-qcow2.img'/> <target dev='sdb' bus='usb'/> <boot order='1'/> <address type='usb' bus='0' port='1'/> </disk> ENJOY! XML.xml Edited August 24, 2017 by boris0n Quote Link to comment Share on other sites More sharing options...
hemna Posted April 27, 2020 Share #2 Posted April 27, 2020 I have tried this, but it doesn't work for me. The boot loader comes up and says "Intro: This mod is brought to you by Jun..... Screen will stop updating shortly, please open http://find.synology.com to continue." The vm cpu load goes up and stays up (looking at virt-manager), I go to http://find.synology.com and it never finds it. 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.