Thanks, glad you like it. An official plug-in API for the web UI, like the storage plugin API, would indeed be the proper solution, and an explicit opt-in with a "no support" warning, as you describe, sounds reasonable to me.
Until something...
Either buy 141 GB more RAM or reduce the max RAM for this VM 115 GB. IDK how much PVE itself needs, maybe 10GB is enough. I dont think a big swap partition would be enough. AFAIK it cant swap out actively used RAM, can it ?
Please don't do this, the HA stack works the way it does to prevent data corruption which can easily happen if HA is enabled and you remove the quorum requirement.
If you want to run a 2-node cluster you need to setup a QDevice. You can read...
This also happened to me, when our NFS-ISO Storage went down, on all Cluster Nodes.
It was fixed after restarting the following Services:
service pve-cluster restart
service pvestatd restart
service pveproxy restart
Edit:
One Node, for some...
A short update for anyone who followed this thread, since a few things you asked about have landed:
Incremental backups that read only what changed (BackupZit 0.44). Running VMs on LVM-thin, ZFS, Ceph RBD or qcow2 now use QEMU dirty bitmaps...
Why would you give the VM more memory than the physical host has?
If you want to run like that, configure a healthy swap file on the host, preferably high-endurance, mirrored NVMe.
Can someone further clarify this "temporary" storage/overlay? Which filesystems and backup types does it happen under? With or without fleecing, or both?
I was under the impression that the VM writes during a backup go to the base virtual disk...
The dirty bitmap is definitely a stick in the eye that hopefully will be improved soon. A lot of people would be happy even if it's opt-in with warnings and strict requirements, such as a mandatory full backup every X number of...
There are dozen of entries in syslog like this:
2026-11-13T10:57:30.054103+01:00 mailgw kernel: audit: type=1400 audit(1794563850.052:46216): apparmor="DENIED" operation="open" class="file" profile="/usr/sbin/clamd"...
Hi, @westrangers
You probably can use the trick with chattr described e.g. here:
https://forum.proxmox.com/threads/how-to-dismount-and-remount-usb-drive-for-manual-backups-on-pve.182545/#post-848004
Maybe a bit late to the party, but tested and working fine on a Friendlyelec NanoPC-T6 with EDK2-RK3588 UEFI built from current trunk as of writing. EDK2 on onboard SPI NOR flash and PVE on NVMe SSD.
Settings in EDK2:
Device manager -> Rockchip...
Interesting approach. A few thoughts from running something similar:
The dirty bitmap only lives in the running QEMU process. A full shutdown or a restart of the VM throws it away, so the next backup has to read the whole disk again. PBS...
Both things can be true, but for what you're describing — CPU jumps just from being logged into the UI, console closed — it's almost certainly just the web interface polling overhead.
When you're signed into Proxmox, the backend keeps hitting...
To clarify, backups during production hours CAN be tricky in some cases. Probably the two biggest issues and their solutions:
- extra load caused by the backups: greatly limit the number of simultaneous backups and throttle the transfer...
Interesting approach. A few thoughts from running something similar:
The dirty bitmap only lives in the running QEMU process. A full shutdown or a restart of the VM throws it away, so the next backup has to read the whole disk again. PBS...
A few operational details still need attention.
Who owns the encryption keys? If the customer loses theirs, the offsite backups are useless. If you hold them, you're taking on the responsibility of protecting all their data.
The initial full...