From: Eric Auger <eric.auger@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: eric.auger.pro@gmail.com, qemu-devel@nongnu.org,
qemu-arm@nongnu.org, miguel.luis@oracle.com,
richard.henderson@linaro.org, maz@kernel.org,
gkulkarni@amperecomputing.com,
gankulkarni@os.amperecomputing.com, hi@alyssa.is
Subject: Re: [PATCH v9 0/5] ARM Nested Virt Support
Date: Thu, 10 Jul 2025 14:38:05 +0200 [thread overview]
Message-ID: <06350d07-7c4f-4ed9-abc1-a3d447a814f8@redhat.com> (raw)
In-Reply-To: <CAFEAcA8UGHWLY-OpSZ2CP=LY7AynO_YxS27BzLadegL40VgNYA@mail.gmail.com>
Hi Peter,
On 7/10/25 12:42 PM, Peter Maydell wrote:
> On Mon, 7 Jul 2025 at 17:41, Eric Auger <eric.auger@redhat.com> wrote:
>> This is candidate for 10.1.
>>
>> For gaining virt functionality in KVM accelerated L1, The host needs to
>> be booted with "kvm-arm.mode=nested" option and qemu needs to be invoked
>> with: -machine virt,virtualization=on.
>>
>> This series can be found at:
>> https://github.com/eauger/qemu/tree/v10.0.0-nv-v9
>> previous:
>> https://github.com/eauger/qemu/tree/v10.0.0-nv-v8
>
> Applied to target-arm.next, thanks. I'm going to squash in
> this change
>
> --- a/hw/arm/virt.c
> +++ b/hw/arm/virt.c
> @@ -2248,8 +2248,13 @@ static void machvirt_init(MachineState *machine)
> exit(1);
> }
>
> - if (vms->virt && !(kvm_enabled() && kvm_arm_el2_supported()) &&
> - !tcg_enabled() && !qtest_enabled()) {
> + if (vms->virt && kvm_enabled() && !kvm_arm_el2_supported()) {
> + error_report("mach-virt: host kernel KVM does not support providing "
> + "Virtualization extensions to the guest CPU");
> + exit(1);
> + }
> +
> + if (vms->virt && !kvm_enabled() && !tcg_enabled() && !qtest_enabled()) {
> error_report("mach-virt: %s does not support providing "
> "Virtualization extensions to the guest CPU",
> current_accel_name());
>
> so we can distinguish "QEMU doesn't support KVM EL2" from
> "QEMU supports it but the kernel does not".
Sure.
Thanks!
Eric
>
> -- PMM
>
prev parent reply other threads:[~2025-07-10 12:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 16:40 [PATCH v9 0/5] ARM Nested Virt Support Eric Auger
2025-07-07 16:40 ` [PATCH v9 1/5] hw/arm: Allow setting KVM vGIC maintenance IRQ Eric Auger
2025-07-07 16:40 ` [PATCH v9 2/5] target/arm/kvm: Add helper to detect EL2 when using KVM Eric Auger
2025-07-07 16:40 ` [PATCH v9 3/5] target/arm: Enable feature ARM_FEATURE_EL2 if EL2 is supported Eric Auger
2025-07-07 16:40 ` [PATCH v9 4/5] hw/arm/arm_gicv3_kvm: Add a migration blocker with kvm nested virt Eric Auger
2025-07-10 14:04 ` Philippe Mathieu-Daudé
2025-07-10 14:10 ` Eric Auger
2025-07-10 15:18 ` Philippe Mathieu-Daudé
2025-07-10 15:18 ` Peter Maydell
2025-07-07 16:40 ` [PATCH v9 5/5] hw/arm/virt: Allow virt extensions with KVM Eric Auger
2025-07-10 10:42 ` [PATCH v9 0/5] ARM Nested Virt Support Peter Maydell
2025-07-10 12:38 ` Eric Auger [this message]
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=06350d07-7c4f-4ed9-abc1-a3d447a814f8@redhat.com \
--to=eric.auger@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=gankulkarni@os.amperecomputing.com \
--cc=gkulkarni@amperecomputing.com \
--cc=hi@alyssa.is \
--cc=maz@kernel.org \
--cc=miguel.luis@oracle.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
/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).