惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

J
Java Code Geeks
G
Google Developers Blog
有赞技术团队
有赞技术团队
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Blog — PlanetScale
Blog — PlanetScale
罗磊的独立博客
博客园 - 聂微东
V
Visual Studio Blog
博客园_首页
D
DataBreaches.Net
腾讯CDC
I
InfoQ
F
Fortinet All Blogs
量子位
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
酷 壳 – CoolShell
酷 壳 – CoolShell
博客园 - 【当耐特】
Google DeepMind News
Google DeepMind News
人人都是产品经理
人人都是产品经理
云风的 BLOG
云风的 BLOG
月光博客
月光博客
Recent Announcements
Recent Announcements
MongoDB | Blog
MongoDB | Blog
C
Check Point Blog

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
remote-migration fails between different Storage Backends
invalid@exam · 2026-06-16 · via Proxmox Support Forum

After being advised to use the remote-migration feature to keep QEMU and LXC templates in sync between our three clusters, I have implemented additional remote-migration tasks in our Ansible playbook which is already capable of creating and deploying the OS templates within our primary cluster.

Our two main clusters use identical Ceph Storage, remote-migration works well here.

Mild issue: after the remote-migration the source VM stays locked with state "migration" as I am supplying "--delete 0" parameter because the template should be copied to the other clusters without being removed.

Big issue: When targeting our third cluster, which does not have Ceph Storage but local ZFS storage in each node, I encounter the following error.
ERROR: error - tunnel command '{"export_formats":"raw+size","migration_snapshot":0,"cmd":"disk-import","allow_rename":"1","format":"raw","storage":"zfs-hdd","volname":"base-200-disk-0","with_snapshots":0}' failed - failed to handle 'disk-import' command - no matching import/export format found for storage 'zfs-hdd'

After some research I found this post from 2023:

Hi,
is the source VM's storage also ZFS? Unfortunately, offline disk migration to/from ZFS is only implemented from/to ZFS at the moment. As a workaround, you can try to migrate the VM while it is running (assuming the disk is attached to the VM).

> Unfortunately, offline disk migration to/from ZFS is only implemented from/to ZFS at the moment.

Is this still the case, am I basically stranded here with a half-working concept? :(

One of the things I hit upon today was using `qm disk move` (or pct move-volume in your case) to get around the zfs<-->ceph hatred. Both VM and CT disk migration followed by CT/VM migration worked fine for me from zfs to ceph just now (Jun 16 2026) once I did the disk move and deleted the unusedX from the CT/VM before migration.