determining the usage values for the current config. pending values are taken into account if they are higher than the current value only, else it would be possible to easily circumvent config limits by setting non-hotpluggable pending values.
Signed-off-by: Fabian Grünbichler <f.gruenbich...@proxmox.com> --- PVE/QemuConfig.pm | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/PVE/QemuConfig.pm b/PVE/QemuConfig.pm index ca30eda0..550ec941 100644 --- a/PVE/QemuConfig.pm +++ b/PVE/QemuConfig.pm @@ -572,4 +572,34 @@ sub has_cloudinit { return $found; } +# for determining pool usage vs limits +# +# this gives the higher of pending or currently configured +sub get_pool_usage { + my ($class, $conf) = @_; + + my $usage = {}; + + my $get_max = sub { + my $max = 0; + + for my $curr (@_) { + $max = $curr if defined($curr) && $curr > $max; + } + + return $max; + }; + + $usage->{sockets} = $get_max->(($conf->{pending}->{sockets}, $conf->{sockets}, 1)); + $usage->{cores} = $get_max->(($conf->{pending}->{cores}, $conf->{cores}, 1)); + $usage->{cpu} = $usage->{sockets} * $usage->{cores}; + $usage->{mem} = $get_max->(( + get_current_memory($conf->{pending}->{memory}), + get_current_memory($conf->{memory}) + )); + $usage->{mem} *= 1024*1024; + + return $usage; +} + 1; -- 2.39.2 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel