From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Itaru Kitayama" <itaru.kitayama@linux.dev>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, qemu-arm <qemu-arm@nongnu.org>,
"Richard Henderson" <richard.henderson@linaro.org>
Subject: Re: Unexpected error in rme_configure_one() at ../target/arm/kvm-rme.c:159
Date: Fri, 31 May 2024 11:21:35 +0100 [thread overview]
Message-ID: <20240531102135.GA40178@myrica> (raw)
In-Reply-To: <CAFEAcA-gye9B1yJNKyT0fcZzR7TukNvaQyc7QkKQ_1FUGfAaYw@mail.gmail.com>
Hi Itaru,
On Fri, May 31, 2024 at 10:57:13AM +0100, Peter Maydell wrote:
> On Fri, 31 May 2024 at 05:20, Itaru Kitayama <itaru.kitayama@linux.dev> wrote:
> >
> >
> >
> > > On May 30, 2024, at 22:30, Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
> > >
> > > Cc'ing more developers
> > >
> > > On 30/5/24 06:30, Itaru Kitayama wrote:
> > >> Hi,
> > >> When I see a Realm VM creation fails with:
> > >> Unexpected error in rme_configure_one() at ../target/arm/kvm-rme.c:159:
> > >> qemu-system-aarch64: RME: failed to configure SVE: Invalid argument
> > >> test.sh: line 8: 2502 Aborted qemu-system-aarch64 -M 'virt,acpi=off,gic-version=3' -cpu host -enable-kvm -smp 2 -m 512M -overcommit 'mem-lock=on' -M 'confidential-guest-support=rme0' -object 'rme-guest,id=rme0,measurement-algo=sha512,num-pmu-counters=6,sve-vector-length=256' -kernel Image -initrd rootfs.cpio -append 'earycon console=ttyAMA0 rdinit=/sbin/init' -nographic -net none
> > >> do I need to suspect first the VMM, QEMU, or the Image? The kernel is built with LLVM, does it matter?
> > >> Thanks,
> > >> Itaru.
> > >
> >
> > I’m testing Jean’s repo at:
> >
> > https://git.codelinaro.org/linaro/dcap/qemu/-/tree/cca/v2?ref_type=heads
Thanks again for testing, you can report issues by replying directly to
my posting, so I can get to them quicker. If you want I can Cc you on the
next one. The latest is:
[PATCH v2 00/22] arm: Run CCA VMs with KVM
https://lore.kernel.org/qemu-devel/20240419155709.318866-2-jean-philippe@linaro.org/
That does sound like the KVM host doesn't support SVE, but the QEMU VMM
version is also too old: in the latest series 'sve-vector-length' was
removed and we use the existing -cpu parameters to configure SVE. Please
make sure that the QEMU branch is cca/v2 to match the Linux KVM branch,
because the older QEMU patches doesn't work with the newest KVM patches.
You'll need to update the command-line as well, because paramaters have
changed for cca/v2.
This may be the case of older build directories that aren't properly
synchronized. They can be removed manually but the quicker way is usually
to remove all source and build directories and start anew.
Thanks,
Jean
>
> OK, we should cc Jean-Philippe then.
>
> I'm wondering if this is as simple as "RME via KVM doesn't support SVE yet",
> perhaps.
>
> thanks
> -- PMM
next prev parent reply other threads:[~2024-05-31 10:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 4:30 Unexpected error in rme_configure_one() at ../target/arm/kvm-rme.c:159 Itaru Kitayama
2024-05-30 13:30 ` Peter Maydell
2024-05-30 13:30 ` Philippe Mathieu-Daudé
2024-05-31 4:19 ` Itaru Kitayama
2024-05-31 6:23 ` Gavin Shan
2024-05-31 15:09 ` Jean-Philippe Brucker
2024-05-31 15:24 ` Ard Biesheuvel
2024-06-04 18:08 ` Jean-Philippe Brucker
2024-06-04 19:04 ` Ard Biesheuvel
2024-06-01 10:14 ` Gavin Shan
2024-06-03 8:24 ` Jean-Philippe Brucker
2024-06-04 3:02 ` Gavin Shan
2024-06-04 11:15 ` Jean-Philippe Brucker
2024-06-05 1:28 ` Gavin Shan
2024-06-05 15:56 ` Jean-Philippe Brucker
2024-06-06 5:05 ` Gavin Shan
2024-06-06 10:13 ` Gavin Shan
2024-06-06 11:03 ` Jean-Philippe Brucker
2024-05-31 9:57 ` Peter Maydell
2024-05-31 10:21 ` Jean-Philippe Brucker [this message]
2024-05-31 14:16 ` Itaru Kitayama
2024-05-31 16:09 ` Jean-Philippe Brucker
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=20240531102135.GA40178@myrica \
--to=jean-philippe@linaro.org \
--cc=itaru.kitayama@linux.dev \
--cc=peter.maydell@linaro.org \
--cc=philmd@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).