<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title></title>
		<description>Discuss </description>
		<link>https://xmoxology.duckdns.org</link>
		<lastBuildDate>Tue, 05 May 2026 02:31:58 +0200</lastBuildDate>
		<generator>JComments</generator>
		<atom:link href="https://xmoxology.duckdns.org/component/jcomments/feed/com_content/53" rel="self" type="application/rss+xml" />
		<item>
			<title>RE: Install Xpenology DSM 6.1.x on Proxmox</title>
			<link>https://xmoxology.duckdns.org#comment-265</link>
			<description><![CDATA[hi thanks for the guide, its gr8. i wonder how do i directly attach two drives i have to the DSM and not via the Proxmox. I have been able to see the drives on the Proxmox within the Host > Disks section /dev/sdb /dev/sdc and have been able to attach to the DSM too using qm set 102 -sata2 /dev/disk/by-id/wwn-0x5000c500226127d2 update VM 102: -sata2 /dev/disk/by-id/wwn-0x5000cca37cc9275e but post creating storage pool and volume, the storage pool crashes within few minutes. So am i wrong to use -sata as an interface, although drives are connected using SATA Cable? could you please help?]]></description>
			<dc:creator>ontljoshi</dc:creator>
			<pubDate>Wed, 23 Dec 2020 13:58:04 +0100</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-265</guid>
		</item>
		<item>
			<title>Gracias</title>
			<link>https://xmoxology.duckdns.org#comment-264</link>
			<description><![CDATA[Gracias Michel!! Buen tuto y bien explicado. Abrazo!!]]></description>
			<dc:creator>Zippo</dc:creator>
			<pubDate>Thu, 25 Jun 2020 00:29:22 +0200</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-264</guid>
		</item>
		<item>
			<title>Help with Linode</title>
			<link>https://xmoxology.duckdns.org#comment-260</link>
			<description><![CDATA[How do I load these settings onto Linode or Vultr vps providers? I have loaded bootdisk (jun's loader) on a disk and it boots, but I cannot connect (some sort of network problem) any ideas? appreciate your reply.]]></description>
			<dc:creator>Dan</dc:creator>
			<pubDate>Sun, 22 Sep 2019 08:07:44 +0200</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-260</guid>
		</item>
		<item>
			<title>Buen tutorial</title>
			<link>https://xmoxology.duckdns.org#comment-259</link>
			<description><![CDATA[El tutorial es bueno, siempre se agradece el esfuerzo]]></description>
			<dc:creator>Mauricio Avila</dc:creator>
			<pubDate>Fri, 17 May 2019 19:33:21 +0200</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-259</guid>
		</item>
		<item>
			<title>solved</title>
			<link>https://xmoxology.duckdns.org#comment-256</link>
			<description><![CDATA[Hi, just wanted to check back in with a solution i found on [censored]s://www.bachmann-lan.de/xpenology-6-2-un ter-proxmox-installieren/ i imported the synoboot.img as a disk using this command syntax: qm importdisk [OPTIONS] (in my case "qm importdisk 101 /var/lib/vz/images/synoboot.img local-lvm") this creates an unused disk you can mount as ide (or sata if you prefer) under boot settings, you boot this disk first.]]></description>
			<dc:creator>vizkoze</dc:creator>
			<pubDate>Sun, 10 Feb 2019 16:44:13 +0100</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-256</guid>
		</item>
		<item>
			<title>RE: Proxmox 5.3-5</title>
			<link>https://xmoxology.duckdns.org#comment-255</link>
			<description><![CDATA[Hi, i'm having issues with crashing dsm start. I was using a custom img 1.02b with built in virtio ethernet drivers but after a restart, i noticed proxmox update to 5.3.6 and i was unable to start dsm. have you figured out how to repair this?]]></description>
			<dc:creator>vizkoze</dc:creator>
			<pubDate>Sun, 10 Feb 2019 13:22:57 +0100</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-255</guid>
		</item>
		<item>
			<title>Proxmox 5.3-5</title>
			<link>https://xmoxology.duckdns.org#comment-252</link>
			<description><![CDATA[Hi, It seems like i'm crashing when I try to start DS3615xs 6.1 Jun's Mod V1.02b.img. Anyone else on version 5.3-5?]]></description>
			<dc:creator>Darky</dc:creator>
			<pubDate>Wed, 02 Jan 2019 16:23:12 +0100</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-252</guid>
		</item>
		<item>
			<title>Reason not able to choose qcow as format</title>
			<link>https://xmoxology.duckdns.org#comment-251</link>
			<description><![CDATA[From the proxmox manual: "The choice of a storage type will determine the format of the hard disk image. Storages which present block devices (LVM, ZFS, Ceph) will require the raw disk image format, whereas files based storages (Ext4, NFS, CIFS, GlusterFS) will let you to choose either the raw disk image format or the QEMU image format." So your proxmox install only contains LVM/ZFS/Ceph storage types.]]></description>
			<dc:creator>zorroog</dc:creator>
			<pubDate>Mon, 15 Oct 2018 14:23:26 +0200</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-251</guid>
		</item>
		<item>
			<title>RE: bootorder not persistent</title>
			<link>https://xmoxology.duckdns.org#comment-250</link>
			<description><![CDATA[Currently I am using proxmox ve 5.2-6 with the following conf which works for me: args: -device 'piix3-usb-uhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/100/synoboot_ xmox.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot' bios: ovmf boot: d efidisk0: local:100/vm-100-disk-0-efi.qcow2,size=128K machine: q35 name: xpenology ostype: l26 serial0: socket ... It is used with Jun's Loader 1.02b (ds3615) to run DSM 6.1.x (currently I am on 6.1.7). I am not sure what the culprit and why you can only choose raw ... because for me, when I create a UEFI disk, I have choice between raw,qcow2 and vmdk. Well if EFI really doesn't work for you, you can still use the bootloader as a disk and boot on it as I have explained to Belokan a few posts before.]]></description>
			<dc:creator>UxOra DBA</dc:creator>
			<pubDate>Sun, 02 Sep 2018 15:30:25 +0200</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-250</guid>
		</item>
		<item>
			<title>bootorder not persistent</title>
			<link>https://xmoxology.duckdns.org#comment-249</link>
			<description><![CDATA[Hi, i followed you excellent guide and my first try did succeed. Like Abdessamad, my bootorder is not persistent. I'm using proxmox 5.2. even tried the Set boot: z in /etc/pve/qemu-server/10x.conf (in my case 103.conf) without succes. there are some differences between 5.2 and you guide. I noticed you use qcow2, I only get the raw option on my box. Could this be the cultprint? standard install with local-lvm provisioning for disk images it drives me nuts not to be able to reboot the vm without going into the uefi bios]]></description>
			<dc:creator>vinny</dc:creator>
			<pubDate>Sat, 01 Sep 2018 00:11:50 +0200</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-249</guid>
		</item>
		<item>
			<title>RE: Great article !</title>
			<link>https://xmoxology.duckdns.org#comment-246</link>
			<description><![CDATA[If EFI really does not work, you may want to try this: - Rename loader (as root): $ mv synoboot.img synoboot_ds3615_v1.03b.raw - Copy it in vm disk folder (ie. /var/lib/vz/images/103/.) - Then use it as a drive by adding these lines in conf (ie. /etc/pve/qemu-server/103.conf) bootdisk: ide0 ide0: local:103/synoboot_ds3615_v1.03b.raw,size=52429K You may want to check this comment as well: [censored]s://xpenology.com/forum/topic/12952-dsm- 62-loader/?page=5&tab=comments#comment-93988 (edit1: choose ide to not mess with sata) (edit2: do not need to convert to qcow2)]]></description>
			<dc:creator>UxOra DBA</dc:creator>
			<pubDate>Sun, 12 Aug 2018 15:11:40 +0200</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-246</guid>
		</item>
		<item>
			<title>RE: install without dhcp server?</title>
			<link>https://xmoxology.duckdns.org#comment-245</link>
			<description><![CDATA[True ... I forgot to mention that, in my case, my Proxmox server NIC eth0 (link with vmbr0 bridge) is connected to a router (with dhcp). If you are not behind a router, I may advise to - install/configure isc-dhcp-server as simple dhcp on proxmox - or create a vm with pfsense as a powerful firewall/router]]></description>
			<dc:creator>UxOra DBA</dc:creator>
			<pubDate>Sun, 12 Aug 2018 00:26:54 +0200</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-245</guid>
		</item>
		<item>
			<title>install without dhcp server?</title>
			<link>https://xmoxology.duckdns.org#comment-244</link>
			<description><![CDATA[i don´t undestaind how your VM xpenlogy is getting an ip via dhcp server cause proxmox not have dhcp by default.]]></description>
			<dc:creator>luis</dc:creator>
			<pubDate>Fri, 10 Aug 2018 20:33:33 +0200</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-244</guid>
		</item>
		<item>
			<title>RE: Great article !</title>
			<link>https://xmoxology.duckdns.org#comment-243</link>
			<description><![CDATA[Thanks for your answer Michel. Looks like Jun's 6.2 loader has issue with EFI right now. As I'm just running regular Debian/CentOS VMs and various containers on my Proxmox environment, I've always used default Seabios BIOS and never played around with EFI apart from this XPE instance ... Any idea/hint on how to get rid of EFI in your tuto ? Maybe a vm.conf file with required modifications ? Thanks in advance]]></description>
			<dc:creator>Belokan</dc:creator>
			<pubDate>Wed, 08 Aug 2018 09:43:32 +0200</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-243</guid>
		</item>
		<item>
			<title>RE: Great article !</title>
			<link>https://xmoxology.duckdns.org#comment-242</link>
			<description><![CDATA[Yes, It's possible. First of all, I would recommend to disable automatic updates as follow: - Go to Control Panel > Update and Restore - On the "DSM Update" tab, - ** click "Update Settings" then check "Important updates only" - ** and select "Download DSM updates but let me choose whether to install them" For minor update (i.e 6.1.x to 6.1.y): - Check if there is no issue with the update on xpenology.com/forum/forum/78-critical-updates/ - Then if ok, just do a normal synology update as usual through "Control Panel > Update and Restore" For major update (i.e 6.1.x to 6.2.y), it's a bit more stressful but possible: - It usually requires to update the bootloader (check if bootloader is stable on xpenology.com/forum/forum/31-loaders/) - Restart with the new bootloader and do a normal synology migration as if it is a new synology machine]]></description>
			<dc:creator>UxOra DBA</dc:creator>
			<pubDate>Tue, 07 Aug 2018 15:35:18 +0200</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-242</guid>
		</item>
		<item>
			<title>Great article !</title>
			<link>https://xmoxology.duckdns.org#comment-241</link>
			<description><![CDATA[Hi, I've recently decommissioned my 2 "real" Synology (412+ & 415+) and replaced them by OMV VM running on Proxmox nodes. I've replaced Surveillance Station by ZoneMinder + ZmNinja. But I was missing few DSM apps not that easily replaceable. I was about to find a second hand 112j when I decided to give XPE a try. I've tried several tutorials but yours is the one that worked straightforward, thanks ! I just have a question about upgrades. Are they even possible ? Or must I stick to 6.1.5 forever ? Thanks in advance !]]></description>
			<dc:creator>Belokan</dc:creator>
			<pubDate>Tue, 07 Aug 2018 07:53:34 +0200</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-241</guid>
		</item>
		<item>
			<title>RE: Question</title>
			<link>https://xmoxology.duckdns.org#comment-239</link>
			<description><![CDATA[You're welcome. :) For your boot order saving issue, make sure you have: - Set VM BIOS to "OVMF UEFI" - Added an EFI disk to your VM - Set boot to z in /etc/pve/qemu-server/10x.conf (UPDATE: This "z" boot trick is no more needed from Proxmox 5.2) Then you should be able to save your bios boot order. All theses steps are shown in this article. Hope this helps.]]></description>
			<dc:creator>UxOra DBA</dc:creator>
			<pubDate>Tue, 19 Jun 2018 13:29:31 +0200</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-239</guid>
		</item>
		<item>
			<title>Question</title>
			<link>https://xmoxology.duckdns.org#comment-238</link>
			<description><![CDATA[Hello Great guide , thanks, i have 1 small problem, when i reboot the VM , proxmox load default boot order .. so i have to enter bios and re up USB]]></description>
			<dc:creator>Abdessamad</dc:creator>
			<pubDate>Mon, 18 Jun 2018 22:51:33 +0200</pubDate>
			<guid>https://xmoxology.duckdns.org#comment-238</guid>
		</item>
	</channel>
</rss>
