[OE-core] QEmu + Spice + Virglrenderer Was: [PATCH] qemu: upgrade to version 2.10.0

[Martin Jansa]

On Wed, Sep 13, 2017 at 4:15 PM, Burton, Ross <ross.burton at intel.com> wrote:

> On 13 September 2017 at 15:12, Martin Jansa <martin.jansa at gmail.com>
> wrote:
>
>> On Fri, Sep 01, 2017 at 01:44:56PM +0200, Martin Jansa wrote:
>> > I don't know how accelerated GL will be in the end, but this commit:
>> > https://git.qemu.org/?p=qemu.git;a=commitdiff;h=474114b7305c
>> c1be7c2ee8ba5267be159a9d56e3
>> > made it possible.
>> >
>> > I've built qemu with my Gentoo host with virgl and spice support, and I
>> > plan to try how fast it goes.
>>
>> I've some WIP changes to build qemu-native with virglrenderer enabled in:
>> http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/qemu
>>
>> and few more to enable spice as well in:
>> http://git.openembedded.org/meta-openembedded-contrib/log/?h=jansa/spice
>
>
> Awesome. Can't wait to see how it performs.
>
> Ross
>

As of today qemu, qemu-native and nativesdk-qemu can be built with
virglrenderer, sdl2 and spice support.

I've tested core-image-sato running in qemu-native from headless Gentoo
chroot, with spicy client on normal Gentoo host as shown in screenshot.

Now I need to find out how to connect virt-viewer to spice running in
chroot over unix socket instead of tcp socket (mandatory for passing
dma-buf file descriptor).

Next step is to benchmark graphics with and without virglrenderer and with
and without spice.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20170914/ed744ee2/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: spicy-sato.png
Type: image/png
Size: 392647 bytes
Desc: not available
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20170914/ed744ee2/attachment-0002.png>