https://wiki.xenproject.org/index.php?title=Xen_VGA_Passthrough_Tested_Adapters&feed=atom&action=historyXen VGA Passthrough Tested Adapters - Revision history2024-03-28T19:26:43ZRevision history for this page on the wikiMediaWiki 1.31.3https://wiki.xenproject.org/index.php?title=Xen_VGA_Passthrough_Tested_Adapters&diff=20015&oldid=prevChuckz: /* Intel display adapters */2022-12-16T20:02:16Z<p><span dir="auto"><span class="autocomment">Intel display adapters</span></span></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 20:02, 16 December 2022</td>
</tr><tr>
<td colspan="2" class="diff-lineno">Line 50:</td>
<td colspan="2" class="diff-lineno">Line 50:</td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.16.x Headless Debian unstable Dom0 with Debian's Qemu 7.0 package as the upstream qemu-xen device model, and the default Debian unstable 5.16.x kernel. With Linux kernel 5.17 and greater, Dom0 does not boot on some older Intel hardware due to an unpatched regression in the Linux kernel. A [https://lore.kernel.org/lkml/9385fa60-fa5d-f559-a137-6608408f88b0@suse.com/ patch] for the Linux kernel is available for this problem and it is now fixed in Linux 5.19.6 and higher.</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.16.x Headless Debian unstable Dom0 with Debian's Qemu 7.0 package as the upstream qemu-xen device model, and the default Debian unstable 5.16.x kernel. With Linux kernel 5.17 and greater, Dom0 does not boot on some older Intel hardware due to an unpatched regression in the Linux kernel. A [https://lore.kernel.org/lkml/9385fa60-fa5d-f559-a137-6608408f88b0@suse.com/ patch] for the Linux kernel is available for this problem and it is now fixed in Linux 5.19.6 and higher.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td colspan="2" class="diff-empty"> </td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> PCI slot 2 problem (this problem only applies to Qemu upstream, Qemu traditional does not have this problem):</div></td>
</tr>
<tr>
<td class="diff-marker">−</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> Update: In some cases, VGA passthrough of the Intel IGD does not work without a [https://lists.xenproject.org/archives/html/xen-devel/2022-10/msg01820.html patch to reserve PCI slot 2 for the Intel IGD] that has been proposed to Qemu upstream that hopefully will make it into a later version of Qemu. If VGA passthrough of the Intel IGD does not work, try the patch to Qemu upstream (backports of the patch all the way back to Qemu 5.2 for Debian 11 bullseye have been tested), and the patch does fix the problem. The exact conditions that trigger the need for the patch have not been identified, but it seems related to whether or not seabios tries to load the legacy VGA bios, and if it does, it expects the IGD to be at PCI slot 2. I have been able to workaround the problem by patching (or in some cases not patching) seabios to change how seabios decides whether or not to load the VGA bios.</div></td>
<td colspan="2" class="diff-empty"> </td>
</tr>
<tr>
<td colspan="2" class="diff-empty"> </td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> In some cases, VGA passthrough of the Intel IGD does not work without a [https://lists.xenproject.org/archives/html/xen-devel/2022-10/msg01820.html patch to reserve PCI slot 2 for the Intel IGD] that has been proposed to Qemu upstream that hopefully will make it into a later version of Qemu. If VGA passthrough of the Intel IGD does not work, try the patch to Qemu upstream (backports of the patch all the way back to Qemu 5.2 for Debian 11 bullseye have been tested), and the patch does fix the problem. The exact conditions that trigger the need for the patch have not been identified, but it seems related to whether or not seabios tries to load the legacy VGA bios, and if it does, it expects the Intel IGD to be at PCI slot 2. It is possible to workaround the problem by patching (or in some cases not patching) seabios to prevent seabios from loading the VGA bios instead of applying the patch to upstream Qemu that reserves PCI slot 2 for the Intel IGD.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Not Working:</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Not Working:</div></td>
</tr>
</table>Chuckzhttps://wiki.xenproject.org/index.php?title=Xen_VGA_Passthrough_Tested_Adapters&diff=20014&oldid=prevChuckz: /* List of tested graphics adapters for Xen VGA Passthrough */2022-12-16T19:47:21Z<p><span dir="auto"><span class="autocomment">List of tested graphics adapters for Xen VGA Passthrough</span></span></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 19:47, 16 December 2022</td>
</tr><tr>
<td colspan="2" class="diff-lineno">Line 40:</td>
<td colspan="2" class="diff-lineno">Line 40:</td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td colspan="2" class="diff-empty"> </td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> Working (In all cases reported here, the bios setting in the domain configuration file is unset or set to seabios):</div></td>
</tr>
<tr>
<td class="diff-marker">−</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> Working:</div></td>
<td colspan="2" class="diff-empty"> </td>
</tr>
<tr>
<td colspan="2" class="diff-empty"> </td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.4.x, Headless Debian jessie Dom0 with qemu traditional device model, and the default Debian jessie 3.16.x kernel. (Note that Debian does not provide either the traditional device model or hvmloader with rombios support, so qemu-dm and hvmloader with rombios support binaries must be built from source for Debian or these two binaries could probably be extracted from compatible Ubuntu Xen packages and added as device model and bios overrides in xl.cfg, qemu-dm was built from the qemu-xen-traditional.git repository at xenbits.xen.org).</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.4.x, Headless Debian jessie Dom0 with qemu traditional device model, and the default Debian jessie 3.16.x kernel. (Note that Debian does not provide either the traditional device model or hvmloader with rombios support, so qemu-dm and hvmloader with rombios support binaries must be built from source for Debian or these two binaries could probably be extracted from compatible Ubuntu Xen packages and added as device model and bios overrides in xl.cfg, qemu-dm was built from the qemu-xen-traditional.git repository at xenbits.xen.org).</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td colspan="2" class="diff-lineno">Line 49:</td>
<td colspan="2" class="diff-lineno">Line 50:</td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.16.x Headless Debian unstable Dom0 with Debian's Qemu 7.0 package as the upstream qemu-xen device model, and the default Debian unstable 5.16.x kernel. With Linux kernel 5.17 and greater, Dom0 does not boot on some older Intel hardware due to an unpatched regression in the Linux kernel. A [https://lore.kernel.org/lkml/9385fa60-fa5d-f559-a137-6608408f88b0@suse.com/ patch] for the Linux kernel is available for this problem and it is now fixed in Linux 5.19.6 and higher.</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.16.x Headless Debian unstable Dom0 with Debian's Qemu 7.0 package as the upstream qemu-xen device model, and the default Debian unstable 5.16.x kernel. With Linux kernel 5.17 and greater, Dom0 does not boot on some older Intel hardware due to an unpatched regression in the Linux kernel. A [https://lore.kernel.org/lkml/9385fa60-fa5d-f559-a137-6608408f88b0@suse.com/ patch] for the Linux kernel is available for this problem and it is now fixed in Linux 5.19.6 and higher.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker">−</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> Update: <del class="diffchange diffchange-inline">Recently</del> <del class="diffchange diffchange-inline">it</del> <del class="diffchange diffchange-inline">was discovered that</del> VGA passthrough of the Intel IGD <del class="diffchange diffchange-inline">is</del> <del class="diffchange diffchange-inline">no</del> <del class="diffchange diffchange-inline">longer working with recent versions of Xen and Linux (Xen 4.14 and higher and Linux 5.10 and higher)</del> without a [https://lists.xenproject.org/archives/html/xen-devel/2022-10/msg01820.html patch to reserve PCI slot 2 for the Intel IGD] that has been proposed to Qemu upstream that hopefully will make it into <del class="diffchange diffchange-inline">Qemu</del> <del class="diffchange diffchange-inline">7.2</del>. <del class="diffchange diffchange-inline">Those</del> <del class="diffchange diffchange-inline">who</del> <del class="diffchange diffchange-inline">are</del> <del class="diffchange diffchange-inline">so</del> <del class="diffchange diffchange-inline">inclined</del> <del class="diffchange diffchange-inline">can</del> try the patch to Qemu upstream <del class="diffchange diffchange-inline">and </del>backports of the patch all the way back to Qemu 5.2 for Debian 11 bullseye have been tested, and the patch does fix the problem.</div></td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> Update: <ins class="diffchange diffchange-inline">In</ins> <ins class="diffchange diffchange-inline">some</ins> <ins class="diffchange diffchange-inline">cases,</ins> VGA passthrough of the Intel IGD <ins class="diffchange diffchange-inline">does</ins> <ins class="diffchange diffchange-inline">not</ins> <ins class="diffchange diffchange-inline">work</ins> without a [https://lists.xenproject.org/archives/html/xen-devel/2022-10/msg01820.html patch to reserve PCI slot 2 for the Intel IGD] that has been proposed to Qemu upstream that hopefully will make it into <ins class="diffchange diffchange-inline">a</ins> <ins class="diffchange diffchange-inline">later version of Qemu</ins>. <ins class="diffchange diffchange-inline">If</ins> <ins class="diffchange diffchange-inline">VGA</ins> <ins class="diffchange diffchange-inline">passthrough</ins> <ins class="diffchange diffchange-inline">of</ins> <ins class="diffchange diffchange-inline">the</ins> <ins class="diffchange diffchange-inline">Intel IGD does not work,</ins> try the patch to Qemu upstream <ins class="diffchange diffchange-inline">(</ins>backports of the patch all the way back to Qemu 5.2 for Debian 11 bullseye have been tested<ins class="diffchange diffchange-inline">)</ins>, and the patch does fix the problem<ins class="diffchange diffchange-inline">. The exact conditions that trigger the need for the patch have not been identified, but it seems related to whether or not seabios tries to load the legacy VGA bios, and if it does, it expects the IGD to be at PCI slot 2. I have been able to workaround the problem by patching (or in some cases not patching) seabios to change how seabios decides whether or not to load the VGA bios</ins>.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Not Working:</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Not Working:</div></td>
</tr>
</table>Chuckzhttps://wiki.xenproject.org/index.php?title=Xen_VGA_Passthrough_Tested_Adapters&diff=20003&oldid=prevChuckz: /* Intel display adapters */2022-11-01T01:24:21Z<p><span dir="auto"><span class="autocomment">Intel display adapters</span></span></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 01:24, 1 November 2022</td>
</tr><tr>
<td colspan="2" class="diff-lineno">Line 45:</td>
<td colspan="2" class="diff-lineno">Line 45:</td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.11.x Headless Debian buster Dom0 with either qemu traditional or Debian's Qemu 3.1 package as the upstream qemu-xen device model, and the default Debian buster 4.19.x kernel.</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.11.x Headless Debian buster Dom0 with either qemu traditional or Debian's Qemu 3.1 package as the upstream qemu-xen device model, and the default Debian buster 4.19.x kernel.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker">−</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.14.x Headless Debian bullseye Dom0 with Debian's Qemu 5.2 package as the upstream qemu-xen device model, and the default Debian bullseye 5.10.x kernel.</div></td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.14.x Headless Debian bullseye Dom0 with Debian's Qemu 5.2 package as the upstream qemu-xen device model, and the default Debian bullseye 5.10.x kernel.<ins class="diffchange diffchange-inline"> </ins></div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker">−</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.16.x Headless Debian unstable Dom0 with Debian's Qemu 7.0 package as the upstream qemu-xen device model, and the default Debian unstable 5.16.x kernel. With Linux kernel 5.17 and greater, Dom0 does not boot on some older Intel hardware due to an unpatched regression in the Linux kernel. A [https://lore.kernel.org/lkml/9385fa60-fa5d-f559-a137-6608408f88b0@suse.com/ patch] for the Linux kernel is available for this problem <del class="diffchange diffchange-inline">that</del> <del class="diffchange diffchange-inline">only</del> <del class="diffchange diffchange-inline">exists</del> <del class="diffchange diffchange-inline">on</del> <del class="diffchange diffchange-inline">certain Intel hardware but it</del> <del class="diffchange diffchange-inline">has</del> <del class="diffchange diffchange-inline">not</del> <del class="diffchange diffchange-inline">been</del> <del class="diffchange diffchange-inline">committed</del> <del class="diffchange diffchange-inline">yet</del>.</div></td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.16.x Headless Debian unstable Dom0 with Debian's Qemu 7.0 package as the upstream qemu-xen device model, and the default Debian unstable 5.16.x kernel. With Linux kernel 5.17 and greater, Dom0 does not boot on some older Intel hardware due to an unpatched regression in the Linux kernel. A [https://lore.kernel.org/lkml/9385fa60-fa5d-f559-a137-6608408f88b0@suse.com/ patch] for the Linux kernel is available for this problem <ins class="diffchange diffchange-inline">and</ins> <ins class="diffchange diffchange-inline">it</ins> <ins class="diffchange diffchange-inline">is</ins> <ins class="diffchange diffchange-inline">now</ins> <ins class="diffchange diffchange-inline">fixed</ins> <ins class="diffchange diffchange-inline">in</ins> <ins class="diffchange diffchange-inline">Linux</ins> <ins class="diffchange diffchange-inline">5.19.6</ins> <ins class="diffchange diffchange-inline">and</ins> <ins class="diffchange diffchange-inline">higher</ins>.</div></td>
</tr>
<tr>
<td colspan="2" class="diff-empty"> </td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td colspan="2" class="diff-empty"> </td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> Update: Recently it was discovered that VGA passthrough of the Intel IGD is no longer working with recent versions of Xen and Linux (Xen 4.14 and higher and Linux 5.10 and higher) without a [https://lists.xenproject.org/archives/html/xen-devel/2022-10/msg01820.html patch to reserve PCI slot 2 for the Intel IGD] that has been proposed to Qemu upstream that hopefully will make it into Qemu 7.2. Those who are so inclined can try the patch to Qemu upstream and backports of the patch all the way back to Qemu 5.2 for Debian 11 bullseye have been tested, and the patch does fix the problem.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Not Working:</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Not Working:</div></td>
</tr>
<tr>
<td colspan="2" class="diff-lineno">Line 53:</td>
<td colspan="2" class="diff-lineno">Line 55:</td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> With the aforementioned patch applied to the Debian stretch Xen 4.8 hypervisor package, it worked with the qemu traditional device model.</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> With the aforementioned patch applied to the Debian stretch Xen 4.8 hypervisor package, it worked with the qemu traditional device model.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker">−</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> In all the configurations with Debian listed above, Windows 7/8/8.1/10 x86/x64 HVM guest DomUs all work well on the HDMI output with the Intel drivers provided by ASRock.</div></td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> In all the configurations with Debian listed above, Windows 7/8/8.1/10 x86/x64 HVM guest DomUs all work well on the HDMI output with the Intel drivers provided by ASRock<ins class="diffchange diffchange-inline"> provided that the aforementioned patch to Qemu upstream to reserve PCI slot 2 for the Intel IGD is applied. Qemu traditional has a patch that reserves slot 2 for the Intel IGD so Qemu traditional can be used as a workaround until the patch is applied to Qemu upstream</ins>.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker">−</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> Debian Linux HVM guest DomUs did not always work - worked with Debian jessie Dom0 and Debian jessie DomU and the traditional device model on the HDMI output and worked with a Debian buster Dom0 with the traditional device model and Debian Linux DomUs, but only on the VGA output, not the HDMI output in the latter configuration. Does not work well with a Debian buster or bullseye Dom0 (Xen 4.11 or Xen 4.14), the upstream device model, and Debian Linux Domus, not even after trying many different tweaks to the configuration. The problem when using the upstream Qemu device model is that there was an unpatched bug in the upstream Qemu device model that prevented the guest from setting up IRQs from the passed through devices. A [https://gitlab.com/qemu-project/qemu/-/commit/be9c61da9fc57eb7d293f380d0805ca6f46c2657 patch] has been committed to the master Qemu upstream branch <del class="diffchange diffchange-inline">to</del> <del class="diffchange diffchange-inline">fix</del> <del class="diffchange diffchange-inline">this</del> <del class="diffchange diffchange-inline">problem</del> <del class="diffchange diffchange-inline">so</del> <del class="diffchange diffchange-inline">this</del> <del class="diffchange diffchange-inline">will</del> <del class="diffchange diffchange-inline">be</del> <del class="diffchange diffchange-inline">fixed</del> <del class="diffchange diffchange-inline">in future Qemu releases</del>. The problem when using the traditional device model is that there is a missing hypercall that is needed to grant the Linux HVM guest permission to access the Intel OpRegion. A [https://lists.xenproject.org/archives/html/xen-devel/2022-03/msg01024.html patch] to fix this problem for the traditional Qemu device model is available on xen-devel but it will not be committed due to the fact that the old traditional Qemu device model is no longer recommended for modern versions of Xen.</div></td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> Debian Linux HVM guest DomUs did not always work - worked with Debian jessie Dom0 and Debian jessie DomU and the traditional device model on the HDMI output and worked with a Debian buster Dom0 with the traditional device model and Debian Linux DomUs, but only on the VGA output, not the HDMI output in the latter configuration. Does not work well with a Debian buster or bullseye Dom0 (Xen 4.11 or Xen 4.14), the upstream device model, and Debian Linux Domus, not even after trying many different tweaks to the configuration. The problem when using the upstream Qemu device model is that there was an unpatched bug in the upstream Qemu device model that prevented the guest from setting up IRQs from the passed through devices. A [https://gitlab.com/qemu-project/qemu/-/commit/be9c61da9fc57eb7d293f380d0805ca6f46c2657 patch] has been committed to the master Qemu upstream branch <ins class="diffchange diffchange-inline">and</ins> <ins class="diffchange diffchange-inline">Qemu</ins> <ins class="diffchange diffchange-inline">upstream</ins> <ins class="diffchange diffchange-inline">version</ins> <ins class="diffchange diffchange-inline">7.1</ins> <ins class="diffchange diffchange-inline">and</ins> <ins class="diffchange diffchange-inline">higher</ins> <ins class="diffchange diffchange-inline">has</ins> <ins class="diffchange diffchange-inline">the</ins> <ins class="diffchange diffchange-inline">fix</ins>. The problem when using the traditional device model is that there is a missing hypercall that is needed to grant the Linux HVM guest permission to access the Intel OpRegion. A [https://lists.xenproject.org/archives/html/xen-devel/2022-03/msg01024.html patch] to fix this problem for the traditional Qemu device model is available on xen-devel but it will not be committed due to the fact that the old traditional Qemu device model is no longer recommended for modern versions of Xen.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> For Xen 4.8 (with the critical patch applied) and Xen 4.11, the xl.cfg file needed the following setting for the PCI passthrough configuration:</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> For Xen 4.8 (with the critical patch applied) and Xen 4.11, the xl.cfg file needed the following setting for the PCI passthrough configuration:</div></td>
</tr>
</table>Chuckzhttps://wiki.xenproject.org/index.php?title=Xen_VGA_Passthrough_Tested_Adapters&diff=19968&oldid=prevChuckz: /* Intel display adapters */2022-07-06T21:41:00Z<p><span dir="auto"><span class="autocomment">Intel display adapters</span></span></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 21:41, 6 July 2022</td>
</tr><tr>
<td colspan="2" class="diff-lineno">Line 55:</td>
<td colspan="2" class="diff-lineno">Line 55:</td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> In all the configurations with Debian listed above, Windows 7/8/8.1/10 x86/x64 HVM guest DomUs all work well on the HDMI output with the Intel drivers provided by ASRock.</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> In all the configurations with Debian listed above, Windows 7/8/8.1/10 x86/x64 HVM guest DomUs all work well on the HDMI output with the Intel drivers provided by ASRock.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker">−</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> Debian Linux HVM guest DomUs did not always work - worked with Debian jessie Dom0 and Debian jessie DomU and the traditional device model on the HDMI output and worked with a Debian buster Dom0 with the traditional device model and Debian Linux DomUs, but only on the VGA output, not the HDMI output in the latter configuration. Does not work well with a Debian buster or bullseye Dom0 (Xen 4.11 or Xen 4.14), the upstream device model, and Debian Linux Domus, not even after trying many different tweaks to the configuration. The problem when using the upstream Qemu device model is that there <del class="diffchange diffchange-inline">is</del> an unpatched bug in the upstream Qemu device model that <del class="diffchange diffchange-inline">prevents</del> the guest from setting up IRQs from the passed through devices. A [https://<del class="diffchange diffchange-inline">www.mail-archive</del>.com/qemu-<del class="diffchange diffchange-inline">devel@nongnu.org</del>/<del class="diffchange diffchange-inline">msg897139.html</del> patch] <del class="diffchange diffchange-inline">is</del> <del class="diffchange diffchange-inline">available</del> to fix this <del class="diffchange diffchange-inline">but</del> <del class="diffchange diffchange-inline">it</del> <del class="diffchange diffchange-inline">has</del> <del class="diffchange diffchange-inline">not</del> <del class="diffchange diffchange-inline">been</del> <del class="diffchange diffchange-inline">committed</del> <del class="diffchange diffchange-inline">to</del> <del class="diffchange diffchange-inline">Qemu</del> <del class="diffchange diffchange-inline">upstream</del> <del class="diffchange diffchange-inline">yet</del>. The problem when using the traditional device model is that there is a missing hypercall that is needed to grant the Linux HVM guest permission to access the Intel OpRegion. A [https://lists.xenproject.org/archives/html/xen-devel/2022-03/msg01024.html patch] to fix this problem for the traditional Qemu device model is available on xen-devel but it will not be committed due to the fact that the old traditional Qemu device model is no longer recommended for modern versions of Xen.</div></td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> Debian Linux HVM guest DomUs did not always work - worked with Debian jessie Dom0 and Debian jessie DomU and the traditional device model on the HDMI output and worked with a Debian buster Dom0 with the traditional device model and Debian Linux DomUs, but only on the VGA output, not the HDMI output in the latter configuration. Does not work well with a Debian buster or bullseye Dom0 (Xen 4.11 or Xen 4.14), the upstream device model, and Debian Linux Domus, not even after trying many different tweaks to the configuration. The problem when using the upstream Qemu device model is that there <ins class="diffchange diffchange-inline">was</ins> an unpatched bug in the upstream Qemu device model that <ins class="diffchange diffchange-inline">prevented</ins> the guest from setting up IRQs from the passed through devices. A [https://<ins class="diffchange diffchange-inline">gitlab</ins>.com/qemu-<ins class="diffchange diffchange-inline">project</ins>/<ins class="diffchange diffchange-inline">qemu/-/commit/be9c61da9fc57eb7d293f380d0805ca6f46c2657</ins> patch] <ins class="diffchange diffchange-inline">has</ins> <ins class="diffchange diffchange-inline">been committed to the master Qemu upstream branch</ins> to fix this <ins class="diffchange diffchange-inline">problem</ins> <ins class="diffchange diffchange-inline">so</ins> <ins class="diffchange diffchange-inline">this</ins> <ins class="diffchange diffchange-inline">will</ins> <ins class="diffchange diffchange-inline">be</ins> <ins class="diffchange diffchange-inline">fixed</ins> <ins class="diffchange diffchange-inline">in</ins> <ins class="diffchange diffchange-inline">future</ins> <ins class="diffchange diffchange-inline">Qemu</ins> <ins class="diffchange diffchange-inline">releases</ins>. The problem when using the traditional device model is that there is a missing hypercall that is needed to grant the Linux HVM guest permission to access the Intel OpRegion. A [https://lists.xenproject.org/archives/html/xen-devel/2022-03/msg01024.html patch] to fix this problem for the traditional Qemu device model is available on xen-devel but it will not be committed due to the fact that the old traditional Qemu device model is no longer recommended for modern versions of Xen.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> For Xen 4.8 (with the critical patch applied) and Xen 4.11, the xl.cfg file needed the following setting for the PCI passthrough configuration:</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> For Xen 4.8 (with the critical patch applied) and Xen 4.11, the xl.cfg file needed the following setting for the PCI passthrough configuration:</div></td>
</tr>
</table>Chuckzhttps://wiki.xenproject.org/index.php?title=Xen_VGA_Passthrough_Tested_Adapters&diff=19967&oldid=prevChuckz: /* Intel display adapters */2022-06-29T19:08:04Z<p><span dir="auto"><span class="autocomment">Intel display adapters</span></span></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 19:08, 29 June 2022</td>
</tr><tr>
<td colspan="2" class="diff-lineno">Line 64:</td>
<td colspan="2" class="diff-lineno">Line 64:</td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> pci = [ '00:1b.0','00:14.0,rdm_policy=relaxed','00:02.0' ]</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> pci = [ '00:1b.0','00:14.0,rdm_policy=relaxed','00:02.0' ]</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker">−</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> If the memory assigned to the guest is greater than around 3 GB (memory = '<del class="diffchange diffchange-inline">3072</del>'), it might be necessary to increase the mmio_hole setting in the domain configuration file. The default is 256 MB, and increasing it to 512 MB enabled memory to be greater than 4 GB:</div></td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> If the memory assigned to the guest is greater than around 3<ins class="diffchange diffchange-inline">.5</ins> GB (memory = '<ins class="diffchange diffchange-inline">3584</ins>'), it might be necessary to increase the mmio_hole setting in the domain configuration file. The default is 256 MB, and increasing it to 512 MB enabled memory to be greater than 4 GB:</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> mmio_hole = '512'</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> mmio_hole = '512'</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
</table>Chuckzhttps://wiki.xenproject.org/index.php?title=Xen_VGA_Passthrough_Tested_Adapters&diff=19965&oldid=prevChuckz: /* Intel display adapters */2022-06-29T17:39:40Z<p><span dir="auto"><span class="autocomment">Intel display adapters</span></span></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 17:39, 29 June 2022</td>
</tr><tr>
<td colspan="2" class="diff-lineno">Line 55:</td>
<td colspan="2" class="diff-lineno">Line 55:</td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> In all the configurations with Debian listed above, Windows 7/8/8.1/10 x86/x64 HVM guest DomUs all work well on the HDMI output with the Intel drivers provided by ASRock.</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> In all the configurations with Debian listed above, Windows 7/8/8.1/10 x86/x64 HVM guest DomUs all work well on the HDMI output with the Intel drivers provided by ASRock.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker">−</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> Debian Linux HVM guest DomUs did not always work - worked with Debian jessie Dom0 and Debian jessie DomU and the traditional device model on the HDMI output and worked with a Debian buster Dom0 with the traditional device model and Debian Linux DomUs, but only on the VGA output, not the HDMI output in the latter configuration. Does not work well with a Debian buster or bullseye Dom0 (Xen 4.11 or Xen 4.14), the upstream device model, and Debian Linux Domus, not even after trying many different tweaks to the configuration. The problem when using the upstream Qemu device model is that there is an unpatched bug in the upstream Qemu device model that prevents the guest from setting up IRQs from the passed through devices. A [https://www.mail-archive.com/qemu-devel@nongnu.org/<del class="diffchange diffchange-inline">msg893744</del>.html patch] is available to fix this but it has not been committed to Qemu upstream yet. The problem when using the traditional device model is that there is a missing hypercall that is needed to grant the Linux HVM guest permission to access the Intel OpRegion. A [https://lists.xenproject.org/archives/html/xen-devel/2022-03/msg01024.html patch] to fix this problem for the traditional Qemu device model is available on xen-devel but it will not be committed due to the fact that the old traditional Qemu device model is no longer recommended for modern versions of Xen.</div></td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> Debian Linux HVM guest DomUs did not always work - worked with Debian jessie Dom0 and Debian jessie DomU and the traditional device model on the HDMI output and worked with a Debian buster Dom0 with the traditional device model and Debian Linux DomUs, but only on the VGA output, not the HDMI output in the latter configuration. Does not work well with a Debian buster or bullseye Dom0 (Xen 4.11 or Xen 4.14), the upstream device model, and Debian Linux Domus, not even after trying many different tweaks to the configuration. The problem when using the upstream Qemu device model is that there is an unpatched bug in the upstream Qemu device model that prevents the guest from setting up IRQs from the passed through devices. A [https://www.mail-archive.com/qemu-devel@nongnu.org/<ins class="diffchange diffchange-inline">msg897139</ins>.html patch] is available to fix this but it has not been committed to Qemu upstream yet. The problem when using the traditional device model is that there is a missing hypercall that is needed to grant the Linux HVM guest permission to access the Intel OpRegion. A [https://lists.xenproject.org/archives/html/xen-devel/2022-03/msg01024.html patch] to fix this problem for the traditional Qemu device model is available on xen-devel but it will not be committed due to the fact that the old traditional Qemu device model is no longer recommended for modern versions of Xen.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> For Xen 4.8 (with the critical patch applied) and Xen 4.11, the xl.cfg file needed the following setting for the PCI passthrough configuration:</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> For Xen 4.8 (with the critical patch applied) and Xen 4.11, the xl.cfg file needed the following setting for the PCI passthrough configuration:</div></td>
</tr>
</table>Chuckzhttps://wiki.xenproject.org/index.php?title=Xen_VGA_Passthrough_Tested_Adapters&diff=19964&oldid=prevChuckz: /* Intel display adapters */2022-06-29T03:35:49Z<p><span dir="auto"><span class="autocomment">Intel display adapters</span></span></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 03:35, 29 June 2022</td>
</tr><tr>
<td colspan="2" class="diff-lineno">Line 46:</td>
<td colspan="2" class="diff-lineno">Line 46:</td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.14.x Headless Debian bullseye Dom0 with Debian's Qemu 5.2 package as the upstream qemu-xen device model, and the default Debian bullseye 5.10.x kernel.</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.14.x Headless Debian bullseye Dom0 with Debian's Qemu 5.2 package as the upstream qemu-xen device model, and the default Debian bullseye 5.10.x kernel.</div></td>
</tr>
<tr>
<td colspan="2" class="diff-empty"> </td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td colspan="2" class="diff-empty"> </td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.16.x Headless Debian unstable Dom0 with Debian's Qemu 7.0 package as the upstream qemu-xen device model, and the default Debian unstable 5.16.x kernel. With Linux kernel 5.17 and greater, Dom0 does not boot on some older Intel hardware due to an unpatched regression in the Linux kernel. A [https://lore.kernel.org/lkml/9385fa60-fa5d-f559-a137-6608408f88b0@suse.com/ patch] for the Linux kernel is available for this problem that only exists on certain Intel hardware but it has not been committed yet.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Not Working:</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Not Working:</div></td>
</tr>
<tr>
<td colspan="2" class="diff-lineno">Line 58:</td>
<td colspan="2" class="diff-lineno">Line 60:</td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> rdm = "strategy=host,policy=relaxed"</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> rdm = "strategy=host,policy=relaxed"</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker">−</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> For Xen 4.14 the xl.cfg file needed the following settings for the PCI passthrough configuration to successfully pass through the USB 3.0 controller with the Intel IGD and integrated sound device:</div></td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> For Xen 4.14<ins class="diffchange diffchange-inline"> and Xen 4.16</ins> the xl.cfg file needed the following settings for the PCI passthrough configuration to successfully pass through the USB 3.0 controller with the Intel IGD and integrated sound device:</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> # rdm = "strategy=host,policy=relaxed"</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> # rdm = "strategy=host,policy=relaxed"</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> pci = [ '00:1b.0','00:14.0,rdm_policy=relaxed','00:02.0' ]</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> pci = [ '00:1b.0','00:14.0,rdm_policy=relaxed','00:02.0' ]</div></td>
</tr>
<tr>
<td colspan="2" class="diff-lineno">Line 65:</td>
<td colspan="2" class="diff-lineno">Line 67:</td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> mmio_hole = '512'</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> mmio_hole = '512'</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker">−</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> With either the Debian buster or the Debian <del class="diffchange diffchange-inline">bullseye</del> Dom0, the Xen hypervisor command line options were:</div></td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> With either the Debian buster<ins class="diffchange diffchange-inline">, the Debian bullseye,</ins> or the Debian <ins class="diffchange diffchange-inline">unstable</ins> Dom0, the Xen hypervisor command line options were:</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> dom0_mem=2G,max:2G smt=false pv-l1tf=false iommu=1 no-real-mode edd=off</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> dom0_mem=2G,max:2G smt=false pv-l1tf=false iommu=1 no-real-mode edd=off</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td>
</tr>
</table>Chuckzhttps://wiki.xenproject.org/index.php?title=Xen_VGA_Passthrough_Tested_Adapters&diff=19963&oldid=prevChuckz: /* Intel display adapters */2022-06-29T03:17:36Z<p><span dir="auto"><span class="autocomment">Intel display adapters</span></span></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 03:17, 29 June 2022</td>
</tr><tr>
<td colspan="2" class="diff-lineno">Line 53:</td>
<td colspan="2" class="diff-lineno">Line 53:</td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> In all the configurations with Debian listed above, Windows 7/8/8.1/10 x86/x64 HVM guest DomUs all work well on the HDMI output with the Intel drivers provided by ASRock.</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> In all the configurations with Debian listed above, Windows 7/8/8.1/10 x86/x64 HVM guest DomUs all work well on the HDMI output with the Intel drivers provided by ASRock.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker">−</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> Debian Linux HVM guest DomUs did not always work - worked with Debian jessie Dom0 and Debian jessie DomU and the traditional device model on the HDMI output and worked with a Debian buster Dom0 with the traditional device model and Debian Linux DomUs, but only on the VGA output, not the HDMI output in the latter configuration. Does not work well with a Debian buster Dom0 (Xen 4.11), the upstream device model, and Debian Linux Domus, not even after trying many different tweaks to the configuration. The problem when using the upstream Qemu device model is that there is an unpatched bug in the upstream Qemu device model that prevents the guest from setting up IRQs from the passed through devices. A [https://www.mail-archive.com/qemu-devel@nongnu.org/msg893744.html patch] is available to fix this but it has not been committed to Qemu upstream yet. The problem when using the traditional device model is that there is a missing hypercall that is needed to grant the Linux HVM guest permission to access the Intel OpRegion. A [https://lists.xenproject.org/archives/html/xen-devel/2022-03/msg01024.html patch] to fix this problem for the traditional Qemu device model is available on xen-devel but it will not be committed due to the fact that the old traditional Qemu device model is no longer recommended for modern versions of Xen.</div></td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> Debian Linux HVM guest DomUs did not always work - worked with Debian jessie Dom0 and Debian jessie DomU and the traditional device model on the HDMI output and worked with a Debian buster Dom0 with the traditional device model and Debian Linux DomUs, but only on the VGA output, not the HDMI output in the latter configuration. Does not work well with a Debian buster<ins class="diffchange diffchange-inline"> or bullseye</ins> Dom0 (Xen 4.11<ins class="diffchange diffchange-inline"> or Xen 4.14</ins>), the upstream device model, and Debian Linux Domus, not even after trying many different tweaks to the configuration. The problem when using the upstream Qemu device model is that there is an unpatched bug in the upstream Qemu device model that prevents the guest from setting up IRQs from the passed through devices. A [https://www.mail-archive.com/qemu-devel@nongnu.org/msg893744.html patch] is available to fix this but it has not been committed to Qemu upstream yet. The problem when using the traditional device model is that there is a missing hypercall that is needed to grant the Linux HVM guest permission to access the Intel OpRegion. A [https://lists.xenproject.org/archives/html/xen-devel/2022-03/msg01024.html patch] to fix this problem for the traditional Qemu device model is available on xen-devel but it will not be committed due to the fact that the old traditional Qemu device model is no longer recommended for modern versions of Xen.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> For Xen 4.8 (with the critical patch applied) and Xen 4.11, the xl.cfg file needed the following setting for the PCI passthrough configuration:</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> For Xen 4.8 (with the critical patch applied) and Xen 4.11, the xl.cfg file needed the following setting for the PCI passthrough configuration:</div></td>
</tr>
</table>Chuckzhttps://wiki.xenproject.org/index.php?title=Xen_VGA_Passthrough_Tested_Adapters&diff=19962&oldid=prevChuckz: /* Intel display adapters */2022-06-29T03:05:53Z<p><span dir="auto"><span class="autocomment">Intel display adapters</span></span></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 03:05, 29 June 2022</td>
</tr><tr>
<td colspan="2" class="diff-lineno">Line 53:</td>
<td colspan="2" class="diff-lineno">Line 53:</td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> In all the configurations with Debian listed above, Windows 7/8/8.1/10 x86/x64 HVM guest DomUs all work well on the HDMI output with the Intel drivers provided by ASRock.</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> In all the configurations with Debian listed above, Windows 7/8/8.1/10 x86/x64 HVM guest DomUs all work well on the HDMI output with the Intel drivers provided by ASRock.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker">−</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> Debian Linux HVM guest DomUs did not always work - worked with Debian jessie Dom0 and Debian jessie DomU and the traditional device model on the HDMI output and worked with a Debian buster Dom0 with the traditional device model and Debian Linux DomUs, but only on the VGA output, not the HDMI output in the latter configuration. Does not work well with a Debian buster Dom0 (Xen 4.11), the upstream device model, and Debian Linux Domus, not even after trying many different tweaks to the configuration.</div></td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> Debian Linux HVM guest DomUs did not always work - worked with Debian jessie Dom0 and Debian jessie DomU and the traditional device model on the HDMI output and worked with a Debian buster Dom0 with the traditional device model and Debian Linux DomUs, but only on the VGA output, not the HDMI output in the latter configuration. Does not work well with a Debian buster Dom0 (Xen 4.11), the upstream device model, and Debian Linux Domus, not even after trying many different tweaks to the configuration<ins class="diffchange diffchange-inline">. The problem when using the upstream Qemu device model is that there is an unpatched bug in the upstream Qemu device model that prevents the guest from setting up IRQs from the passed through devices. A [https://www.mail-archive.com/qemu-devel@nongnu.org/msg893744.html patch] is available to fix this but it has not been committed to Qemu upstream yet. The problem when using the traditional device model is that there is a missing hypercall that is needed to grant the Linux HVM guest permission to access the Intel OpRegion. A [https://lists.xenproject.org/archives/html/xen-devel/2022-03/msg01024.html patch] to fix this problem for the traditional Qemu device model is available on xen-devel but it will not be committed due to the fact that the old traditional Qemu device model is no longer recommended for modern versions of Xen</ins>.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> For Xen 4.8 (with the critical patch applied) and Xen 4.11, the xl.cfg file needed the following setting for the PCI passthrough configuration:</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> For Xen 4.8 (with the critical patch applied) and Xen 4.11, the xl.cfg file needed the following setting for the PCI passthrough configuration:</div></td>
</tr>
<tr>
<td colspan="2" class="diff-lineno">Line 62:</td>
<td colspan="2" class="diff-lineno">Line 62:</td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> pci = [ '00:1b.0','00:14.0,rdm_policy=relaxed','00:02.0' ]</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> pci = [ '00:1b.0','00:14.0,rdm_policy=relaxed','00:02.0' ]</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td colspan="2" class="diff-empty"> </td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> If the memory assigned to the guest is greater than around 3 GB (memory = '3072'), it might be necessary to increase the mmio_hole setting in the domain configuration file. The default is 256 MB, and increasing it to 512 MB enabled memory to be greater than 4 GB:</div></td>
</tr>
<tr>
<td class="diff-marker">−</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> A limitation: In xl.cfg for the guest, memory = '3072' (3 GB) because it did not work with 4 GB and greater. I did not investigate if there is a workaround for this limitation on guest memory. Newer Intel architectures may not have this limitation. For basic productivity tasks, 3 GB is sufficient for both x86 and x64 Windows guests.</div></td>
<td colspan="2" class="diff-empty"> </td>
</tr>
<tr>
<td colspan="2" class="diff-empty"> </td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> mmio_hole = '512'</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> With either the Debian buster or the Debian bullseye Dom0, the Xen hypervisor command line options were:</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> With either the Debian buster or the Debian bullseye Dom0, the Xen hypervisor command line options were:</div></td>
</tr>
</table>Chuckzhttps://wiki.xenproject.org/index.php?title=Xen_VGA_Passthrough_Tested_Adapters&diff=19871&oldid=prevChuckz: /* Intel display adapters */ Update with information about Xen 4.142021-05-09T22:35:11Z<p><span dir="auto"><span class="autocomment">Intel display adapters: </span> Update with information about Xen 4.14</span></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 22:35, 9 May 2021</td>
</tr><tr>
<td colspan="2" class="diff-lineno">Line 44:</td>
<td colspan="2" class="diff-lineno">Line 44:</td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.11.x Headless Debian buster Dom0 with either qemu traditional or Debian's Qemu 3.1 package as the upstream qemu-xen device model, and the default Debian buster 4.19.x kernel.</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.11.x Headless Debian buster Dom0 with either qemu traditional or Debian's Qemu 3.1 package as the upstream qemu-xen device model, and the default Debian buster 4.19.x kernel.</div></td>
</tr>
<tr>
<td colspan="2" class="diff-empty"> </td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td colspan="2" class="diff-empty"> </td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> Xen 4.14.x Headless Debian bullseye Dom0 with Debian's Qemu 5.2 package as the upstream qemu-xen device model, and the default Debian bullseye 5.10.x kernel.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Not Working:</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> Not Working:</div></td>
</tr>
<tr>
<td colspan="2" class="diff-lineno">Line 55:</td>
<td colspan="2" class="diff-lineno">Line 57:</td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> For Xen 4.8 (with the critical patch applied) and Xen 4.11, the xl.cfg file needed the following setting for the PCI passthrough configuration:</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> For Xen 4.8 (with the critical patch applied) and Xen 4.11, the xl.cfg file needed the following setting for the PCI passthrough configuration:</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> rdm = "strategy=host,policy=relaxed"</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> rdm = "strategy=host,policy=relaxed"</div></td>
</tr>
<tr>
<td colspan="2" class="diff-empty"> </td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td colspan="2" class="diff-empty"> </td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> For Xen 4.14 the xl.cfg file needed the following settings for the PCI passthrough configuration to successfully pass through the USB 3.0 controller with the Intel IGD and integrated sound device:</div></td>
</tr>
<tr>
<td colspan="2" class="diff-empty"> </td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> # rdm = "strategy=host,policy=relaxed"</div></td>
</tr>
<tr>
<td colspan="2" class="diff-empty"> </td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> pci = [ '00:1b.0','00:14.0,rdm_policy=relaxed','00:02.0' ]</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> A limitation: In xl.cfg for the guest, memory = '3072' (3 GB) because it did not work with 4 GB and greater. I did not investigate if there is a workaround for this limitation on guest memory. Newer Intel architectures may not have this limitation. For basic productivity tasks, 3 GB is sufficient for both x86 and x64 Windows guests.</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> A limitation: In xl.cfg for the guest, memory = '3072' (3 GB) because it did not work with 4 GB and greater. I did not investigate if there is a workaround for this limitation on guest memory. Newer Intel architectures may not have this limitation. For basic productivity tasks, 3 GB is sufficient for both x86 and x64 Windows guests.</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> </div></td>
</tr>
<tr>
<td class="diff-marker">−</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> With the Debian buster Dom0, the Xen<del class="diffchange diffchange-inline"> 4.11</del> hypervisor command line options were:</div></td>
<td class="diff-marker">+</td>
<td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> With<ins class="diffchange diffchange-inline"> either</ins> the Debian buster<ins class="diffchange diffchange-inline"> or the Debian bullseye</ins> Dom0, the Xen hypervisor command line options were:</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> dom0_mem=2G,max:2G smt=false pv-l1tf=false iommu=1 no-real-mode edd=off</div></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div> dom0_mem=2G,max:2G smt=false pv-l1tf=false iommu=1 no-real-mode edd=off</div></td>
</tr>
<tr>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td>
<td class="diff-marker"> </td>
<td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td>
</tr>
</table>Chuckz