"agl-cluster-demo-platform" qemu-x86_64 vmdk image issue with VirtualBox on koi branch
Description
Environment
Attachments
Activity
Marius Vlad June 22, 2022 at 1:01 PM
With a marlin build I can't really see any artefacts described here, the cluster-demo starts immediately.
Also, tried out vbox 6.1.34-dfsg-3 from debian testing.
please re-open if you still see this issue.
Marius Vlad July 21, 2021 at 9:12 AM
Yeah, but at least it narrows things a bit. This seems to only happen with Vbox and the cluster-demo.
Farshid Monhaseri July 20, 2021 at 10:37 AM
Hi @Marius, I just tested the latest IVI master prebuilt vmdk image (agl-demo-platform-crosssdk-qemux86-64-20210720021726.rootfs.wic.vmdk) as your request on my platform with VirtualBox.
It works perfectly fine, and the agl-compositor doesn't need any kind of input or mouse event to start to display.
Here I attached the compositor.log file, as you can see there are no error ... but on cluster image the compositor.log file is appended with error messages with a crazy rate! (as you can see on cluster compositor.log I attached here).
So I guess something wrong with the cluster image vmdk image ... so weird.
Farshid Monhaseri July 19, 2021 at 5:03 PM
These are the logs, for " journalctl -u weston@display", before and after the input mouse event, which cause agl-compositor to display the window content.
Farshid Monhaseri out of curiosity have you tried agl-demo (not the cluster demo) with Virtualbox? There are snapshots for that at https://download.automotivelinux.org/AGL/snapshots/master/latest/qemux86-64/deploy/images/qemux86-64/ so you could grab one and test? I'd be interested to see if that happens as well.
Today I test the master image but for the Qemu (by seprate bzimage & rootfs file) but not with the vmdk image ... on cluster image also the qemu image is OK, the issue is for the vmdk image with virtualBox.
But I can test the vmdk too, I will report the result in this week.
Marius Vlad July 19, 2021 at 2:39 PM
if you still have access and can, I'd like to get a protocol dump. Edit /etc/default/weston add WAYLAND_DEBUG=1 and reboot. Attach the contents of journalctl -u weston@display
out of curiosity have you tried agl-demo (not the cluster demo) with Virtualbox? There are snapshots for that at https://download.automotivelinux.org/AGL/snapshots/master/latest/qemux86-64/deploy/images/qemux86-64/ so you could grab one and test? I'd be interested to see if that happens as well.
Details
Details
Assignee
Marius VladReporter
Farshid MonhaseriHardware Platform(s) Affected
Components
Affects versions
Priority
Minor
Hi community,
There are some issues with the "vmdk" image of "agl-cluster-demo-platform" on "koi" branch with VirtualBox. After userspace loading, the compositor looks to be not loaded or maybe froze at init steps (maybe) and we have black screen (attached the image).
The compositor immediately runs (display the cluster graphics) after gets an input from mouse pointer in vbox screen active area (mouse hover or click).
Also, the cluster demo is not fitted to vbox borders on "koi" and also "jellyfish" branches.
The VitualBox settings are mainly same with the one AGL documentations recommended, and I attached the vbox configs too.
The "koi" and "jellyfish" images are just working perfectly fine with QEMU in the same environment with the QEMU command & options from meta-elisa README. Also works fine with the "qemu_agl_efi.sh" from , so the "vmdk" looks to be OK, but It is weird that just happens on koi branch.
This issue is just forwarded to Elisa project cluster demo image too and since they use the qemu-x86_64 image (with VirtualBox and QEMU) so these a few minor issues would be considered major there.