To establish the virtio interfaces as a truly performant and portable solution we need to test with multiple hypervisors which all exhibit different memory models for example.
We are targets three hypervisors at this time
KVM with AGL
Recorded on a MachiatoBin machine with KVM enabled. Using entirely stock AGL Jellyfish images.
Multimedia name agl-arm64-kvm-virtio-gpu-2020-11-10_11.11.55.mp4
| name | agl-arm64-kvm-virtio-gpu-2020-11-10_11.11.55.mp4 |
|---|
Xen Dom0 with AGL (under QEMU TCG Emulation)
Recorded on x86_64 developer machine running under QEMU TCG emulation (hence the slowness). The run uses the stock AGL kernel which is why you don't see the messages from the Dom0 kernel console.
Multimedia name agl-arm64-xen-dom0-virtio-gpu-2020-11-10_11.19.57.mp4
Automotive Grade Linux (AGL) Demo
We hope to show the first steps of this platform working at an AGL demo in December 2020
Venu https://events.linuxfoundation.org/automotive-linux-summit/
|
Xen Dom0 with AGL and Xen aware Linux 5.9 (under QEMU TCG emulation)
QEMU TCG emulation, but this time running a stock 5.9 stable kernel which I did a "make olddefconfig" with the .config from the AGL kernel and then enabled the Xen paravirtualised console (which is why you can see the kernel messages on boot up). You can see some services fail to start on boot-up but I suspect those are just timeouts due to the slowness of emulation. You can ssh into it once it's up.
Multimedia name agl-arm64-xen-dom0-virtio-gpu-custom-kernel-2020-11-10_11.25.44.mp4