qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Auger <eric.auger@redhat.com>
To: Alyssa Ross <hi@alyssa.is>,
	eric.auger.pro@gmail.com, qemu-devel@nongnu.org,
	qemu-arm@nongnu.org, miguel.luis@oracle.com,
	peter.maydell@linaro.org, richard.henderson@linaro.org,
	maz@kernel.org, gkulkarni@amperecomputing.com,
	gankulkarni@os.amperecomputing.com
Subject: Re: [PATCH v5 5/5] hw/arm/virt: Allow virt extensions with KVM
Date: Tue, 17 Jun 2025 16:52:55 +0200	[thread overview]
Message-ID: <6debc836-c55d-406f-a74d-8ea5070b7fba@redhat.com> (raw)
In-Reply-To: <875xgutpuh.fsf@alyssa.is>

Hi Alyssa,
On 6/17/25 4:17 PM, Alyssa Ross wrote:
> Eric Auger <eric.auger@redhat.com> writes:
>
>> From: Haibo Xu <haibo.xu@linaro.org>
>>
>> Up to now virt support on guest has been only supported with TCG.
>> Now it becomes feasible to use it with KVM acceleration.
>>
>> Also check only in-kernel GICv3 is used along with KVM EL2.
>>
>> Signed-off-by: Haibo Xu <haibo.xu@linaro.org>
>> Signed-off-by: Miguel Luis <miguel.luis@oracle.com>
>> Signed-off-by: Eric Auger <eric.auger@redhat.com>
>> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
> Hi!  From what I can tell, this will produce an error on hosts that
> don't support nested virtualization when QEMU is invoked with -accel
> kvm:tcg -machine virtualization=on, but I don't think that's the ideal
Thanks for reporting this issue. This is not an expected behavior. I
will respin hopefully this week so I will have give it a try.

What kind of error msg do you get?

Thanks

Eric
> behaviour.  It would make more sense for it to fall back to the first
> permitted accel option that does support running the machine as
> configured, so if hardware nested virtualization is not supported, it
> should fall back to TCG.
>
> I maintain an OS development environment that includes scripts for
> running images in QEMU, where running KVM on those images is a
> requirement.  Currently, those scripts simply force TCG on aarch64.
> With this change, to take advantage of KVM NV support, I'd have to try
> to identify in the script whether NV would be supported.  QEMU would be
> in a much better position to determine this and fall back to TCG if it's
> unsupported, like how the -accel option with multiple values usually
> works.



  reply	other threads:[~2025-06-17 15:38 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27  6:24 [PATCH v5 0/5] ARM Nested Virt Support Eric Auger
2025-05-27  6:24 ` [PATCH v5 1/5] linux-headers: Update against kvm/next Eric Auger
2025-05-27  6:24 ` [PATCH v5 2/5] hw/arm: Allow setting KVM vGIC maintenance IRQ Eric Auger
2025-05-27  6:24 ` [PATCH v5 3/5] target/arm/kvm: Add helper to detect EL2 when using KVM Eric Auger
2025-05-27  6:24 ` [PATCH v5 4/5] target/arm: Enable feature ARM_FEATURE_EL2 if EL2 is supported Eric Auger
2025-05-27  6:24 ` [PATCH v5 5/5] hw/arm/virt: Allow virt extensions with KVM Eric Auger
2025-06-17 14:17   ` Alyssa Ross
2025-06-17 14:52     ` Eric Auger [this message]
2025-06-17 15:10     ` Eric Auger
2025-06-17 15:23     ` Miguel Luis
2025-06-17 15:41       ` Eric Auger
2025-06-17 15:50         ` Miguel Luis
2025-06-19  9:40           ` Eric Auger
2025-06-19 13:29           ` Eric Auger
2025-06-19 16:04             ` Alyssa Ross
2025-06-20 16:20             ` Miguel Luis
2025-05-27  7:39 ` [PATCH v5 0/5] ARM Nested Virt Support Marc Zyngier
2025-05-27  9:05   ` Eric Auger
2025-05-27 11:40   ` Miguel Luis
2025-05-27 12:02     ` Marc Zyngier
2025-05-27 13:24       ` Miguel Luis
2025-05-27 13:46         ` Marc Zyngier
2025-05-27 15:55           ` Miguel Luis
2025-05-27 16:52             ` Marc Zyngier
2025-05-27 23:52               ` Miguel Luis
2025-05-28  8:07                 ` Marc Zyngier
2025-06-19  8:19   ` Eric Auger
2025-06-19  8:33     ` Miguel Luis
2025-05-27 11:33 ` Miguel Luis
2025-05-27 12:01   ` Marc Zyngier
2025-05-27 12:54     ` Miguel Luis
2025-05-27 13:11       ` Eric Auger
2025-05-27 14:15         ` Marc Zyngier

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=6debc836-c55d-406f-a74d-8ea5070b7fba@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).