From: Tom Lendacky <[email protected]> In prep for AP booting, require the use of in-kernel irqchip support. This lessens the Qemu support burden required to boot APs.
Cc: Paolo Bonzini <[email protected]> Cc: Richard Henderson <[email protected]> Cc: Eduardo Habkost <[email protected]> Reviewed-by: Dr. David Alan Gilbert <[email protected]> Signed-off-by: Tom Lendacky <[email protected]> Reviewed-by: Venu Busireddy <[email protected]> Message-Id: <e9aec5941e613456f0757f5a73869cdc5deea105.1611682609.git.thomas.lenda...@amd.com> Signed-off-by: Paolo Bonzini <[email protected]> --- target/i386/sev.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/target/i386/sev.c b/target/i386/sev.c index dc0e53019b..35b9259bfc 100644 --- a/target/i386/sev.c +++ b/target/i386/sev.c @@ -753,6 +753,12 @@ int sev_kvm_init(ConfidentialGuestSupport *cgs, Error **errp) sev->api_minor = status.api_minor; if (sev_es_enabled()) { + if (!kvm_kernel_irqchip_allowed()) { + error_report("%s: SEV-ES guests require in-kernel irqchip support", + __func__); + goto err; + } + if (!(status.flags & SEV_STATUS_FLAGS_CONFIG_ES)) { error_report("%s: guest policy requires SEV-ES, but " "host SEV-ES support unavailable", -- 2.29.2
