[Bug] Cross-Cluster Replication fails

[ccesario]

Describe the bug

Cross-Cluster Replication fails when creating/running a DR replication job for a VM. The job starts the tunnel and begins the migration phase, but aborts while copying the local disk image with the following error:

ERROR: no export formats for '<REDACTED-STORAGE>:vm-<ID>-disk-0.qcow2' - check storage plugin support!
TASK ERROR: migration aborted

Steps to Reproduce

1. Open a VM in the source PegaProx/Proxmox cluster.
2. Go to Replication.
3. In Cross-Cluster Replication, click Add DR Job.
4. Select the target cluster.
5. Select a target storage of type lvm.
6. Configure the network mapping, schedule and retention.
7. Create/run the replication job.
8. Check the task viewer/log output.

Expected behavior

The Cross-Cluster Replication job should create/run successfully and copy the VM disk to the target cluster/storage.

If the selected target storage type is not supported for this replication/export workflow, the UI should prevent selecting it or show a clear validation error before starting the job.

Environment

• PegaProx Version: Beta 0.9.14
• Installation Method: Appliance
• Behind Reverse Proxy? No
• UI? Corporate

Logs

remote: started tunnel worker '<REDACTED>'
tunnel: -> sending command "version" to remote
tunnel: <- got reply
Use of uninitialized value $reader_stderr in <HANDLE> at /usr/share/perl5/PVE/Tunnel.pm line 77.
readline() on unopened filehandle at /usr/share/perl5/PVE/Tunnel.pm line 77.
local WS tunnel version: 2
remote WS tunnel version: 2
minimum required WS tunnel version: 2
websocket tunnel started
starting migration of VM <ID> to node '<REDACTED-TARGET-NODE>' (<REDACTED-IP>)
tunnel: -> sending command "bwlimit" to remote
tunnel: <- got reply
Use of uninitialized value $reader_stderr in <HANDLE> at /usr/share/perl5/PVE/Tunnel.pm line 77.
readline() on unopened filehandle at /usr/share/perl5/PVE/Tunnel.pm line 77.
found local disk '<REDACTED-STORAGE>:vm-<ID>-disk-0.qcow2' (attached)
copying local disk images
ERROR: no export formats for '<REDACTED-STORAGE>:vm-<ID>-disk-0.qcow2' - check storage plugin support!
aborting phase 1 - cleanup resources
tunnel: -> sending command "quit" to remote
tunnel: <- got reply
Use of uninitialized value $reader_stderr in <HANDLE> at /usr/share/perl5/PVE/Tunnel.pm line 77.
readline() on unopened filehandle at /usr/share/perl5/PVE/Tunnel.pm line 77.
ERROR: migration aborted: no export formats for '<REDACTED-STORAGE>:vm-<ID>-disk-0.qcow2' - check storage plugin support!
TASK ERROR: migration aborted

Screenshots

Checklist

• I have searched existing issues to make sure this is not a duplicate
• I am using the latest version of PegaProx

[MrMasterbay]

Hi @ccesario ,

that is nothing that we can fix I'm afraid. This seems like a Proxmox Issue. Feel free to open a Proxmox Ticket on there support but I'm afraid they simple don't support that

On "the UI should block the incompatible target storage" I get the intent, but we can't do that reliably. There's no stable list of which source-format → target-storage combos remote-migrate actually supports; it shifts per PVE version and per storage plugin. Reimplementing and babysitting a
shadow copy of Proxmox's export/import matrix would break on every point release and be worse than the clear PVE error you already get.

Best path: a request on bugzilla.proxmox.com for remote-migrate export support for that combo, or pick a target storage PVE can import into (a file/dir-based target for a qcow2 source works). If Proxmox ever publishes a supported-combo list we can query, I'll happily wire a pre-check to it until then it'd just be trial-and-error for everyone.

PegaProx is a donation-funded side project (opencollective.com/pegaprox)