Announcement

Collapse
No announcement yet.

VMware Prepares Linux Driver For Next-Gen Virtual GPU

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

  • #31
    Originally posted by gilboa View Post

    I wonder if I can somehow get it working via ovirt....

    - Gilboa
    oVirt uses Libvirt still right? it should work fine then.

    Comment


    • #32
      Originally posted by Quackdoc View Post

      oVirt uses Libvirt still right? it should work fine then.
      Yes.
      I assume I need to replace qxl w/ virt-gpu?

      - Gilboa
      oVirt-HV1: Intel S2600C0, 2xE5-2658V2, 128GB, 8x2TB, 4x480GB SSD, GTX1080 (to-VM), Dell U3219Q, U2415, U2412M.
      oVirt-HV2: Intel S2400GP2, 2xE5-2448L, 120GB, 8x2TB, 4x480GB SSD, GTX730 (to-VM).
      oVirt-HV3: Gigabyte B85M-HD3, E3-1245V3, 32GB, 4x1TB, 2x480GB SSD, GTX980 (to-VM).
      Devel-2: Asus H110M-K, i5-6500, 16GB, 3x1TB + 128GB-SSD, F33.

      Comment


      • #33
        Originally posted by gilboa View Post

        Yes.
        I assume I need to replace qxl w/ virt-gpu?

        - Gilboa
        yes you most likely want to replace it.

        Comment


        • #34
          Originally posted by Quackdoc View Post

          yes you most likely want to replace it.
          Thanks.
          Seems that virt-gpu is not support by ovirt.


          - Gilboa
          oVirt-HV1: Intel S2600C0, 2xE5-2658V2, 128GB, 8x2TB, 4x480GB SSD, GTX1080 (to-VM), Dell U3219Q, U2415, U2412M.
          oVirt-HV2: Intel S2400GP2, 2xE5-2448L, 120GB, 8x2TB, 4x480GB SSD, GTX730 (to-VM).
          oVirt-HV3: Gigabyte B85M-HD3, E3-1245V3, 32GB, 4x1TB, 2x480GB SSD, GTX980 (to-VM).
          Devel-2: Asus H110M-K, i5-6500, 16GB, 3x1TB + 128GB-SSD, F33.

          Comment


          • #35
            VM
            Originally posted by gilboa View Post
            Not only is that ancient it also shouldn't matter, try editing the xml directly, just use virsh edit VMNAME, then add the necessary bits to the config file

            Comment


            • #36
              Meanwhile, Red Hat published a virtio-win package update that provides VIRTIO-GPU support on Windows guests (tested with Fedora as host):

              dxdiag showing VIRTIO-GPU

              Comment


              • #37
                Originally posted by fdelapena View Post
                Meanwhile, Red Hat published a virtio-win package update that provides VIRTIO-GPU support on Windows guests (tested with Fedora as host):

                dxdiag showing VIRTIO-GPU
                Its important to note that is a DOD only, so you will still be using software rasterization

                Comment


                • #38
                  Originally posted by Quackdoc View Post
                  VM
                  Not only is that ancient it also shouldn't matter, try editing the xml directly, just use virsh edit VMNAME, then add the necessary bits to the config file
                  Didn't think about it. Good idea.
                  oVirt has a hook (and UI) to support manual configuration of the VM (I actually use it on the desktop I write this on, to pass-through nVidia 1650TI to a Linux VM without having the driver detect its running as guest).

                  - Gilboa
                  oVirt-HV1: Intel S2600C0, 2xE5-2658V2, 128GB, 8x2TB, 4x480GB SSD, GTX1080 (to-VM), Dell U3219Q, U2415, U2412M.
                  oVirt-HV2: Intel S2400GP2, 2xE5-2448L, 120GB, 8x2TB, 4x480GB SSD, GTX730 (to-VM).
                  oVirt-HV3: Gigabyte B85M-HD3, E3-1245V3, 32GB, 4x1TB, 2x480GB SSD, GTX980 (to-VM).
                  Devel-2: Asus H110M-K, i5-6500, 16GB, 3x1TB + 128GB-SSD, F33.

                  Comment

                  Working...
                  X