> On 27 May 2025, at 12:01, Marc Zyngier <m...@kernel.org> wrote: > > On Tue, 27 May 2025 12:33:23 +0100, > Miguel Luis <miguel.l...@oracle.com> wrote: >> >> Hi Eric, >> >>> On 27 May 2025, at 06:24, Eric Auger <eric.au...@redhat.com> wrote: >>> >>> Now that ARM nested virt has landed in kvm/next, let's turn the series >>> into a PATCH series. The linux header update was made against kvm/next. >>> >>> 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. >> >> For the current kvmarm/next the guest also needs >> “kvm-arm.mode=nested” I believe. > > No, unless you want the guest itself to be NV-capable. >
Correct, I got carried away with some mode combinations. Maybe we should depict here more broadly how NV might be used with different mode combinations. I'll think about this further ahead. As far this series go I couldn't found any issue booting a L1 guest with virtualization=on and a L2 guest with virtualization=off. Miguel > M. > > -- > Without deviation from the norm, progress is not possible.
