<div dir="ltr">Check in dmesg. If radeon try to take the card, you should have plently of log about it. If not, you are good to go. Module can be loaded without taking the card for itself. =)<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">--<div>Deldycke Quentin<br></div><div><div><br></div></div></div></div></div>
<br><div class="gmail_quote">On 18 April 2016 at 08:20, Jonas Camillus Jeppesen <span dir="ltr"><<a href="mailto:jonascj@sdu.dk" target="_blank">jonascj@sdu.dk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>So are you worried by this:<span class=""><br>
<br>
<blockquote type="cite"> # lspci -nnk<br>
04:00.0 VGA compatible controller [0300]: Advanced
Micro<br>
Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290]
[1002:67b1]<br>
Subsystem: ASUSTeK Computer Inc. Device
[1043:0470]<br>
Kernel driver in use: vfio-pci<br>
Kernel modules: radeon</blockquote>
<br></span>
That the radeon module is still in play? I have wondered myself
why it says "Kernel modules: radeon" when it should be claimed by
vfio-pci. I could try to blacklist the module, but I'll also give
all the other excellent suggestions a try.<div><div class="h5"><br>
<br>
<br>
On 04/18/2016 08:17 AM, Quentin Deldycke wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>Hello,<br>
<br>
</div>
Here is my vfio .xml:<br>
<a href="https://github.com/qdel/scripts/blob/master/vfio/win10.xml" target="_blank">https://github.com/qdel/scripts/blob/master/vfio/win10.xml</a><br>
<br>
</div>
for info, i7 4790k, asrock extreme 6 (z 97), r9 290<br>
<br>
</div>
I had in the past problem of bsod during driver install, but
not anymore using latest versions. It work nearly flawlessly.<br>
</div>
<div>I use suspend of vm while suspending the host... sometimes,
at restart the gpu crash and crash the host (1 out of 10
resume, not so good ration...) at this moment, i cannot enter
windows:<br>
<ul>
<li>After the blue windows logo, the load of driver make
crash the pc. In this case i need to enter safe mode, run
a little "display driver uninstaller", reboot reinstall
driver and re-work :).</li>
</ul>
<p>I speak of radeon, because if you switch from radeon driver
to vfio during runtime, you need to know that radeon does
not let the card in a clean state...<br>
</p>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div>
<div dir="ltr">--
<div>Deldycke Quentin<br>
</div>
<div>
<div><br>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On 18 April 2016 at 02:47, Stewart Adam
<span dir="ltr"><<a href="mailto:s.adam@diffingo.com" target="_blank">s.adam@diffingo.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I faced
similar issues with my R270, in my case *entirely removing*
the vmport=off option (its presence alone caused issues) and
attaching the GPU to a ioh3420 device instead of directly to
the PCI bus fixed the issue: <a href="https://www.redhat.com/archives/vfio-users/2015-December/msg00211.html" rel="noreferrer" target="_blank">https://www.redhat.com/archives/vfio-users/2015-December/msg00211.html</a><br>
<br>
Like many of you mention, I tried several versions from both
Catalyst and Crimson and all failed without those two
elements in my configuration. Without them, I experienced
all sorts of hangs and BSODs on driver installation or
boot-up. It's worked flawlessly, even after several guest
reboots, since adding them.<br>
<br>
This thread from January is also be relevant: <a href="https://www.redhat.com/archives/vfio-users/2016-January/msg00191.html" rel="noreferrer" target="_blank">https://www.redhat.com/archives/vfio-users/2016-January/msg00191.html</a><br>
<br>
Regards,<br>
Stewart<span><br>
<br>
On 2016-04-17 6:15 PM, Ryan Flagler wrote:<br>
</span>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
<br>
I ran an R9 280 with only the reboot issue. I believe
the most important settings for me were using the i440fx
chipset and the uefi bios.<br>
<br>
<br>
</span><span>
On Sun, Apr 17, 2016, 4:21 PM Eric Griffith <<a href="mailto:egriffith92@gmail.com" target="_blank">egriffith92@gmail.com</a>
<mailto:<a href="mailto:egriffith92@gmail.com" target="_blank">egriffith92@gmail.com</a>>>
wrote:<br>
<br>
Jonas, I've got an R9 290X and after fighting for a
few weeks with<br>
Win7/8.1/10 BSODs during driver-install, I
eventually just said "screw<br>
it" and stopped trying. It's one reason why I'm
thinking of going<br>
Nvidia for this upcoming generation<br>
<br>
On Apr 17, 2016 17:13, "Jonas Camillus Jeppesen"
<<a href="mailto:jonascj@sdu.dk" target="_blank">jonascj@sdu.dk</a><br>
</span>
<div>
<div>
<mailto:<a href="mailto:jonascj@sdu.dk" target="_blank">jonascj@sdu.dk</a>>>
wrote:<br>
<br>
I have tried both i440FX and Q35. Both seem to
produce the same<br>
result. Q35 seems to reboot/crash earlier than
i440FX, i.e.<br>
already during driver extraction before the
installation begins.<br>
As a matter of fact the Q35 install is not
stable at all, it<br>
reboots/crashes after roughly 1min no matter
what I do (idle on<br>
desktop, at login screen, installing driver,
etc.).<br>
<br>
To answer a question by Quentin which went to
me directly instead<br>
of the list:<br>
<br>
On 04/17/2016 10:21 PM, Quentin Deldycke
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hello,<br>
<br>
I have same gpu nearly same processor, and
no problems.<br>
<br>
I can install drivers without problem. Even
very last ones.<br>
<br>
I will send further information tomorrow as
I am not on this pc<br>
right now :)<br>
<br>
Does Radeon was loaded before you switch to
vfio-pci? (what was<br>
using card at boot)<br>
<br>
</blockquote>
<br>
What do you mean if Radeon was loaded before
switching to vfio-pci?<br>
<br>
First I configured my host to make vfio-pci
claim the radeon card<br>
as described here (/etc/modprobe.d/vfio.conf
with IDs to be<br>
claimed):<br>
<a href="https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#vfio-pci" rel="noreferrer" target="_blank">https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#vfio-pci</a><br>
<br>
Then I install Windows 10 using virt-manager
and its provided<br>
display (SPICE/VNC). Once the system is
configured with an VNC<br>
server (or Synergy for sharing mouse/keyboard)
I shutdown, remove<br>
all SPICE/VNC adapters, add my Radeon gpu and
boot the guest<br>
again. This time the graphics output appears
on the monitor<br>
connected to the Radeon GPU, and I would
expect that I could just<br>
install the Radeon driver at this point, but
apparently not.<br>
<br>
I haven't tried installing Windows with the
Radeon GPU passed<br>
through during installation, I will try that
next.<br>
<br>
<br>
On 04/17/2016 10:51 PM, Ryan Flagler wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>
<br>
What chipset emulation are you using?<br>
<br>
<br>
On Sun, Apr 17, 2016, 3:17 PM Jonas Camillus
Jeppesen<br>
</div>
</div>
<div>
<div>
<<a href="mailto:jonascj@sdu.dk" target="_blank">jonascj@sdu.dk</a>
<mailto:<a href="mailto:jonascj@sdu.dk" target="_blank">jonascj@sdu.dk</a>>>
wrote:<br>
<br>
Hello everyone<br>
<br>
Anyone having Windows 10 guests with
Radeon R9 290 passed<br>
through via VFIO, and if so, did you
experience any problems<br>
installing drivers?<br>
<br>
I have a R9290-DC2OC-4GD5 passed through
to a Windows 10<br>
guest (build 10586.104, newest ISO from
Microsoft.com), and<br>
at first glance everything seems fine. I
get output on my R9<br>
290 GPU when I start my guest, Windows
10 boots, I am able to<br>
login etc., but I am stuck with some
built-in Microsoft<br>
display driver because the Win10 guest
reboots/BSODs when I<br>
try to install the AMD drivers.<br>
<br>
Device manager on the guest shows a
"Video Controller (VGA<br>
Compatible)" and its VEN_ID and DEV_ID
indicates that it is<br>
the AMD R9 GPU. Regardless of whether I
go through AMD's<br>
driver installer, or if I right-click
this device and update<br>
driver the guest reboots during the
installation.<br>
<br>
I have tried different AMD driver
verisons, but you can only<br>
go so far back before it complains that
the driver does not<br>
support this version of Windows (i.e.
version <14 does not<br>
support Win10).<br>
<br>
Any suggestions as to what I might try
to resolve this, or<br>
anyone with similar problems?<br>
<br>
Thank you for reading,<br>
JonasCJ<br>
<br>
- - - - - - - - - - - - -<br>
<br>
My config / setup is this:<br>
<br>
Arch Linux, kernel 4.5.0, unpatched<br>
CPU: Intel i7-4770<br>
Guest GPU: R9290-DC2OC-4GD5<br>
Host GPU: Built-in Intel i7 gpu<br>
Motherboard: ASROCK Z87M Extreme 4 (GPU
in PCI-E port 4)<br>
<br>
I assume the basics are working since I
get output on my<br>
guest gpu and no immediate BSODs/reboots
etc., but for the<br>
sake of completeness:<br>
<br>
# lspci -nnk<br>
04:00.0 VGA compatible controller
[0300]: Advanced Micro<br>
Devices, Inc. [AMD/ATI] Hawaii PRO
[Radeon R9 290] [1002:67b1]<br>
Subsystem: ASUSTeK Computer Inc.
Device [1043:0470]<br>
Kernel driver in use: vfio-pci<br>
Kernel modules: radeon<br>
04:00.1 Audio device [0403]: Advanced
Micro Devices, Inc.<br>
[AMD/ATI] Hawaii HDMI Audio [1002:aac8]<br>
Subsystem: ASUSTeK Computer Inc.
Device [1043:aac8]<br>
Kernel driver in use: vfio-pci<br>
Kernel modules: snd_hda_intel<br>
<br>
<br>
# IOMMU groups listed as described here:<br>
<a href="https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#Ensuring_that_the_groups_are_valid" rel="noreferrer" target="_blank">https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#Ensuring_that_the_groups_are_valid</a><br>
IOMMU group 0<br>
00:00.0 Host bridge [0600]:
Intel Corporation 4th Gen<br>
Core Processor DRAM Controller
[8086:0c00] (rev 06)<br>
IOMMU group 1<br>
00:01.0 PCI bridge [0604]: Intel
Corporation Xeon<br>
E3-1200 v3/4th Gen Core Processor PCI
Express x16 Controller<br>
[8086:0c01] (rev 06)<br>
IOMMU group 2<br>
00:02.0 VGA compatible
controller [0300]: Intel<br>
Corporation Xeon E3-1200 v3/4th Gen Core
Processor Integrated<br>
Graphics Controller [8086:0412] (rev 06)<br>
IOMMU group 3<br>
00:03.0 Audio device [0403]:
Intel Corporation Xeon<br>
E3-1200 v3/4th Gen Core Processor HD
Audio Controller<br>
[8086:0c0c] (rev 06)<br>
IOMMU group 4<br>
00:14.0 USB controller [0c03]:
Intel Corporation 8<br>
Series/C220 Series Chipset Family USB
xHCI [8086:8c31] (rev 05)<br>
IOMMU group 5<br>
00:16.0 Communication controller
[0780]: Intel<br>
Corporation 8 Series/C220 Series Chipset
Family MEI<br>
Controller #1 [8086:8c3a] (rev 04)<br>
IOMMU group 6<br>
00:19.0 Ethernet controller
[0200]: Intel Corporation<br>
Ethernet Connection I217-V [8086:153b]
(rev 05)<br>
IOMMU group 7<br>
00:1a.0 USB controller [0c03]:
Intel Corporation 8<br>
Series/C220 Series Chipset Family USB
EHCI #2 [8086:8c2d]<br>
(rev 05)<br>
IOMMU group 8<br>
00:1b.0 Audio device [0403]:
Intel Corporation 8<br>
Series/C220 Series Chipset High
Definition Audio Controller<br>
[8086:8c20] (rev 05)<br>
IOMMU group 9<br>
00:1c.0 PCI bridge [0604]: Intel
Corporation 8<br>
Series/C220 Series Chipset Family PCI
Express Root Port #1<br>
[8086:8c10] (rev d5)<br>
IOMMU group 10<br>
00:1c.3 PCI bridge [0604]: Intel
Corporation 8<br>
Series/C220 Series Chipset Family PCI
Express Root Port #4<br>
[8086:8c16] (rev d5)<br>
IOMMU group 11<br>
00:1c.4 PCI bridge [0604]: Intel
Corporation 8<br>
Series/C220 Series Chipset Family PCI
Express Root Port #5<br>
[8086:8c18] (rev d5)<br>
IOMMU group 12<br>
00:1d.0 USB controller [0c03]:
Intel Corporation 8<br>
Series/C220 Series Chipset Family USB
EHCI #1 [8086:8c26]<br>
(rev 05)<br>
IOMMU group 13<br>
00:1f.0 ISA bridge [0601]: Intel
Corporation Z87<br>
Express LPC Controller [8086:8c44] (rev
05)<br>
00:1f.2 SATA controller [0106]:
Intel Corporation 8<br>
Series/C220 Series Chipset Family 6-port
SATA Controller 1<br>
[AHCI mode] [8086:8c02] (rev 05)<br>
00:1f.3 SMBus [0c05]: Intel
Corporation 8 Series/C220<br>
Series Chipset Family SMBus Controller
[8086:8c22] (rev 05)<br>
IOMMU group 14<br>
04:00.0 VGA compatible
controller [0300]: Advanced<br>
Micro Devices, Inc. [AMD/ATI] Hawaii PRO
[Radeon R9 290]<br>
[1002:67b1]<br>
04:00.1 Audio device [0403]:
Advanced Micro Devices,<br>
Inc. [AMD/ATI] Hawaii HDMI Audio
[1002:aac8]<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
vfio-users mailing list<br>
</div>
</div>
<a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a>
<mailto:<a href="mailto:vfio-users@redhat.com" target="_blank">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>
<br>
<br>
_______________________________________________<br>
vfio-users mailing list<br>
<a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a>
<mailto:<a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a>><span><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>
<br>
<br>
_______________________________________________<br>
vfio-users mailing list<br>
<a href="mailto:vfio-users@redhat.com" target="_blank">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>
</span></blockquote>
<div>
<div>
<br>
_______________________________________________<br>
vfio-users mailing list<br>
<a href="mailto:vfio-users@redhat.com" target="_blank">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>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>