Yes there is an integration. 

It is only finding crashes as of now, but there are plans to add support for correctness bug detection.

Does virglrenderer require an actual GPU?

virglrenderer can run on hardware and software drivers (llvmpipe, softpipe).  We're primarily going to use hardware drivers.  There's some hairy shader conversion code (https://cgit.freedesktop.org/virglrenderer/tree/src/vrend_shader.c) we would like to see tested.

Ah right, I've actually worked with driley on fuzzing other parts using libFuzzer. But I think using GraphicsFuzz will find quite a few more bugs.
I've set up a meeting for Friday, feel free to reschedule if Friday is a bad time.

Summary from meeting:

- metzman@ has a setup that generates shaders, creates a WebGL context, and runs the shaders.  The current GL implementation is Swiftshader.

- The current virgl fuzzer does not necessarily test GL implementations (libGLES), but generates random data for the virglrenderer (libvirglrenderer) api.

- To get a GL implementation, we can use vtest.  It sets up a socket between virglrenderer and guest GL.  It's already used in the freedesktop CI for testing dEQP:

https://gitlab.freedesktop.org/virgl/virglrenderer/merge_requests/74 


Action items:

1 - Get vtest building and running in our infrastructure (ChromeOS gfx will look into this)