On Fri, Oct 07, 2022 at 02:38:06PM +0900, Masahiro Yamada wrote:

> The arm virt machine with gicv3 booted as far as I tested.
> 
> So, I need to know more details about the settings of the KernelCI.

The HTML versions of the boot logs include the qemu command, these days
it's run using docker so so you can even get the specific version of
qemu version that was being used by kernelci in case that's important:

docker run --network=host --cap-add=NET_ADMIN --interactive --tty --rm --init --name=lava-docker-qemu-7496529-2.1.1-gexyjab5hb --device=/dev/kvm --device=/dev/net/tun --mount=type=bind,source=/var/lib/lava/dispatcher/tmp,destination=/var/lib/lava/dispatcher/tmp kernelci/qemu qemu-system-arm -cpu cortex-a15 -machine virt-2.11,gic-version=3 -nographic -net nic,model=virtio,macaddr=DE:AD:BE:EF:45:5C -net bridge,br=virbr0 -m 1024 -monitor none -kernel /var/lib/lava/dispatcher/tmp/7496529/deployimages-blwzkdvs/kernel/zImage -append "console=ttyAMA0,115200 root=/dev/ram0 debug verbose console_msg_format=syslog earlycon" -initrd /var/lib/lava/dispatcher/tmp/7496529/deployimages-blwzkdvs/ramdisk/rootfs.cpio.gz -drive format=qcow2,file=/var/lib/lava/dispatcher/tmp/7496529/apply-overlay-guest-f5mnvw0l/lava-guest.qcow2,media=disk,if=virtio,id=lavatest

Everything from qemu-system-arm on is the command that's run inside the
container.

The logs also show the download of the filesystems that would be used,
though we don't get as far as actually using them so it's a bit moot:

https://storage.kernelci.org/next/master/next-20221004/arm/multi_v7_defconfig+debug/gcc-10/lab-collabora/baseline-qemu_arm-virt-gicv3.html