From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Daniel Kral <d.kral@proxmox.com>,
Daniel Herzig <d.herzig@proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server] api: vmlist: add plugged cpu count to vmlist table
Date: Fri, 17 Jan 2025 16:27:31 +0100 [thread overview]
Message-ID: <36eb1444-2d84-4461-a3b7-d6e2705fee97@proxmox.com> (raw)
In-Reply-To: <10c1643f-c7b1-4afd-8cc5-253a3546c018@proxmox.com>
Am 17.01.25 um 16:10 schrieb Daniel Kral:
> What do you think about fixing the problem from the other side: I could
> do a follow up where it's not possible to actively assign a VM more
> resources than currently available, since it would not boot anyway? I
> think there's a negligible amount of users who'd want to configure more
> resources and only later upgrade to the required primary memory or a
> heavier CPU (wrt to their core count).
Such a VM might not boot on it's current node, but it could boot on
another node with more CPU cores. Often not a big issue, but we avoid
such restrictions as they often create more friction without providing
that much help – a UI only hint in case of setting more cores than the
current node supports might be better here.
Maybe best to just ignore the glitch in the output for now, or indeed
duplicate the calculation, or look into why vmstatus does it that way
and see if it could be unclamped there (or a new property is warranted).
btw. you use the "api" prefix for this patch, but it should be "cli",
as this is not changing the (REST) API in any way.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-01-17 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 17:09 Daniel Kral
2025-01-13 9:45 ` Daniel Herzig
2025-01-17 15:10 ` Daniel Kral
2025-01-17 15:27 ` Thomas Lamprecht [this message]
2025-01-17 16:25 ` Daniel Kral
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36eb1444-2d84-4461-a3b7-d6e2705fee97@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.herzig@proxmox.com \
--cc=d.kral@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox