toseeme Posted September 12, 2018 #1 Posted September 12, 2018 (edited) 1. Standard host on Proxmox, BIOS=SeaBIOS. SATA0 reserved for loader img. add additional data storage HDD on SATA1. setup boot media from SATA0. add serial port for you troubleshooting. **Pay attention on network, use Intel E1000 instead of VirtIO ** - VirtIO cannot get IP address on network (My experience) 2. copy synoboot.img to /var/lib/vz/image, convert img to qcow2 by qemu-img convert, my qm host ID is 100, please modify to yours. ** example: qemu-img convert -f raw -O qcow2 /var/lib/vz/images/100/synoboot.img /var/lib/vz/images/100/vm-100-disk-1.qcow2 3. import disk by qm inportdisk ** example: qm importdisk 100 /var/lib/vz/images/100/vm-100-disk1.qcow2 <your-qve-disk> 4. back to Proxmox devices setting, attach disk as SATA0. 5. qm start 100 and monitor on serial port. 6. find.synology,com or find IP from your router, using 3617xs 6.2-23729.pat, after launch system, update to 23739 update2. Edited September 12, 2018 by toseeme Quote
yozz Posted September 27, 2018 #2 Posted September 27, 2018 (edited) hey! what disk i need past on part 3? 3. import disk by qm inportdisk ** example: qm importdisk 100 /var/lib/vz/images/100/vm-100-disk1.qcow2 <your-qve-disk> vm-100-disk-0? (sata0 boot disk) or something else? if i try this - i see error "ERROR: unknown command 'qm importdisk'" nvm, i did misprint Edited September 27, 2018 by yozz Quote
toseeme Posted September 28, 2018 Author #3 Posted September 28, 2018 4 hours ago, yozz said: hey! what disk i need past on part 3? 3. import disk by qm inportdisk ** example: qm importdisk 100 /var/lib/vz/images/100/vm-100-disk1.qcow2 <your-qve-disk> vm-100-disk-0? (sata0 boot disk) or something else? if i try this - i see error "ERROR: unknown command 'qm importdisk'" nvm, i did misprint pls try qm --help on your PVE, it will provide you this command as example: qm importdisk <vmid> <source> <storage> [OPTIONS] Quote
kazuni Posted November 19, 2018 #4 Posted November 19, 2018 serial doesn't report anything now... could it be that jun disabled serial piping ? Quote
toseeme Posted November 20, 2018 Author #5 Posted November 20, 2018 Have you add it on Hardware? And check activate information on host console. Quote
themogul504 Posted November 20, 2018 #6 Posted November 20, 2018 I cannot get an get an ip address using proxmox 5.2 Quote
themogul504 Posted November 20, 2018 #7 Posted November 20, 2018 What do i do here I converted to file to qcow2 how would I get the vm to see it. I don't understand part 3. the import to your <your-qve-disk> (what do i do at this part?) Quote
toseeme Posted November 21, 2018 Author #8 Posted November 21, 2018 19 hours ago, themogul504 said: What do i do here I converted to file to qcow2 how would I get the vm to see it. I don't understand part 3. the import to your <your-qve-disk> (what do i do at this part?) the datacnter hdd resource you have. such as hdd-thin. you can check on storage view - Datecenter, which under your Proxmox server list. for mine is hdd-thin. Quote
toseeme Posted November 21, 2018 Author #9 Posted November 21, 2018 19 hours ago, themogul504 said: I cannot get an get an ip address using proxmox 5.2 this is my conf for your refer. Quote
WillWilson Posted January 13, 2019 #10 Posted January 13, 2019 Managed to get DS3617XS working on proxmox like you but can't upgrade to DSM 6.2.1-23824 Update 4 Have you been able todo it? Quote
Antaris Posted January 20, 2019 #11 Posted January 20, 2019 Thanks dude, I also manged to install it on Proxmox 5.3-7 and find small error in step 3: "** example: qm importdisk 100 /var/lib/vz/images/100/vm-100-disk1.qcow2 <your-qve-disk>" should be: "** example: qm importdisk 100 /var/lib/vz/images/100/vm-100-disk-1.qcow2 <your-qve-disk>" according to example in previous step. Quote
Antaris Posted January 23, 2019 #12 Posted January 23, 2019 Any clue from where to get QEMU guest agent? Quote
wenlez Posted January 31, 2019 #13 Posted January 31, 2019 There is no QEMU guest agent for Xpenology. At least not at the moment. Quote
toseeme Posted March 12, 2019 Author #14 Posted March 12, 2019 On 11/20/2018 at 4:31 PM, themogul504 said: I cannot get an get an ip address using proxmox 5.2 use intel e1000 instead of virtIO network card Quote
toseeme Posted March 12, 2019 Author #15 Posted March 12, 2019 On 1/20/2019 at 9:31 PM, Antaris said: Thanks dude, I also manged to install it on Proxmox 5.3-7 and find small error in step 3: "** example: qm importdisk 100 /var/lib/vz/images/100/vm-100-disk1.qcow2 <your-qve-disk>" should be: "** example: qm importdisk 100 /var/lib/vz/images/100/vm-100-disk-1.qcow2 <your-qve-disk>" according to example in previous step. <your-qve-disk> means the location where your PVE server saves your host. for me is Local-LVM. you can find it as picture show. Quote
toseeme Posted March 12, 2019 Author #16 Posted March 12, 2019 it's also working on DSM918+ 1.04b with new DSM_DS918+_23824.pat Quote
Shawn Posted May 11, 2019 #17 Posted May 11, 2019 On 9/11/2018 at 9:31 PM, toseeme said: system hi, toseeme I followed your post but I got "no hard disk" error. Any ideas why? PVE version is 5.4-3. loader 1.03b Quote
graddumdum Posted July 11, 2019 #18 Posted July 11, 2019 On 9/12/2018 at 8:31 AM, toseeme said: qm importdisk 100 /var/lib/vz/images/100/vm-100-disk1.qcow2 <your-qve-disk> Its still giving me an error. root@Proxmos:~# qm importdisk 102 /var/lib/vz/images/102/vm-102-disk1.qcow2 local-lvm /var/lib/vz/images/102/vm-102-disk1.qcow2: non-existent or non-regular file Quote
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.