Recent content by powersupport

Hi, This usually happens when the Proxmox GUI or services don’t refresh the VM list properly, even though the VMs are still running. You can try restarting Proxmox services instead of rebooting: systemctl restart pve-cluster pvedaemon pvestatd pveproxy Also check disk space and VM config...

After the update, Proxmox now handles container mount points more strictly. This mainly affects unprivileged containers. Mounted folders now show up as root:root inside the container, so services like MySQL can’t access their files. If a mount point is set to read-only, the container may fail...

This VM runs Blue Iris, which heavily uses the GPU all the time (video decoding, encoding, and AI processing). Other VMs using the same Intel GPU are fine because they don’t use the GPU as heavily or continuously. What appears to be happening is: The Intel GPU virtual function sometimes stops...

Hi, In Proxmox VE 8.4, the GUI gets the backup list from the Proxmox Backup Server (PBS). The “communication failure (0)” usually means a temporary connection or timeout issue to PBS. You can check logs here: On Proxmox VE /var/log/pveproxy/error.log /var/log/syslog journalctl -u pveproxy On...

Hi, This speed is normal for your setup. Backups are slow because: The backup system is running inside a virtual machine The disk is a USB hard drive The storage is going through another device (Raspberry Pi) Backup software does more work than a normal file copy, so even if copying a file...

Hi, Thank you for the detailed explanation and for sharing your field-tested procedure. Before we communicate this back to the customer, we just want to double-check with the Proxmox community: Is this manual cleanup approach (Safe Mode, removing VMware services/drivers, then installing...

Hi, After migrating Windows VMs from VMware ESXi to Proxmox, we are seeing VMware Tools errors on the guest OS. Guest OS: Windows Server 2016 / 2019 / 2022 / 2025 Could you please advise: The recommended way to manually remove VMware Tools on Windows after migration Any drivers or services...

Hi, Since other VMs back up fine to the same PBS, this looks VM-specific, not a PBS issue. The error happens before the backup task starts, which often points to: Corrupted incremental / dirty bitmap state Snapshot issue on that VM Small config difference compared to the working VMs Things...

We try to curl with both IP and hostname, but there is an error stating that there are SSL ceritifcate problem: self-signed certificate. Currently, we have 2 certificates configured on our proxmox mail relay server. I have attached the screenshots for analysis. Able to help take a look?

This is not a kernel issue. The ZFS storage was missing support for cloud-init disks. In /etc/pve/storage.cfg, the ZFS pool did not include cloudinit in the content types: zfspool: proxmox content images,rootdir After updating it to: zfspool: proxmox content...

Hi, Thanks for the clarification. So to confirm: • New VMs already include Microsoft UEFI CA 2023 • qm enroll-efi-keys is only for older VMs • Windows Server is supported when OS Type and EFI config are correct • No further action required unless dealing with legacy VMs I’ll relay this to...

Hi, This is normal. Disk format options depend on the storage type. LVM / ZFS / Ceph → only raw Directory / NFS → qcow2 is available Your storage only supports raw, so no other options are shown. Check Datacenter → Storage to see the storage type.

Hi, Thanks for confirming. Understood — so at the moment `qm enroll-efi-keys` only applies to Windows 10/11, and Windows Server editions are intentionally excluded for now. We’ll rely on Windows Update inside the guest for Server VMs and wait for official support or guidance for manual...

This error is caused by a leftover mount directory from a failed snapshot, which started happening after the Proxmox 9 upgrade. The key message is: This means Proxmox is trying to mount the snapshot, but the mount directory already contains files from a previous failed backup. To Fix this...

Hi all, Thank you for the detailed explanations so far — this helped a lot. Just to double-confirm my understanding: • It is expected that older EFI vars (created before the recent updates) may not contain "Microsoft UEFI CA 2023". • Newly created Windows VMs on Proxmox VE 9 with updated...