From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 34FCDE9A03B for ; Thu, 19 Feb 2026 09:28:31 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1vt0K3-0004Em-K1; Thu, 19 Feb 2026 04:27:47 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1vt0K1-0004EZ-UH for qemu-devel@nongnu.org; Thu, 19 Feb 2026 04:27:45 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1vt0K0-0000Vt-GL for qemu-devel@nongnu.org; Thu, 19 Feb 2026 04:27:45 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1771493262; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=S2GCB5kKchNZzJ4zmQdq9r21LqvZXDnJfHDnX9TsjWI=; b=ExnpPYwIjZBZsLb7H2reveB8dd7UmzmrLXGr/VEgs2HrQ5Hs8ex/v92Q0KwsX9JwG/w6CE +5dgpUlRjIBcVGHHTKXnIgwWkNxVxDz6014c4N9qhdWsrbSGTFh4DiIIHwfdTjQqWt4AjO 2+w979RS63LQSLm5rn/x+wr2eUD7oJw= Received: from mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-605-PwauhJpEPE-NyOE558yWrg-1; Thu, 19 Feb 2026 04:27:41 -0500 X-MC-Unique: PwauhJpEPE-NyOE558yWrg-1 X-Mimecast-MFC-AGG-ID: PwauhJpEPE-NyOE558yWrg_1771493260 Received: from mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 979611800763; Thu, 19 Feb 2026 09:27:40 +0000 (UTC) Received: from blackfin.pond.sub.org (unknown [10.45.242.14]) by mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 327C31955F01; Thu, 19 Feb 2026 09:27:40 +0000 (UTC) Received: by blackfin.pond.sub.org (Postfix, from userid 1000) id BBF6E21E692D; Thu, 19 Feb 2026 10:27:37 +0100 (CET) From: Markus Armbruster To: Ani Sinha Cc: Markus Armbruster , Paolo Bonzini , Daniel Berrange , Eduardo Habkost , Eric Blake , Gerd Hoffmann , qemu-devel Subject: Re: [PATCH v5 33/34] qom: add 'confidential-guest-reset' property for x86 confidential vms In-Reply-To: (Ani Sinha's message of "Thu, 19 Feb 2026 14:42:36 +0530") References: <20260218114233.266178-1-anisinha@redhat.com> <20260218114233.266178-34-anisinha@redhat.com> <87wm093yer.fsf@pond.sub.org> Date: Thu, 19 Feb 2026 10:27:37 +0100 Message-ID: <87pl613wxi.fsf@pond.sub.org> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 3.0 on 10.30.177.12 Received-SPF: pass client-ip=170.10.129.124; envelope-from=armbru@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.043, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, GB_FAKE_RF=0.754, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: qemu development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Ani Sinha writes: >> On 19 Feb 2026, at 2:25=E2=80=AFPM, Markus Armbruster wrote: >>=20 >> Ani Sinha writes: >>=20 >>> Through the new 'confidential-guest-reset' property, control plane shou= ld be >>> able to detect if the hypervisor supports x86 confidential guest resets= . Older >>> hypervisors that do not support resets will not have this property popu= lated. >>=20 >> Double-checking... This is an static ability of QEMU, and QEMU alone. >> It does not depend on QEMU's run-time environment (host kernel, ...) or >> the guest. Correct? > > The run time environment is the same as what is needed to spawn confident= ial guests. That is, the host should support confidential technology. The h= ost kernel/distribution should support confidential technologies. Plus the = guest should support confidential technologies. There is nothing additional= ly needed to support resets. There are no additional dependencies with host= kernel/environment and/or the guest etc to support reset. So... if a QEMU with this feature succeeded at starting a confidential guest, then x86 confidential guest reset is definitely supported for that guest. Correct? >>=20 >>> Suggested-by: Daniel P. Berrang=C3=A9 >>> Signed-off-by: Ani Sinha >>=20 >> Patch looks sane. >>=20