Hi,
This is expected behavior. Although both nodes have an LVM storage with the same name, they are still separate local storages. Proxmox does not support storage migration directly from local LVM to local LVM, which is why you see the error
The issue is almost certainly that KRBD (Kernel RBD) is disabled on your vms storage configuration.
Why VMs work, but LXCs don't
VMs access Ceph directly in userspace via QEMU (librbd).
LXCs share the host kernel and need the host to map the...
Hi,
We have a customer currently running Proxmox VE 8.x who would like to upgrade to Proxmox VE 9.2.1 instead of the latest available 9.x release due to compatibility requirements with their Veeam Backup & Replication environment.
We would like...
Hi,
You don't actually need three separate jobs! Having multiple jobs for the same VM causes them to step on each other and prune each other's backups.
The best solution is to use 1 single daily backup job and let Proxmox handle the retention...
Since the host is detecting both USB devices with lsusb, but they are repeatedly resetting and the VM can see them without any traffic passing through, it looks more like a USB passthrough or kernel regression after the PVE 9 upgrade rather than...
Hi,
The error client closed connection to the resume command means that the migration data actually transferred successfully, but the QEMU process on the target node crashed or terminated immediately when trying to resume the VM state.
Since...