<html>
    <head>
      <base href="https://bugs.freedesktop.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Support WDDM 1.3 and embedded display in qxl-wddm-dod for an Optimus Windows guest hybrid setup"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=106760">106760</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Support WDDM 1.3 and embedded display in qxl-wddm-dod for an Optimus Windows guest hybrid setup
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>Spice
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>x86-64 (AMD64)
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Windows (All)
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>win32 qxl xddm
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>spice-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>oblitz@protonmail.com
          </td>
        </tr></table>
      <p>
        <div>
        <pre>There have been progress to get an Nvidia dGPU to work in a Windows guest in an
Optimus setup for the past year. A hacky OVMF patch [1] has allowed the dGPU to
initialize properly, bypassing the error 43, and allowed certain applications
to make use of the dGPU at a near-native performance.

However, the number of applications that are clever enough to make use of the
dGPU seem rare. A reason for this could be due to a lack of proper hybrid setup
where an integrated/embedded display panel is not detected.

A potential solution to this could be to modify the qxl-wddm-dod driver to WDDM
1.3 and expose the emulated display as an embedded display. [2,3,4]

[1] <a href="https://github.com/jscinoz/optimus-vfio-docs/issues/2">https://github.com/jscinoz/optimus-vfio-docs/issues/2</a>
[2]
<a href="https://github.com/jscinoz/optimus-vfio-docs/issues/2#issuecomment-390550145">https://github.com/jscinoz/optimus-vfio-docs/issues/2#issuecomment-390550145</a>
[3] <a href="https://www.redhat.com/archives/vfio-users/2018-April/msg00019.html">https://www.redhat.com/archives/vfio-users/2018-April/msg00019.html</a>
[4]
<a href="https://reddit.com/r/VFIO/comments/8gv60l/current_state_of_optimus_muxless_laptop_gpu/">https://reddit.com/r/VFIO/comments/8gv60l/current_state_of_optimus_muxless_laptop_gpu/</a></pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>