From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: "Xiaoyao Li" <xiaoyao.li@intel.com>,
qemu-stable@nongnu.org,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"Brijesh Singh" <brijesh.singh@amd.com>,
"Pankaj Gupta" <pankaj.gupta@amd.com>
Subject: Re: [PATCH] physmem: replace assertion with error
Date: Mon, 17 Feb 2025 13:28:43 +0100 [thread overview]
Message-ID: <051e10cb-7cb1-430d-956d-b508b7f7db5a@linaro.org> (raw)
In-Reply-To: <20250217120812.396522-1-pbonzini@redhat.com>
Hi Paolo,
On 17/2/25 13:08, Paolo Bonzini wrote:
> It is possible to start QEMU with a confidential-guest-support object
> even in TCG mode. While there is already a check in qemu_machine_creation_done:
>
> if (machine->cgs && !machine->cgs->ready) {
> error_setg(errp, "accelerator does not support confidential guest %s",
> object_get_typename(OBJECT(machine->cgs)));
> exit(1);
> }
>
> the creation of RAMBlocks happens earlier, in qemu_init_board(), if
> the command line does not override the default memory backend with
> -M memdev. Then the RAMBlock will try to use guest_memfd (because
> machine_require_guest_memfd correctly returns true; at least correctly
> according to the current implementation) and trigger the assertion
> failure for kvm_enabled(). This happend with a command line as
> simple as the following:
>
> qemu-system-x86_64 -m 512 -nographic -object sev-snp-guest,reduced-phys-bits=48,id=sev0 \
> -M q35,kernel-irqchip=split,confidential-guest-support=sev0
> qemu-system-x86_64: ../system/physmem.c:1871: ram_block_add: Assertion `kvm_enabled()' failed.
I'd expect sev-snp-guest to bail out early enough.
Is a KVM-enabled check in sev_snp_guest_instance_init() missing?
> Cc: Xiaoyao Li <xiaoyao.li@intel.com>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> system/physmem.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/system/physmem.c b/system/physmem.c
> index 67c9db9daad..1ddf9fb10d0 100644
> --- a/system/physmem.c
> +++ b/system/physmem.c
> @@ -1882,7 +1882,11 @@ static void ram_block_add(RAMBlock *new_block, Error **errp)
> if (new_block->flags & RAM_GUEST_MEMFD) {
> int ret;
>
> - assert(kvm_enabled());
> + if (!kvm_enabled()) {
> + error_setg(errp, "cannot set up private guest memory for %s: KVM required",
> + object_get_typename(OBJECT(current_machine->cgs)));
Common code should be SW vs HW accel, so IMHO your check
should go within sev_snp_guest_instance_init(), removing
the assertion here. That said I have no clue about SEV.
> + goto out_free;
> + }
> assert(new_block->guest_memfd < 0);
>
> ret = ram_block_discard_require(true);
next prev parent reply other threads:[~2025-02-17 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 12:08 [PATCH] physmem: replace assertion with error Paolo Bonzini
2025-02-17 12:19 ` Daniel P. Berrangé
2025-02-17 12:28 ` Philippe Mathieu-Daudé [this message]
2025-02-17 13:15 ` Paolo Bonzini
2025-02-18 1:30 ` Xiaoyao Li
2025-02-18 15:45 ` David Hildenbrand
2025-02-19 6:39 ` Gupta, Pankaj
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=051e10cb-7cb1-430d-956d-b508b7f7db5a@linaro.org \
--to=philmd@linaro.org \
--cc=berrange@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=mtosatti@redhat.com \
--cc=pankaj.gupta@amd.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=xiaoyao.li@intel.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;
as well as URLs for NNTP newsgroup(s).