On Fri, May 31, 2024 at 11:16:30PM +0900, Itaru Kitayama wrote: > Thanks! I wasn’t aware of it The good news is that after whole day of try and > error attempts I was able to > bring up a Realm VM on FVP. Here’s my version of overlay yaml, cca-v2.yaml:
That is good news, thanks for the update > build: > linux: > repo: > revision: cca-full/v2 > > # kvmtool: > # repo: > # revision: cca/v2 > > rmm: > repo: > revision: main > > > > tfa: > repo: > revision: master > > kvm-unit-tests: > repo: > revision: cca/v2 > > … and the QEMU options are below: > > 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 Note that the cca/v2 branch of QEMU would reject 'num-pmu-counters' and 'sve-vector-length' arguments, so if this works it means an older version of the QEMU patches is being used (which also means an older Linux branch is being used). It's possible that shrinkwrap is caching all the build files, so I'd remove the ~/.shrinkwrap/ files to start fresh Thanks, Jean
