<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Proxmox VE on Margrop Blog</title>
    <link>https://blog.margrop.net/en/tag/proxmox-ve/</link>
    <description>Recent content in Proxmox VE on Margrop Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Sat, 11 Jul 2026 02:30:00 +0800</lastBuildDate>
    <atom:link href="https://blog.margrop.net/en/tag/proxmox-ve/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Proxmox VE 9.0 Daily Maintenance: Remove the No-Subscription Notice and Use China Mirrors (Updated 2025-08-06)</title>
      <link>https://blog.margrop.net/en/post/proxmox-ve-daily-maintain/</link>
      <pubDate>Sun, 26 Feb 2023 20:00:19 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/proxmox-ve-daily-maintain/</guid>
      <description>&lt;p&gt;This article collects the most common maintenance tasks for PVE 6.x / 7.x / 8.x / 9.x and fixes duplicated sections and obvious errors from older revisions.&lt;/p&gt;&#xA;&lt;p&gt;Check the current version first, then follow the instructions that match that version. Do not mix repository settings across different PVE releases.&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;pveversion&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;</description>
    </item>
    <item>
      <title>Stop Clicking Through VMs: A Hands-On Guide to Connecting Proxmox VE to an AI Agent Safely</title>
      <link>https://blog.margrop.net/en/post/proxmox-ve-ai-agent-guide/</link>
      <pubDate>Sat, 11 Jul 2026 02:30:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/proxmox-ve-ai-agent-guide/</guid>
      <description>Connecting an AI agent to Proxmox VE sounds like giving a robot administrator the keys to your datacenter. That is exactly what you should not do. The safe starting point is a dedicated, revocable, read-only API token, a locally running MCP server, and a clear approval boundary for every write operation. This guide explains the architecture, shows manual and agent-assisted setup, and provides one-click installers for Windows 11, Ubuntu 26.</description>
    </item>
    <item>
      <title>Avoiding the Trap: Why Fail2Ban Fails on Ubuntu 26.04 &amp; PVE 9.2 (And How to Fix It)</title>
      <link>https://blog.margrop.net/en/post/ubuntu-2604-pve-92-fail2ban-nftables-guide/</link>
      <pubDate>Tue, 26 May 2026 22:20:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/ubuntu-2604-pve-92-fail2ban-nftables-guide/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;The Bottom Line&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;With the releases of Ubuntu 26.04 LTS and Proxmox VE (PVE) 9.2, many system administrators, DevOps engineers, and self-hosting enthusiasts have eagerly upgraded or clean-installed these latest systems. However, during the post-installation security hardening phase, you may encounter a highly frustrating scenario: &lt;strong&gt;simply copying over your legacy Fail2Ban configuration files from older versions (such as Ubuntu 20.04/22.04 or PVE 7.x/8.x) will either cause the Fail2Ban service to crash during startup or, worse, run silently in the background while completely failing to block external brute-force attacks!&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;This issue is not caused by a bug in Fail2Ban itself. Instead, it is the result of three &amp;ldquo;invisible bombs&amp;rdquo; hidden beneath the surface of these modern Linux distributions, namely changes in the logging architecture, service activation mechanisms, and firewall backends. This article provides an in-depth analysis of these three architectural shifts and introduces a modern, bulletproof Fail2Ban configuration guide fully integrated with &lt;code&gt;systemd-journald&lt;/code&gt; and &lt;code&gt;nftables&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
    </item>
    <item>
      <title>Resize the disk of an Ubuntu VM in PVE — the complete workflow from Web UI to guest OS</title>
      <link>https://blog.margrop.net/en/post/pve-ubuntu-vm-disk-resize/</link>
      <pubDate>Mon, 23 Mar 2026 10:30:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/pve-ubuntu-vm-disk-resize/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Preface&lt;/strong&gt;&#xA;When you manage a virtualized environment with Proxmox VE, running out of disk space is only a matter of time. Maybe your Ubuntu VM keeps pulling more Docker images, or maybe database logs fill up the root partition. In short, disk expansion is a must-have skill for PVE operations. This article walks through the entire process, from resizing the virtual disk in the PVE Web UI to expanding LVM inside the Ubuntu guest, step by step.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;1-why-do-we-need-to-resize&#34;&gt;1 Why do we need to resize?&lt;/h2&gt;&#xA;&lt;p&gt;PVE usually allocates a fixed-size virtual disk when a VM is created, for example 32 GB. As the workload grows, that space may no longer be enough. Fortunately, PVE supports online disk expansion, and Ubuntu&amp;rsquo;s default LVM setup also supports dynamic logical volume expansion. Together, they make the process very convenient.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ProxmoxVE Upgrade from 8 to 9 How to upgrade to PVE9</title>
      <link>https://blog.margrop.net/en/post/proxmoxve-upgrade-from-8-to-9/</link>
      <pubDate>Wed, 06 Aug 2025 13:28:55 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/proxmoxve-upgrade-from-8-to-9/</guid>
      <description>参考文档：https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 Preparation before upgrading pve8to9 apt update apt dist-upgrade pveversion #reboot 建议更新完毕后重启1次 Operation step one (back up existing files) cp /etc/apt/sources.list /etc/apt/sources.list_202508_bak cp /etc/apt/sources.list.d/pve-install-repo.list /etc/apt/sources.list.d/pve-install-repo.list_202508_bak Operation step two (start upgrading) sed -i &amp;#39;s/bookworm/trixie/g&amp;#39; /etc/apt/sources.list sed -i &amp;#39;s/bookworm/trixie/g&amp;#39; /etc/apt/sources.list.d/pve-install-repo.list apt update apt dist-upgrade Operation step three (remove unsubscribed prompts) sed -i_orig &amp;#34;s/data.status === &amp;#39;Active&amp;#39;/true/g&amp;#34; /usr/share/pve-manager/js/pvemanagerlib.js sed -i_orig &amp;#34;s/if (res === null || res === undefined || \!res || res/if(/g&amp;#34; /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js sed -i_orig &amp;#34;s/.</description>
    </item>
    <item>
      <title>PVE disk inspection connected to UptimeKuma - the 404 pitfall and the final script</title>
      <link>https://blog.margrop.net/en/post/pve-host-virtual-machine-disk-space-monitor-experience-step-two/</link>
      <pubDate>Wed, 14 May 2025 22:16:48 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/pve-host-virtual-machine-disk-space-monitor-experience-step-two/</guid>
      <description>Read first The previous article showed how to push the PVE host&amp;rsquo;s LVM-Thin usage to UptimeKuma. After following the instructions, some readers got a 404 when the script used curl. This article explains the cause, fixes the script, and provides an optional upgrade path. Follow along from scratch and you should succeed on the first try.&#xA;1 Phenomenon: curl ... 404 curl -fsS --retry 3 \ &amp;#34;${PUSH_URL}?status=up&amp;amp;msg=OK&amp;#34; \ -H &amp;#39;Content-Type: application/json&amp;#39; \ --data-raw &amp;#34;$result&amp;#34; # ↳ curl: (22) The requested URL returned error: 404 The same URL works in a browser or with curl GET:</description>
    </item>
    <item>
      <title>PVE host disk space monitoring - from pitfalls to UptimeKuma</title>
      <link>https://blog.margrop.net/en/post/pve-host-virtual-machine-lvm-disk-space-monitor-experience/</link>
      <pubDate>Wed, 14 May 2025 22:11:33 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/pve-host-virtual-machine-lvm-disk-space-monitor-experience/</guid>
      <description>Target Reader This article is written for readers who have just started using Proxmox VE (referred to as PVE) and want to copy the steps and get it running. The article aims to:&#xA;explain why the problem happens provide the full command at each step give troubleshooting ideas when something goes wrong 0 Background - What went wrong? The official PVE installation wizard defaults to putting the VM disk into the LVM-Thin pool (commonly pve/data)</description>
    </item>
    <item>
      <title>An Effective Method to Quickly Set Up Fail2ban in Proxmox VE to Prevent Multiple Failed Login Attempts</title>
      <link>https://blog.margrop.net/en/post/how-to-quickly-configure-fail2ban-in-proxmox-ve/</link>
      <pubDate>Tue, 18 Jun 2024 15:33:01 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/how-to-quickly-configure-fail2ban-in-proxmox-ve/</guid>
      <description>&lt;p&gt;This briefly introduces how to set up Fail2ban in Proxmox VE to temporarily block IP addresses with multiple failed login attempts.&lt;/p&gt;&#xA;&lt;h3 id=&#34;install-fail2ban&#34;&gt;Install Fail2ban&lt;/h3&gt;&#xA;&lt;p&gt;Execute the following commands as root on the Proxmox VE host:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;apt update&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;apt install fail2ban&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3 id=&#34;configure-basic-settings&#34;&gt;Configure Basic Settings&lt;/h3&gt;&#xA;&lt;p&gt;It is recommended to use the &lt;code&gt;/etc/fail2ban/jail.local&lt;/code&gt; file, whose settings take precedence over &lt;code&gt;jail.conf&lt;/code&gt;. Use the following command to copy the template:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;cp /etc/fail2ban/jail.conf /etc/fail2ban/jail.local&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;</description>
    </item>
    <item>
      <title>N5105 Proxmox VE 8.2 version, solving the problem of frequent virtual machine crashes</title>
      <link>https://blog.margrop.net/en/post/n5105-in-promox-ve-frequently-dead/</link>
      <pubDate>Sat, 04 May 2024 07:55:22 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/n5105-in-promox-ve-frequently-dead/</guid>
      <description>1. Problem background Recently, major PT websites were developed and registered on May Day, so I registered several websites, and then downloaded and uploaded them like crazy in order to complete novice tasks. As soft routers, N5105 and iKuai, when under high load for a long time, the virtual machine crashed randomly, and the CPU remained at 100% for a long time. The virtual machine could only be killed and restarted, which greatly affected the completion of novice tasks.</description>
    </item>
    <item>
      <title>Installing a Minimal k8s Environment with Minikube</title>
      <link>https://blog.margrop.net/en/post/install-min-k8s-using-minikube-on-pve/</link>
      <pubDate>Tue, 30 Apr 2024 19:37:29 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/install-min-k8s-using-minikube-on-pve/</guid>
      <description>&lt;p&gt;Deploying Minikube on Proxmox VE (a Debian-based virtualization environment) requires consideration of Proxmox&amp;rsquo;s characteristics, as it is essentially a virtual machine and container management platform. You will need to create a virtual machine (VM) on Proxmox VE and then install Minikube within that VM. Below are the detailed steps:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Upgrade ProxmoxVE 7.4 to 8.0, detailed steps</title>
      <link>https://blog.margrop.net/en/post/pve-7-upgrade-to-8/</link>
      <pubDate>Sat, 08 Jul 2023 10:25:13 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/pve-7-upgrade-to-8/</guid>
      <description>Step 1: Read the official documentation in detail Notice: If you use ssh connection remotely, it is recommended to use the screen command first to avoid various problems caused by network instability and operation interruption.&#xA;Step 2: Upgrade to the latest version 7.4 The latest version is 7.4.15&#xA;apt update -y &amp;amp;&amp;amp; apt dist-upgrade -y sed -i_orig &amp;#34;s/data.status === &amp;#39;Active&amp;#39;/true/g&amp;#34; /usr/share/pve-manager/js/pvemanagerlib.js sed -i_orig &amp;#34;s/if (res === null || res === undefined || \!</description>
    </item>
    <item>
      <title>Proxmox VE 6.4 daily upgrade commands</title>
      <link>https://blog.margrop.net/en/post/proxmox-ve-upgrade-software-command/</link>
      <pubDate>Mon, 29 Mar 2021 08:23:52 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/proxmox-ve-upgrade-software-command/</guid>
      <description>Remove unused Linux kernel pvekclean Update software: apt update -y &amp;amp;&amp;amp; apt dist-upgrade -y Remove the unsubscribed prompt and support PVE 6.3 / 6.4 sed -i_orig &amp;#34;s/data.status === &amp;#39;Active&amp;#39;/true/g&amp;#34; /usr/share/pve-manager/js/pvemanagerlib.js sed -i_orig &amp;#34;s/if (res === null || res === undefined || \!res || res/if(/g&amp;#34; /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js sed -i_orig &amp;#34;s/.data.status.toLowerCase() !== &amp;#39;active&amp;#39;/false/g&amp;#34; /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js systemctl restart pveproxy After confirming that everything is correct, restart the server. reboot Solve software upgrade problems Added Alibaba Cloud&amp;rsquo;s Debian image source</description>
    </item>
    <item>
      <title>How to Install Jike AC Virtual Machine in Proxmox VE Environment?</title>
      <link>https://blog.margrop.net/en/post/how-to-install-jika-ac-in-pve/</link>
      <pubDate>Wed, 03 Feb 2021 16:18:33 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/how-to-install-jika-ac-in-pve/</guid>
      <description>&lt;p&gt;According to &lt;a href=&#34;https://www.right.com.cn/forum/thread-1501038-1-1.html&#34;&gt;恩山的集客AC AP扫盲贴&lt;/a&gt;:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Q: Can I skip &lt;code&gt;AC&lt;/code&gt; and have two &lt;code&gt;AP&lt;/code&gt; connect directly to the main router for roaming?&#xA;A: Yes, but roaming works better with &lt;code&gt;AC&lt;/code&gt; than without it. With &lt;code&gt;ac&lt;/code&gt; present, roaming performance won&amp;rsquo;t disappoint. Jike&amp;rsquo;s roaming is not a simple weak-signal kick. With &lt;code&gt;ac&lt;/code&gt; in place, excellent roaming effects are achieved regardless of whether Jike &lt;code&gt;ap&lt;/code&gt; supports &lt;code&gt;kvr&lt;/code&gt;, because &lt;code&gt;ac+ap&lt;/code&gt; is proactive roaming, which does not rely on &lt;code&gt;kvr&lt;/code&gt; protocol and has very low requirements on clients. Micro &lt;code&gt;ac&lt;/code&gt; only handles configuration distribution and cannot perform proactive roaming; roaming effectiveness depends on the client.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
    </item>
    <item>
      <title>Let&#39;s Encrypt automatically synchronizes Proxmox VE and DSM certificates after automatic renewal</title>
      <link>https://blog.margrop.net/en/post/lets-encrypt-sync-https-cert-to-pve-and-dsm/</link>
      <pubDate>Tue, 02 Feb 2021 19:19:38 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/lets-encrypt-sync-https-cert-to-pve-and-dsm/</guid>
      <description>Last time we talked about Let&amp;rsquo;s Encrypt通过DNS TXT记录来验证域名有效性, and the last part of the article was about how to use certbot renew for automatic renewal. Then the automatic renewal is successful, how to synchronize it to PVE and DSM?&#xA;Below we use a script to perform automatic synchronization.&#xA;Need to configure SSH password-free login on Proxmox VE and DSM servers Automatically synchronize Proxmox VE certificate Proxmox VE synchronized to this machine Proxmox VE synchronized to LAN cp /etc/letsencrypt/live/blog.</description>
    </item>
    <item>
      <title>How to Import a Third-Party VM Image into Proxmox VE</title>
      <link>https://blog.margrop.net/en/post/pve-kvm-import-vm-format-qcow2/</link>
      <pubDate>Mon, 01 Feb 2021 15:12:47 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/pve-kvm-import-vm-format-qcow2/</guid>
      <description>&lt;p&gt;In the example below, the &lt;code&gt;VM ID&lt;/code&gt; is always &lt;code&gt;100&lt;/code&gt;; change it as needed.&lt;/p&gt;&#xA;&lt;h1 id=&#34;file-format-conversion&#34;&gt;File Format Conversion&lt;/h1&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Use &lt;code&gt;qemu-img&lt;/code&gt; to convert virtual disk files in other formats to &lt;code&gt;qcow2&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;For example, the following converts &lt;code&gt;vmdk&lt;/code&gt; to &lt;code&gt;qcow2&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>How to Configure a Freshly Installed Ubuntu 20.04 Server VM on PVE</title>
      <link>https://blog.margrop.net/en/post/pve-how-to-config-brand-new-ubuntu-20.04-vm/</link>
      <pubDate>Sat, 30 Jan 2021 15:33:44 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/pve-how-to-config-brand-new-ubuntu-20.04-vm/</guid>
      <description>&lt;h1 id=&#34;download-the-installation-iso&#34;&gt;Download the Installation ISO&lt;/h1&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://mirrors.aliyun.com/ubuntu-releases/focal/ubuntu-20.04.2-live-server-amd64.iso&#34;&gt;Aliyun Ubuntu 20.04 live server download&lt;/a&gt;&#xA;&lt;a href=&#34;https://mirrors.aliyun.com/ubuntu-releases/bionic/ubuntu-18.04.5-live-server-amd64.iso&#34;&gt;Aliyun Ubuntu 18.04 live server download&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Enable Intel GVT-g Graphics Virtualization on Proxmox VE</title>
      <link>https://blog.margrop.net/en/post/proxmox-ve-graphics-card-enable-intel-gvt-g/</link>
      <pubDate>Sat, 23 Jan 2021 11:23:04 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/proxmox-ve-graphics-card-enable-intel-gvt-g/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;Note: Intel GVT-g is currently only supported by fifth, sixth, and seventh generation Intel Core processors and Xeon E3 v4/v5/v6 processors on PVE.&#xA;My tests show that 8th generation and newer CPUs are not supported for now -_-!&#xA;If this changes, feel free to contact me.&#xA;Reference: &lt;a href=&#34;https://pve.proxmox.com/wiki/PCI(e)_Passthrough&#34;&gt;https://pve.proxmox.com/wiki/PCI(e)_Passthrough&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
    </item>
    <item>
      <title>Proxmox VE commonly used local paths, and how to modify hosts, host name, IP address and DNS configuration</title>
      <link>https://blog.margrop.net/en/post/proxmox-ve-url-and-modify-hosts-ip-dns/</link>
      <pubDate>Fri, 22 Jan 2021 17:02:01 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/proxmox-ve-url-and-modify-hosts-ip-dns/</guid>
      <description>PVE local ISO file directory: /var/lib/vz/template/iso PVE local OVZ file directory: /var/lib/vz/template/cache&#xA;Modify hosts file Effective after restart vi /etc/hosts Modify hostname Effective after restart vi /etc/hostname Modify IP address and DNS configuration Effective after restart Reference DNS configuration vi /etc/network/interfaces dns-nameservers 114.114.114.114,223.5.5.5 </description>
    </item>
    <item>
      <title>Initialization script after Proxmox VE installation</title>
      <link>https://blog.margrop.net/en/post/proxmox-ve-init-bash-script/</link>
      <pubDate>Fri, 22 Jan 2021 16:42:46 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/proxmox-ve-init-bash-script/</guid>
      <description>&lt;p&gt;In order to facilitate the installation of PVE, I compiled the relevant commands myself. Please modify them according to your own environment.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ProxmoxVE 6.3 uses commands to back up Synology virtual machines</title>
      <link>https://blog.margrop.net/en/post/proxmoxve-use-bash-to-backup-dsm-vm/</link>
      <pubDate>Thu, 21 Jan 2021 18:16:22 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/proxmoxve-use-bash-to-backup-dsm-vm/</guid>
      <description>Since the Synology virtual machine in my ProxmoxVE runs on a LUN passthrough disk, I cannot click backup directly in the Web interface.&#xA;DSM virtual machine backup process: Stop the virtual machine -&amp;gt; Unmount the hard disk -&amp;gt; Back up the virtual machine -&amp;gt; Mount the hard disk -&amp;gt; Start the virtual machine It is really troublesome and error-prone to do this entirely through the Web interface. So I studied the command-line workflow.</description>
    </item>
    <item>
      <title>Does Synology DSM Support QEMU Guest Agent?</title>
      <link>https://blog.margrop.net/en/post/is-dsm-supported-qemu-agent/</link>
      <pubDate>Wed, 20 Jan 2021 13:19:28 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/is-dsm-supported-qemu-agent/</guid>
      <description>&lt;p&gt;Install the &lt;code&gt;Power Button Package&lt;/code&gt; in Synology DSM and disable the &lt;code&gt;qemu&lt;/code&gt; agent option in &lt;code&gt;PVE&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;h1 id=&#34;where-to-download-the-power-button-package&#34;&gt;Where to Download the Power Button Package&lt;/h1&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Note that &lt;code&gt;DSM 6.1&lt;/code&gt; and &lt;code&gt;DSM 6.2&lt;/code&gt; use different &lt;code&gt;spk&lt;/code&gt; packages&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>img2KVM, Convert IMG Format to KVM Format, Install DSM Synology Virtual Machine</title>
      <link>https://blog.margrop.net/en/post/img2kvm-convert-img-format-file-to-kvm/</link>
      <pubDate>Wed, 20 Jan 2021 08:32:25 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/img2kvm-convert-img-format-file-to-kvm/</guid>
      <description>&lt;h1 id=&#34;install-img2kvm&#34;&gt;Install img2kvm&lt;/h1&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;cd /root&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;wget -c https://download.margrop.net/d/oneindex/network/PVE/img2kvm -O img2kvm&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;chmod +x img2kvm&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;</description>
    </item>
    <item>
      <title>Solution to PVE upgrade failure due to insufficient boot space</title>
      <link>https://blog.margrop.net/en/post/pve-boot-space-not-enough-fail-upgrade/</link>
      <pubDate>Sun, 17 Jan 2021 19:25:59 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/pve-boot-space-not-enough-fail-upgrade/</guid>
      <description>During the default installation, the space allocated by proxmox to /boot is less than 300M. The iteration of proxmox is very fast, and /boot can easily be filled up. If you are not careful, the upgrade will fail. The only way is to manually delete the old kernel.&#xA;Delete old kernel proxmox is based on debian. Every time you use apt update &amp;amp;&amp;amp; apt dist-upgrade, debian&amp;rsquo;s linux-image and pve-kernel will be automatically installed.</description>
    </item>
  </channel>
</rss>
