Announcement

Collapse
No announcement yet.

Virgl Gallium3D Inching Closer To OpenGL 4.4, Crosses Off ARB_query_buffer_object

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

  • Virgl Gallium3D Inching Closer To OpenGL 4.4, Crosses Off ARB_query_buffer_object

    Phoronix: Virgl Gallium3D Inching Closer To OpenGL 4.4, Crosses Off ARB_query_buffer_object

    Fresh on the Mesa 19.1 development cycle, the Virgl Gallium3D driver that is used as part of OpenGL acceleration for KVM guests with VirtIO-GPU is seeing some improvements...

    http://www.phoronix.com/scan.php?pag...h-Query-Buffer

  • #2
    Where are the Windows drivers ?


    Comment


    • #3
      Originally posted by sarfarazahmad View Post
      Where are the Windows drivers ?
      And what's even worse no way to use it with Spice over a tcp socket
      ## VGA ##
      AMD: X1950XTX, HD3870, HD5870
      Intel: GMA45, HD3000 (Core i5 2500K)

      Comment


      • #4
        sarfarazahmad and darkbasic
        From what I read, it seems both of your complaints are related to the same problem. Virgl uses SPICE:
        https://en.wikipedia.org/wiki/Simple...g_Environments
        SPICE is based on TCP, but apparently it doesn't work on Windows.

        Comment


        • #5
          Did anyone manage to run Linux guest on Linux host using virt-manager with Qemu/KVM + virgl in current Debian testing? It refuses to start if OpenGL is enabled. Pure Qemu runs though. Not sure if it's a libvirt issue or something else.

          See:
          https://www.reddit.com/r/debian/comm...on_in_qemukvm/
          https://www.reddit.com/r/VFIO/commen...on_in_qemukvm/

          Comment


          • #6
            Is this the latest information on the interwebs for virtio-opengl-windows?

            https://www.studiopixl.com/2017-08-2...ng-virtio.html
            https://gist.github.com/Keenuts/1991...62cf0011147c0b
            https://www.phoronix.com/forums/foru...g-virgl-virtio

            It seems Nathan "Keenuts" Gauër is still active and working on something that is IMO more important:


            (The conversation is French with English text in the presentation)

            Comment


            • #7
              Originally posted by schmidtbag View Post
              SPICE is based on TCP, but apparently it doesn't work on Windows.
              Spice is working well in Windows VM when using for example QXL-GPU. But no OpenGL or DirectX acceleration at all...

              Originally posted by Jabberwocky View Post
              Is this the latest information on the interwebs for virtio-opengl-windows?
              I also would like to know if there are some plans to do Windows driver for VirtIO-GPU with 3D acceleration capability... I guess that there was no interest in OpenGL capable Windows driver, because usage of it would be very limited...

              But with Vulkan it is another story. Especially after DXVK premiere... Windows VirtIO-GPU driver with Vulkan support means almost native DirectX 10/11 support after DXVK installation!

              Comment


              • #8
                Red Hat has someone looking at Windows drivers, just a lot of work, no timelines yet.

                Comment


                • #9
                  Originally posted by airlied View Post
                  Red Hat has someone looking at Windows drivers, just a lot of work, no timelines yet.
                  Thanks for your and Redhat's efforts. It's good to hear someone is working on it. Fixing the industry's compute woes sure does take priority above Windows drivers for virtualized 3D acceleration! 👍

                  Comment


                  • #10
                    Originally posted by schmidtbag View Post
                    SPICE is based on TCP
                    Spice works with Unix sockets as well, but when you use TCP (mandatory if the virtualization server is remote) then it won't work with virgl.
                    ## VGA ##
                    AMD: X1950XTX, HD3870, HD5870
                    Intel: GMA45, HD3000 (Core i5 2500K)

                    Comment

                    Working...
                    X