<div dir="ltr">Thanks Alex,<div><br></div><div>Yes i know, I'm targeting for arm though. I see '3d acceleration enabled' so it was pointing me to its availability still without KVM. I was finally able to have weston and its gl examples working for aarch64 and performance seems reasonable. I'm still evaluating it though.</div><div><br></div><div><br></div><div>Br,</div><div>Joao</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 13, 2019 at 10:52 AM Alexander Kanavin <<a href="mailto:alex.kanavin@gmail.com" target="_blank">alex.kanavin@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, 12 Feb 2019 at 18:54, João Rasta <<a href="mailto:freakforever@gmail.com" target="_blank">freakforever@gmail.com</a>> wrote:<br>
> I was trying to build virgl-gtk branch for ARM qemu target, but I'm not completely sure if it's possible as it generally seems to require KVM.<br>
><br>
> qemu-system-aarch64 has the virtio-gpu-pci device, which i'd assume to support GL forwarding to the host if compiled with libvirglrenderer. I've also been able to run a cross-compiled image reporting [drm] 3d Acceleration enabled. However, I was not able to start any graphics application on the guest.<br>
><br>
> Could someone pls clarify this?<br>
<br>
First, do you need specifically qemuarm64? qemux86_64 is significantly<br>
faster because it has kvm. I never tried arm or other emulation<br>
targets because of that, it's all tested with x86*.<br>
<br>
The tests you need to do are:<br>
a) run 'dmesg | grep drm'. What do you see?<br>
<br>
b) add kmscube to your image and run that. There is a demo video I<br>
made so you can see how it works:<br>
<a href="https://www.youtube.com/watch?v=0YBuku3JESc&feature=youtu.be" rel="noreferrer" target="_blank">https://www.youtube.com/watch?v=0YBuku3JESc&feature=youtu.be</a><br>
<br>
Alex<br>
</blockquote></div>