<p dir="ltr">Gigabyte motherboards allow you to select your primary GPU, but it is only relevant to VGA.<br>
Doing nvidia+amd is good because you can be 100% sure that the host driver won't bind the VM GPU.<br>
I personally have a gt610 paired with hd 7750 and it is totally fine.</p>
<div class="gmail_quote">On Sep 17, 2015 12:34 PM, "Janusz" <<a href="mailto:januszmk6@gmail.com">januszmk6@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>I think its problem with kernel
>=4.2 and ovmf, I cant test it on 4.1 because i915 support for
skylake there is preliminary and I am getting kernel panic at host
boot, so I am thinking about buying cheap another GPU card that
will support 3 monitors (2x 1920x1080 + 1x 2560x1440), is this
possible to setup that my system will use one card (how can I be
sure my motherboard will boot from right GPU?) and I set another
one for vga passthrough? will there be a problem if I would have
one nvidia and one amd gpu?<br>
I include one more time my hw if it is relevant: i7 6700k, msi
z170a M7<br>
My iommu groups:<br>
<br>
/sys/kernel/iommu_groups/0/devices/0000:00:00.0<br>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">/sys/kernel/iommu_groups/1/devices/0000:00:01.0<br>
/sys/kernel/iommu_groups/1/devices/0000:01:00.0<br>
/sys/kernel/iommu_groups/1/devices/0000:01:00.1<br>
</blockquote>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">/sys/kernel/iommu_groups/2/devices/0000:00:02.0<br>
/sys/kernel/iommu_groups/3/devices/0000:00:08.0<br>
/sys/kernel/iommu_groups/4/devices/0000:00:14.0<br>
/sys/kernel/iommu_groups/4/devices/0000:00:14.2<br>
/sys/kernel/iommu_groups/5/devices/0000:00:15.0<br>
/sys/kernel/iommu_groups/5/devices/0000:00:15.1<br>
/sys/kernel/iommu_groups/6/devices/0000:00:16.0<br>
/sys/kernel/iommu_groups/7/devices/0000:00:17.0<br>
</blockquote>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">/sys/kernel/iommu_groups/8/devices/0000:00:1c.0<br>
/sys/kernel/iommu_groups/8/devices/0000:00:1c.2<br>
/sys/kernel/iommu_groups/8/devices/0000:00:1c.7<br>
/sys/kernel/iommu_groups/8/devices/0000:02:00.0<br>
/sys/kernel/iommu_groups/8/devices/0000:03:00.0<br>
/sys/kernel/iommu_groups/8/devices/0000:04:00.0</blockquote>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">/sys/kernel/iommu_groups/9/devices/0000:00:1e.0<br>
/sys/kernel/iommu_groups/10/devices/0000:00:1f.0<br>
/sys/kernel/iommu_groups/10/devices/0000:00:1f.2<br>
/sys/kernel/iommu_groups/10/devices/0000:00:1f.3<br>
/sys/kernel/iommu_groups/10/devices/0000:00:1f.4<br>
<br>
and lspci:<br>
<br>
00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM<br>
Registers (rev 07)<br>
</blockquote>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">00:01.0
PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16)<br>
(rev 07)<br>
</blockquote>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">00:02.0
VGA compatible controller: Intel Corporation Sky Lake Integrated<br>
Graphics (rev 06)<br>
</blockquote>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">00:08.0
System peripheral: Intel Corporation Sky Lake Gaussian Mixture
Model<br>
</blockquote>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">00:14.0
USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI<br>
Controller (rev 31)<br>
00:14.2 Signal processing controller: Intel Corporation Sunrise
Point-H<br>
Thermal subsystem (rev 31)<br>
</blockquote>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">00:15.0
Signal processing controller: Intel Corporation Sunrise Point-H<br>
LPSS I2C Controller #0 (rev 31)<br>
00:15.1 Signal processing controller: Intel Corporation Sunrise
Point-H<br>
LPSS I2C Controller #1 (rev 31)<br>
</blockquote>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">00:16.0
Communication controller: Intel Corporation Sunrise Point-H CSME<br>
HECI #1 (rev 31)<br>
</blockquote>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">00:17.0
SATA controller: Intel Corporation Device a102 (rev 31)<br>
</blockquote>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">00:1c.0
PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root<br>
Port #1 (rev f1)<br>
00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI
Express Root<br>
Port #3 (rev f1)<br>
00:1c.7 PCI bridge: Intel Corporation Sunrise Point-H PCI
Express Root<br>
Port #8 (rev f1)<br>
00:1e.0 Signal processing controller: Intel Corporation Sunrise
Point-H<br>
LPSS UART #0 (rev 31)<br>
</blockquote>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">00:1f.0
ISA bridge: Intel Corporation Sunrise Point-H LPC Controller<br>
(rev 31)<br>
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC
(rev 31)<br>
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio
(rev 31)<br>
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)<br>
</blockquote>
<br>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">01:00.0
VGA compatible controller: Advanced Micro Devices, Inc.<br>
[AMD/ATI] Hawaii PRO [Radeon R9 290]</blockquote>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">01:00.1
Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aac8<br>
</blockquote>
<div> </div>
02:00.0 USB controller: ASMedia Technology Inc. Device 1242<br>
03:00.0 Ethernet controller: Qualcomm Atheros Device e0a1 (rev 10)<br>
04:00.0 Ethernet controller: Broadcom Corporation NetXtreme
BCM5721<br>
Gigabit Ethernet PCI Express (rev 21)<br>
<br>
<br>
W dniu 13.09.2015 o 15:44, Okky Hendriansyah pisze:<br>
</div>
<blockquote type="cite">
<pre>I assume you're installing with QEMU machine model Q35, have you tried with model i440FX also?
Best regards,
Okky Hendriansyah
</pre>
<blockquote type="cite">
<pre>On Sep 13, 2015, at 20:15, Janusz <a href="mailto:januszmk6@gmail.com" target="_blank"><januszmk6@gmail.com></a> wrote:
W dniu 13.09.2015 o 15:08, Okky Hendriansyah pisze:
</pre>
<blockquote type="cite">
<pre>Hi Janus,
Are you trying to upgrade to Windows 10? I had issues when upgrading from Windows 8.1 to Windows 10, after changing the cpu to "core2duo", the upgrade finished and I quickly revert back to "host" on my first reboot.
Best regards,
Okky Hendriansyah
</pre>
</blockquote>
<pre>no upgrade, I had clean installation on uefi platform done without
passing through my gpu, but when I limited threads to 1 windows was
unable to boot - every time it reboots it self. I reinstalled windows
10, but still have problem that its sometimes reseting it self while
loading (no bsod just reset), and just installed windows 8.1, the same
problem. The installation both win10 and win8.1 went without problems.
</pre>
<blockquote type="cite">
<pre>
</pre>
<blockquote type="cite">
<pre>On Sep 13, 2015, at 18:21, Janusz <a href="mailto:januszmk6@gmail.com" target="_blank"><januszmk6@gmail.com></a> wrote:
W dniu 13.09.2015 o 00:28, Blank Field pisze:
</pre>
<blockquote type="cite">
<pre>Looking at IOMMU groups, his lspci and his problems, there's no way
anyone would want to take intel for VFIO usage.
Good lord, that's worse than my system...
</pre>
<blockquote type="cite">
<pre>No BSOD, only silent reboot or reset on uefi bios display, also reset
issue for gpu (that was already fixed I think in some kernel/qemu
version for hawaii, monitor still gets old display sometimes after
turining off or reset VM), in dmesg I found only those:
[10145.621272] vgaarb: device changed decodes:
PCI:0000:01:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[10145.641778] vgaarb: device changed decodes:
PCI:0000:01:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[10145.760058] [drm:check_wm_state] *ERROR* mismatch in DDB state
pipe A plane 1 (expected (0,0), found (0,289))
[10145.760061] [drm:check_wm_state] *ERROR* mismatch in DDB state
pipe A cursor (expected (0,0), found (289,297))
[10145.760062] [drm:check_wm_state] *ERROR* mismatch in DDB state
pipe B plane 1 (expected (0,0), found (297,586))
[10145.760063] [drm:check_wm_state] *ERROR* mismatch in DDB state
pipe B cursor (expected (0,0), found (586,594))
[10148.490876] vfio_ecap_init: 0000:01:00.0 hiding ecap 0x19@0x270
[10148.490881] vfio_ecap_init: 0000:01:00.0 hiding ecap 0x1b@0x2d0
[10154.080574] usb 1-12: reset low-speed USB device number 5 using
xhci_hcd
[10154.372122] usb 1-12: ep 0x81 - rounding interval to 64
microframes, ep desc says 80 microframes
[10194.443399] kvm: zapping shadow pages for mmio generation wraparound
[10194.453708] kvm: zapping shadow pages for mmio generation wraparound
[10165.930150] usb 1-12: ep 0x81 - rounding interval to 64
microframes, ep desc says 80 microframes
[10168.912066] usb 1-12: reset low-speed USB device number 5 using
xhci_hcd
[10169.203902] usb 1-12: ep 0x81 - rounding interval to 64
microframes, ep desc says 80 microframes
I can be missing something as I get lot of warnings from i915 driver
(known bug for i915 and skylake), but I did grep for kvm and vfio and
didn't find anything else
I am running now dev version of qemu because I wanted to test if
newer version will give better result (it didn't), and didn't
compiled back the stable version yet
</pre>
</blockquote>
<pre>And yes, I have AMD Catalyst drivers installed in the guest, but as
this also happening before it starts to boot windows and when starting
windows installation, I don't think this is the reason
</pre>
</blockquote>
<pre>I think I found some solution. I changed number of threads on cpu from 2
to 1, and windows installation is starting every time now. problem still
is with installed windows - its rebooting every time it wants to start
win10, is windows sensitive for such changes?
When I changed number of threads to 2 and number of cores to 3, problem
still occurs
Also, I upgraded to kernel 4.3-r1
I find that someone reported issue to OVMF that it has problems with
kernel >= 4.2 <a href="https://github.com/tianocore/edk2/issues/21" target="_blank">https://github.com/tianocore/edk2/issues/21</a>, unfortunately
I am not able to test it on 4.1 or 4.0 as on 4.1 I get some weird
operations on null pointer in kernel at boot - segfault, and in 4.0 I
don't even get signal to monitor - probably hardware is too new for
those versions (I know about i915 preliminary support but its not working)
anyway, I am gonna test futher later, and see if with threads=1,cores=4
will problem still occur after reinstalling win10
_______________________________________________
vfio-users mailing list
<a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a>
<a href="https://www.redhat.com/mailman/listinfo/vfio-users" target="_blank">https://www.redhat.com/mailman/listinfo/vfio-users</a>
</pre>
</blockquote>
</blockquote>
<pre>
</pre>
</blockquote>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
vfio-users mailing list<br>
<a href="mailto:vfio-users@redhat.com">vfio-users@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/vfio-users" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/vfio-users</a><br>
<br></blockquote></div>