Announcement

Collapse
No announcement yet.

VirtualBox DRM Driver Gets Patches To Go Atomic, Promote Out Of Staging

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

  • VirtualBox DRM Driver Gets Patches To Go Atomic, Promote Out Of Staging

    Phoronix: VirtualBox DRM Driver Gets Patches To Go Atomic, Promote Out Of Staging

    We've known Red Hat was working on converting the VirtualBox "vboxvideo" DRM/KMS driver to using the atomic APIs for atomic mode-setting to replace the legacy APIs and now those patches are out there...

    http://www.phoronix.com/scan.php?pag...ic-Patches-Out

  • #2
    That's an interesting take. Given that Red Hat had a lot of investment put into KVM and Libvirt. Maybe the cross-platform aspect of VBox got them to change their mind.

    Comment


    • #3
      Now they just have the much harder task of getting Vbox video driver to the same quality and GL/ES API exposure of SVGA II and Virglrenderer.

      Comment


      • #4
        Originally posted by Xaero_Vincent View Post
        GL/ES API exposure of SVGA II and Virglrenderer.
        Does VirtualBox itself support utilizing host's OGL/ES?

        Comment


        • #5
          My work on the VirtualBox *guest* drivers is purely to give Fedora (and Linux in general) a better OOTB experience when installed as a VirtualBox guest. The reason for this is that many people first dip their toe into the waters of running Fedora using a VM and VirtualBox is a popular choice for doing this. This really is no different from how we support running as a guest under e.g. HyperV.

          For running a vm under Linux you should absolutely use KMS + libvirt, through e.g. boxes or virt-manager.

          And sorry I've no plans to work on VirGL or some-such for VirtualBox.

          Comment


          • #6
            Thanks again for all your work, hansdegoede! You're submitted several patches that have made my life easier.

            Comment


            • #7
              Originally posted by RickXy View Post
              That's an interesting take. Given that Red Hat had a lot of investment put into KVM and Libvirt. Maybe the cross-platform aspect of VBox got them to change their mind.
              lol, considering subj is about guest drivers, maybe missing kvm on windows got them to not change their mind?
              Last edited by pal666; 09-27-2018, 05:11 PM.

              Comment


              • #8
                Once again, many thanks to Hans for his excellent work.

                Comment


                • #9
                  Originally posted by hansdegoede View Post
                  For running a vm under Linux you should absolutely use KMS + libvirt, through e.g. boxes or virt-manager.
                  Is it just as easy to setup virtual networks with boxes/virt-manager as it is with VirtualBox?

                  With VirtualBox they've made it super easy to add adapters to virtual machines and connect them to your real network or a virtual one. It's all nicely documented too.

                  Comment


                  • #10
                    Originally posted by cybertraveler View Post
                    Is it just as easy to setup virtual networks with boxes/virt-manager as it is with VirtualBox?
                    Check "virt-manager virtual networks" image search in Google.

                    Comment

                    Working...
                    X