Announcement

Collapse
No announcement yet.

VirGL VirtIO 3D GPU Driver Added To Gallium3D

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • VirGL VirtIO 3D GPU Driver Added To Gallium3D

    Phoronix: VirGL VirtIO 3D GPU Driver Added To Gallium3D

    The open-souce QEMU/KVM stack with VirtIO will finally be able to have guest 3D/OpenGL acceleration that's backed by the GPU/driver of the host system! While VMware and VirtualBox have long had guest 3D support backed by the host's hardware, it's taken a while for the open-source Linux virtualization stack to gain this functionality...

    http://www.phoronix.com/scan.php?pag...rGL-3D-In-Mesa

  • #2
    Cant wait for benchmarks!

    Comment


    • #3
      When benchmarks arrive, I would be really interested to see comparisons to bare metal (obviously), but also GPU/PCI passthrough of the host GPU being tested. That way we see whether the VM is the bottleneck or the drivers (or both).

      Seems like this is something that may need to be added to mesamatrix, too.
      Last edited by schmidtbag; 10-23-2015, 09:22 AM.

      Comment


      • #4
        The backend renderer translates the virgl interface into OpenGL currently...
        Does this mean it will work with proprietary drivers on the host machine?

        Comment


        • #5
          Originally posted by MoonMoon View Post
          Does this mean it will work with proprietary drivers on the host machine?
          yes .

          Comment


          • #6
            awesome

            Comment


            • #7
              Can this driver be cross compiled for Windows? I know the current qxl driver is available for windows but can we use virgl with Mesa's gallium-nine backend to bring direct3d acceleration in windows?

              Comment


              • #8
                Nice, congrats Dave!

                Comment


                • #9
                  This is really cool, thanks Dave!

                  Comment


                  • #10
                    Originally posted by schmidtbag View Post
                    When benchmarks arrive, I would be really interested to see comparisons to bare metal (obviously), but also GPU/PCI passthrough of the host GPU being tested. That way we see whether the VM is the bottleneck or the drivers (or both).

                    Seems like this is something that may need to be added to mesamatrix, too.
                    Probably doesn't need much mesamatrix, since it is very dependant on what host drivers expose.

                    For benchmarks I'd rather see benchmarks vs vmware and virtualbox running the same software on host/guest. Comparing virgl against pci passthrough is apples to oranges, they are different things, and have very different use cases. If you want speed and can give up the hw you use passthrough, if can't dedicate the hw you want something like virgl. It won't ever be close to native speeds, since there is always extra overheads.

                    If you say run F23/gnome-shell in a guest inside a host running F23/gnome-shell, you have two compositors in the stack, along with the VM overheads. In theory you'd have to run a fullscreen app in the VM running in fullscreen on the host and hope the compositors get out of the way, then at least you just have the extra copies involved due to GL, as the guest app renders to a guest back buffer, swaps to a guest front buffer, the host side then copies the guest front buffer to a host back buffer and swaps that to get it on the screen.

                    Dave.

                    Comment

                    Working...
                    X