On Thu, 22 Jan 2026 13:10:18 +0100, Fiona Ebner wrote:
> While in practice, it should be quite rare and unexpected for the
> get_memory_stat() to fail, a single failing call should not fail the
> whole pvestatd collection for VMs or even the single
> '/qemu/{vmid}/status/current' API call for the affected VM, which e.g.
> leads to the display for the VM in the UI being inaccessible.
>
> One situation where it can happen is manually invoking the command
> given by 'qm showcmd', because the process won't be part of the usual
> systemd scope.
>
> [...]
Applied, thanks!
[1/1] vm status: guard get_memory_stat() call with eval
commit: 61d76518025f0ef3f7c5e6525af0f68e11bfee60
Best regards,
--
Fabian Grünbichler <[email protected]>
_______________________________________________
pve-devel mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
