[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <01205247-ffcd-439f-b00f-d8e70720d049@arm.com>
Date: Mon, 2 Dec 2024 08:54:11 +0000
From: Steven Price <steven.price@....com>
To: Itaru Kitayama <itaru.kitayama@...ux.dev>
Cc: kvm@...r.kernel.org, kvmarm@...ts.linux.dev,
Catalin Marinas <catalin.marinas@....com>, Marc Zyngier <maz@...nel.org>,
Will Deacon <will@...nel.org>, James Morse <james.morse@....com>,
Oliver Upton <oliver.upton@...ux.dev>,
Suzuki K Poulose <suzuki.poulose@....com>, Zenghui Yu
<yuzenghui@...wei.com>, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, Joey Gouly <joey.gouly@....com>,
Alexandru Elisei <alexandru.elisei@....com>,
Christoffer Dall <christoffer.dall@....com>, Fuad Tabba <tabba@...gle.com>,
linux-coco@...ts.linux.dev,
Ganapatrao Kulkarni <gankulkarni@...amperecomputing.com>,
Gavin Shan <gshan@...hat.com>, Shanker Donthineni <sdonthineni@...dia.com>,
Alper Gun <alpergun@...gle.com>, "Aneesh Kumar K . V"
<aneesh.kumar@...nel.org>, Jean-Philippe Brucker <jean-philippe@...aro.org>
Subject: Re: [PATCH v5 00/43] arm64: Support for Arm CCA in KVM
Hi Itaru,
On 02/12/2024 05:10, Itaru Kitayama wrote:
> On Fri, Oct 04, 2024 at 04:27:21PM +0100, Steven Price wrote:
>> This series adds support for running protected VMs using KVM under the
>> Arm Confidential Compute Architecture (CCA).
...
>
> On FVP, the v5+v7 kernel is unable to execute virt-manager:
>
> Starting install...
> Allocating 'test9.qcow2' | 0 B 00:00 ...
> Removing disk 'test9.qcow2' | 0 B 00:00
> ERROR internal error: process exited while connecting to monitor: 2024-12-04T18:56:11.646168Z qemu-system-aarch64: -accel kvm: ioctl(KVM_CREATE_VM) failed: Invalid argument
> 2024-12-04T18:56:11.646520Z qemu-system-aarch64: -accel kvm: failed to initialize kvm: Invalid argument
> Domain installation does not appear to have been successful.
Can you check that the kernel has detected the RMM being available, you
should have a message like below when the host kernel is booting:
kvm [1]: RMI ABI version 1.0
My guess is that you've got mismatched versions of the RMM and TF-A. The
interface between those two components isn't stable and there were
breaking changes fairly recently. And obviously if the RMM hasn't
initialised successfully then confidential VMs won't be available.
> Below is my virt-manager options:
>
> virt-install --machine=virt --arch=aarch64 --name=test9 --memory=2048 --vcpu=1 --nographic --check all=off --features acpi=off --virt-type kvm --boot kernel=Image-cca,initrd=rootfs.cpio,kernel_args='earlycon console=ttyAMA0 rdinit=/sbin/init rw root=/dev/vda acpi=off' --qemu-commandline='-M virt,confidential-guest-support=rme0,gic-version=3 -cpu host -object rme-guest,id=rme0 -nodefaults' --disk size=4 --import --osinfo detect=on,require=off
>
> Userland is Ubuntu 24.10, the VMM is Linaro's cca/2024-11-20:
>
> https://git.codelinaro.org/linaro/dcap/qemu/-/tree/cca/2024-11-20?ref_type=heads
I don't think this is the latest QEMU tree, Jean-Philippe posted an
update last week:
https://lore.kernel.org/qemu-devel/20241125195626.856992-2-jean-philippe@linaro.org/
I'm not sure if there were any important updates there, but there are
detailed instructions that might help.
Regards,
Steve
Powered by blists - more mailing lists