[GH-ISSUE #84] cross-cluster migrate (lvm -> zfs) #61

New issue

Closed

opened 2026-03-02 15:47:38 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 15:47:38 +03:00

Owner

Originally created by @devnull-vs on GitHub (Feb 25, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/84

same problem as in Proxmox data center manager

2026-02-26 00:16:35 remote: started tunnel worker 'UPID:pve1:00113795:1557C2C4:699F82D3:qmtunnel:567:root@pam!pegaprox-migrate-1772061395:'
tunnel: -> sending command "version" to remote
tunnel: <- got reply
2026-02-26 00:16:35 local WS tunnel version: 2
2026-02-26 00:16:35 remote WS tunnel version: 2
2026-02-26 00:16:35 minimum required WS tunnel version: 2
websocket tunnel started
2026-02-26 00:16:35 starting migration of VM 107 to node 'pve1' (172.17.172.4)
tunnel: -> sending command "bwlimit" to remote
tunnel: <- got reply
2026-02-26 00:16:35 found local disk 'local:107/vm-107-disk-0.qcow2' (attached)
2026-02-26 00:16:35 copying local disk images
tunnel: -> sending command "disk-import" to remote
tunnel: <- got reply
2026-02-26 00:16:35 ERROR: error - tunnel command '{"migration_snapshot":0,"volname":"vm-567-disk-0.qcow2","cmd":"disk-import","allow_rename":"1","storage":"raid0","export_formats":"qcow2+size","with_snapshots":1,"format":"qcow2"}' failed - failed to handle 'disk-import' command - unsupported format 'qcow2' for storage type zfspool
2026-02-26 00:16:35 aborting phase 1 - cleanup resources
tunnel: -> sending command "quit" to remote
tunnel: <- got reply
2026-02-26 00:16:36 ERROR: migration aborted (duration 00:00:01): error - tunnel command '{"migration_snapshot":0,"volname":"vm-567-disk-0.qcow2","cmd":"disk-import","allow_rename":"1","storage":"raid0","export_formats":"qcow2+size","with_snapshots":1,"format":"qcow2"}' failed - failed to handle 'disk-import' command - unsupported format 'qcow2' for storage type zfspool
TASK ERROR: migration aborted

Originally created by @devnull-vs on GitHub (Feb 25, 2026). Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/84 same problem as in Proxmox data center manager ```shell 2026-02-26 00:16:35 remote: started tunnel worker 'UPID:pve1:00113795:1557C2C4:699F82D3:qmtunnel:567:root@pam!pegaprox-migrate-1772061395:' tunnel: -> sending command "version" to remote tunnel: <- got reply 2026-02-26 00:16:35 local WS tunnel version: 2 2026-02-26 00:16:35 remote WS tunnel version: 2 2026-02-26 00:16:35 minimum required WS tunnel version: 2 websocket tunnel started 2026-02-26 00:16:35 starting migration of VM 107 to node 'pve1' (172.17.172.4) tunnel: -> sending command "bwlimit" to remote tunnel: <- got reply 2026-02-26 00:16:35 found local disk 'local:107/vm-107-disk-0.qcow2' (attached) 2026-02-26 00:16:35 copying local disk images tunnel: -> sending command "disk-import" to remote tunnel: <- got reply 2026-02-26 00:16:35 ERROR: error - tunnel command '{"migration_snapshot":0,"volname":"vm-567-disk-0.qcow2","cmd":"disk-import","allow_rename":"1","storage":"raid0","export_formats":"qcow2+size","with_snapshots":1,"format":"qcow2"}' failed - failed to handle 'disk-import' command - unsupported format 'qcow2' for storage type zfspool 2026-02-26 00:16:35 aborting phase 1 - cleanup resources tunnel: -> sending command "quit" to remote tunnel: <- got reply 2026-02-26 00:16:36 ERROR: migration aborted (duration 00:00:01): error - tunnel command '{"migration_snapshot":0,"volname":"vm-567-disk-0.qcow2","cmd":"disk-import","allow_rename":"1","storage":"raid0","export_formats":"qcow2+size","with_snapshots":1,"format":"qcow2"}' failed - failed to handle 'disk-import' command - unsupported format 'qcow2' for storage type zfspool TASK ERROR: migration aborted ```

kerem closed this issue

2026-03-02 15:47:38 +03:00

kerem commented

2026-03-02 15:47:39 +03:00

Author

Owner

@MrMasterbay commented on GitHub (Feb 26, 2026):

Hi @devnull-vs ,

if the problem already appeared in pdm please open a ticket at Proxmox themselves. We use here their API they would need to fix that.

There is nothing that we could do in this case.
Best Regards,
Nico

@MrMasterbay commented on GitHub (Feb 26, 2026): Hi @devnull-vs , if the problem already appeared in pdm please open a ticket at Proxmox themselves. We use here their API they would need to fix that. There is nothing that we could do in this case. Best Regards, Nico

kerem commented

2026-03-02 15:47:39 +03:00

Author

Owner

@devnull-vs commented on GitHub (Feb 26, 2026):

https://bugzilla.proxmox.com/show_bug.cgi?id=6087

@devnull-vs commented on GitHub (Feb 26, 2026): https://bugzilla.proxmox.com/show_bug.cgi?id=6087

kerem referenced this issue

2026-03-02 15:47:54 +03:00

[PR #61] [MERGED] fix(update): restore 0700 permissions on config/ and ssl/ after update #99