From: David Airlie <airlied@redhat.com>
To: Saket Sinha <saket.sinha89@gmail.com>
Cc: kvm@vger.kernel.org, dri-devel@lists.freedesktop.org,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] VirtIO-GPU 3D OpenGL Hardware Acceleration for VMs
Date: Sun, 14 Feb 2016 21:47:05 -0500 (EST) [thread overview]
Message-ID: <884678637.28458711.1455504425694.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAK25hWMx_u9KZ-QDtOSRzenF+SPzXBWymM4p8Xxn8EJGURCGRg@mail.gmail.com>
----- Original Message -----
> From: "Saket Sinha" <saket.sinha89@gmail.com>
> To: dri-devel@lists.freedesktop.org, kvm@vger.kernel.org, qemu-devel@nongnu.org
> Cc: "Dave Airlie" <airlied@redhat.com>
> Sent: Monday, 15 February, 2016 12:34:18 PM
> Subject: VirtIO-GPU 3D OpenGL Hardware Acceleration for VMs
>
> Hi,
>
> It seems upstream Linux/Gallium3D/Mesa/Qemu/KVM has recently gained
> virtualized support for 3D/OpenGL hardware acceleration in VMs,
> allowing using the GPU of the host in VMs.
>
> As per my understanding the following components are needed -
>
> - Linux 4.4 kernel includes the DRM driver for VirtIO-GPU 3D
> acceleration (needed in the VM).
> - Qemu 2.5 includes the VirtIO-GPU 3D mode support.
In qemu 2.5 only gtk3 frontend support 3D and must be enabled with gl=on
> - Gallium3D VirGL driver is included in Mesa git (needed in the VM,
> supports up to OpenGL 3.3 atm).
> - On the host *any* OpenGL driver (for the host GPU obviously), no
> special requirements there.
>
> In order to do test this, if I can be guided as to what are the right
> applications to test the entire Graphic stack on a QEMU-KVM Virtual
> machine, I shall be grateful.
glxinfo in the guest should print virgl in the renderer string, that is enough
to know the stack is functioning.
if it shows llvmpipe it isn't.
Dave.
next prev parent reply other threads:[~2016-02-15 2:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 2:34 [Qemu-devel] VirtIO-GPU 3D OpenGL Hardware Acceleration for VMs Saket Sinha
2016-02-15 2:47 ` David Airlie [this message]
2016-03-24 7:41 ` Chih-Wei Huang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=884678637.28458711.1455504425694.JavaMail.zimbra@redhat.com \
--to=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=saket.sinha89@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).