Recent content by powersupport

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

This is results @alexskysilk root@pVE-04:~# cat /etc/pve/storage.cfg dir: local path /var/lib/vz content backup,vztmpl,iso lvmthin: local-lvm thinpool data vgname pve content images,rootdir lvm: pVE-DataStore vgname PVE-DS01 content rootdir,images saferemove 0 shared 1 esxi: esxi02 server...

This looks more like a cache path / mount issue than an S3 problem. When PBS marks an S3 datastore as “unavailable,” it’s usually because the local cache directory isn’t accessible or doesn’t match what PBS expects. Here are a few things to check: 1. Verify the new disk is mounted correctly...

Hi, This looks like the NFS storage is temporarily disconnecting during backup. Since it happens on different nodes and VMs, it’s likely a network or NFS mount issue, not the VM itself. Please check NFS connectivity, server logs, and mount stability on /mnt/pve/dm5000h.

We have set up a single-node Proxmox environment with storage backed by an FC LUN. Two storage types are configured on it: one as LVM and the other as directory storage. Recently, we attempted to migrate a VM from VMware to Proxmox. We tried both the Proxmox migration tool and manually...

This issue does not look like a CPU or RAM problem. The behavior you described (GUI freezing for 10–15 minutes and then recovering) is usually related to storage I/O delays. Since you have around 200 VMs, it’s possible that too many backups running at the same time are overloading the storage...

Hi, This usually happens when the server is a bit busy during the scheduled backup time. Since manual backups work fine, the issue is likely due to higher load when the automatic backups run. You can try running backups at a different time or avoid running multiple backups together.

Hi, From the config, the VM is currently showing lock: backup, which suggests a previous backup task may be stuck. That alone can prevent new backups from progressing. Also, since the disk is QCOW2 on NFS and you’re using snapshot mode, it can sometimes hang at 0% if there’s an issue with...