public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>,
	"Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server] api: add 'allow-ksm' to memory options
Date: Tue, 18 Nov 2025 11:22:20 +0100	[thread overview]
Message-ID: <5772d1aa-85c6-4d00-b7b7-624b0003a90b@proxmox.com> (raw)
In-Reply-To: <1763460696.90n4lepto7.astroid@yuna.none>

Am 18.11.25 um 11:12 AM schrieb Fabian Grünbichler:
> On November 18, 2025 11:08 am, Fiona Ebner wrote:
>> Am 18.11.25 um 10:42 AM schrieb Fabian Grünbichler:
>>> else it is treated as root-only parameter, and since the UI will set/clear it
>>> by default, that makes memory-editing in its entirety root-only.
>>
>> Should it be editable by users with "just" VM.Config.Memory? One main
>> use case is security-related to avoid side-channel attacks. If the
>> answer is no, we should fix the UI of course ;)
> 
> IMHO, yes. it is the default after all, and its purpose is to protect
> this VM against other co-located guests, not against other admins that
> are allowed to (re-)configure my VM.

Yes, good point :)


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  reply	other threads:[~2025-11-18 10:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18  9:42 Fabian Grünbichler
2025-11-18 10:08 ` Fiona Ebner
2025-11-18 10:12   ` Fabian Grünbichler
2025-11-18 10:22     ` Fiona Ebner [this message]
2025-11-18 13:30 ` Thomas Lamprecht

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=5772d1aa-85c6-4d00-b7b7-624b0003a90b@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=f.gruenbichler@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal