Ani Sinha <[email protected]> writes: >> On 19 Feb 2026, at 2:25 PM, Markus Armbruster <[email protected]> wrote: >> >> Ani Sinha <[email protected]> writes: >> >>> Through the new 'confidential-guest-reset' property, control plane should be >>> able to detect if the hypervisor supports x86 confidential guest resets. >>> Older >>> hypervisors that do not support resets will not have this property >>> populated. >> >> 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 confidential > guests. That is, the host should support confidential technology. The host > kernel/distribution should support confidential technologies. Plus the guest > should support confidential technologies. There is nothing additionally > 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? >> >>> Suggested-by: Daniel P. Berrangé <[email protected]> >>> Signed-off-by: Ani Sinha <[email protected]> >> >> Patch looks sane. >>
