Recent content by powersupport

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 block device directly into /dev/rbdX. For LXC...

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 to know: Is there a supported upgrade path from...

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 automatically. On your single daily job, set the...

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 a VM configuration issue. Could you please check...

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 the migration network and conntrack toggles aren't...

Hi, Yes, to some extent. The best approach is to use a dedicated PBS API token with only the permissions needed to create backups, and do not grant delete privileges. Let PBS handle pruning based on its retention policy. However, if someone has full root/admin access to both Proxmox VE and...

Hi all, We are experiencing an issue on several Proxmox VE 9 nodes where management network connectivity is lost following a firewall failover, firewall reload, or temporary firewall service interruption on our Palo Alto PA1410 HA pair. Symptoms: The affected Proxmox node becomes unreachable...

Hi, I can understand your concern. In your case, VM B is not really a separate machine but a refreshed copy of VM A, so keeping the same UUID would help avoid licensing issues and reduce administrative work. As far as I know, there is currently no option in Proxmox to keep the UUID...

Hi, This sounds more like a hardware/BIOS issue than a Proxmox issue, since the system works fine after a full power off and only has trouble on reboot. You may want to check the BIOS boot settings again (especially Fast Boot / boot mode), and also confirm whether the SSD is being detected...

Hi, Unfortunately, this is currently not possible in Proxmox. The VM.Backup privilege allows users to view, restore, and also delete backups. There is no separate restore-only permission available at the moment.

When you delete a snapshot, Proxmox has to merge the changes back into the base .qcow2 file. Because it's on NFS, QEMU forces every single write to be completely synchronous over the network. This locks up the VM's disk controller and causes the freeze, regardless of how fast your Optane and...

Hi, It looks like the tape-restored snapshot may still have some locked or protected metadata. You may try: Running datastore verify Running garbage collection Checking for active tasks/locks Restarting proxmox-backup-proxy If normal removal still fails, manual cleanup may be required after...

Hi, This is expected in Proxmox. When a VM is shut down from the GUI, its disk is fully deactivated, so Veeam can’t see it. Using: qm stop 114 --keepactive works because it keeps the disk active even when the VM is off. a way to make --keepactive the default in the GUI. As a workaround...

Hi, Anyone advice on this issue? Thank you