* Re: KVM progress with FEAT_NV2
[not found] <YT6PR01MB10847DF9576E4055F3F8F95F3C0952@YT6PR01MB10847.CANPRD01.PROD.OUTLOOK.COM>
@ 2026-10-07 9:23 ` Marc Zyngier
0 siblings, 0 replies; only message in thread
From: Marc Zyngier @ 2026-10-07 9:23 UTC (permalink / raw)
To: Jasmin Mulaosmanovic; +Cc: kvmarm@lists.linux.dev, Sheridan Ethier, Phil Giroux
Hi Jasmin,
On Tue, 06 Oct 2026 20:01:22 +0100,
Jasmin Mulaosmanovic <jmulaosmanovic@qnx.com> wrote:
>
> Hi Marc,
>
> I'm a product manager at QNX looking at the status of nested
> virtualization support in KVM. The ARM team pointed me to you as the
> right person to contact.
>
> Our automotive customers run QNX-based systems in the cloud. We want
> to run multiple QNX Hypervisor instances on top of KVM, with each
> instance hosting its own Android and Linux guests.
>
> We understand there has been ongoing upstream work on FEAT_NV2
> support. Is there a roadmap or expected timeline for KVM to support
> this configuration with hardware acceleration?
Support for FEAT_NV2 has been merged about a year ago (in 6.17, if I
remember correctly), as an experimental feature, and is regularly
improved. There is also some limited support in upstream QEMU and
kvmtool to drive this.
As for a roadmap, we don't have one. Architectural features are
enabled as needed, and as people find the time (and interest) to
support them. Whether the existing KVM support matches what QNX
requires, I can't tell.
Hope this helps,
M.
--
Jazz isn't dead. It just smells funny.
^ permalink raw reply [flat|nested] only message in thread