[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [vfio-users] Radeon R9 290 passthrough to Win10 guest - bsod/reboot on driver install



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. =)

--
Deldycke Quentin


On 18 April 2016 at 08:20, Jonas Camillus Jeppesen <jonascj sdu dk> wrote:
So are you worried by this:

            # lspci -nnk
            04:00.0 VGA compatible controller [0300]: Advanced Micro
            Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1]
                    Subsystem: ASUSTeK Computer Inc. Device [1043:0470]
                    Kernel driver in use: vfio-pci
                    Kernel modules: radeon

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.



On 04/18/2016 08:17 AM, Quentin Deldycke wrote:
for info, i7 4790k, asrock extreme 6 (z 97), r9 290

I had in the past problem of bsod during driver install, but not anymore using latest versions. It work nearly flawlessly.
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:
  • 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 :).

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...



--
Deldycke Quentin


On 18 April 2016 at 02:47, Stewart Adam <s adam diffingo com> wrote:
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: https://www.redhat.com/archives/vfio-users/2015-December/msg00211.html

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.

This thread from January is also be relevant: https://www.redhat.com/archives/vfio-users/2016-January/msg00191.html

Regards,
Stewart

On 2016-04-17 6:15 PM, Ryan Flagler wrote:

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.


On Sun, Apr 17, 2016, 4:21 PM Eric Griffith <egriffith92 gmail com <mailto:egriffith92 gmail com>> wrote:

    Jonas, I've got an R9 290X and after fighting for a few weeks with
    Win7/8.1/10 BSODs during driver-install, I eventually just said "screw
    it" and stopped trying. It's one reason why I'm thinking of going
    Nvidia for this upcoming generation

    On Apr 17, 2016 17:13, "Jonas Camillus Jeppesen" <jonascj sdu dk
    <mailto:jonascj sdu dk>> wrote:

        I have tried both i440FX and Q35. Both seem to produce the same
        result. Q35 seems to reboot/crash earlier than i440FX, i.e.
        already during driver extraction before the installation begins.
        As a matter of fact the Q35 install is not stable at all, it
        reboots/crashes after roughly 1min no matter what I do (idle on
        desktop, at login screen, installing driver, etc.).

        To answer a question by Quentin which went to me directly instead
        of the list:

        On 04/17/2016 10:21 PM, Quentin Deldycke wrote:

        Hello,

        I have same gpu nearly same processor, and no problems.

        I can install drivers without problem. Even very last ones.

        I will send further information tomorrow as I am not on this pc
        right now :)

        Does Radeon was loaded before you switch to vfio-pci?  (what was
        using card at boot)


        What do you mean if Radeon was loaded before switching to vfio-pci?

        First I configured my host to make vfio-pci claim the radeon card
        as described here (/etc/modprobe.d/vfio.conf with IDs to be
        claimed):
        https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#vfio-pci

        Then I install Windows 10 using virt-manager and its provided
        display (SPICE/VNC). Once the system is configured with an VNC
        server (or Synergy for sharing mouse/keyboard) I shutdown, remove
        all SPICE/VNC adapters, add my Radeon gpu and boot the guest
        again. This time the graphics output appears on the monitor
        connected to the Radeon GPU, and I would expect that I could just
        install the Radeon driver at this point, but apparently not.

        I haven't tried installing Windows with the Radeon GPU passed
        through during installation, I will try that next.


        On 04/17/2016 10:51 PM, Ryan Flagler wrote:

        What chipset emulation are you using?


        On Sun, Apr 17, 2016, 3:17 PM Jonas Camillus Jeppesen
        <jonascj sdu dk <mailto:jonascj sdu dk>> wrote:

            Hello everyone

            Anyone having Windows 10 guests with Radeon R9 290 passed
            through via VFIO, and if so, did you experience any problems
            installing drivers?

            I have a R9290-DC2OC-4GD5 passed through to a Windows 10
            guest (build 10586.104, newest ISO from Microsoft.com), and
            at first glance everything seems fine. I get output on my R9
            290 GPU when I start my guest, Windows 10 boots, I am able to
            login etc., but I am stuck with some built-in Microsoft
            display driver because the Win10 guest reboots/BSODs when I
            try to install the AMD drivers.

            Device manager on the guest shows a "Video Controller (VGA
            Compatible)" and its VEN_ID and DEV_ID indicates that it is
            the AMD R9 GPU. Regardless of whether I go through AMD's
            driver installer, or if I right-click this device and update
            driver the guest reboots during the installation.

            I have tried different AMD driver verisons, but you can only
            go so far back before it complains that the driver does not
            support this version of Windows (i.e. version <14 does not
            support Win10).

            Any suggestions as to what I might try to resolve this, or
            anyone with similar problems?

            Thank you for reading,
            JonasCJ

            - - - - - - - - - - - - -

            My config / setup is this:

            Arch Linux, kernel 4.5.0, unpatched
            CPU: Intel i7-4770
            Guest GPU: R9290-DC2OC-4GD5
            Host GPU: Built-in Intel i7 gpu
            Motherboard: ASROCK Z87M Extreme 4 (GPU in PCI-E port 4)

            I assume the basics are working since I get output on my
            guest gpu and no immediate BSODs/reboots etc., but for the
            sake of completeness:

            # lspci -nnk
            04:00.0 VGA compatible controller [0300]: Advanced Micro
            Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1]
                    Subsystem: ASUSTeK Computer Inc. Device [1043:0470]
                    Kernel driver in use: vfio-pci
                    Kernel modules: radeon
            04:00.1 Audio device [0403]: Advanced Micro Devices, Inc.
            [AMD/ATI] Hawaii HDMI Audio [1002:aac8]
                    Subsystem: ASUSTeK Computer Inc. Device [1043:aac8]
                    Kernel driver in use: vfio-pci
                    Kernel modules: snd_hda_intel


            # IOMMU groups listed as described here:
            https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#Ensuring_that_the_groups_are_valid
            IOMMU group 0
                    00:00.0 Host bridge [0600]: Intel Corporation 4th Gen
            Core Processor DRAM Controller [8086:0c00] (rev 06)
            IOMMU group 1
                    00:01.0 PCI bridge [0604]: Intel Corporation Xeon
            E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller
            [8086:0c01] (rev 06)
            IOMMU group 2
                    00:02.0 VGA compatible controller [0300]: Intel
            Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated
            Graphics Controller [8086:0412] (rev 06)
            IOMMU group 3
                    00:03.0 Audio device [0403]: Intel Corporation Xeon
            E3-1200 v3/4th Gen Core Processor HD Audio Controller
            [8086:0c0c] (rev 06)
            IOMMU group 4
                    00:14.0 USB controller [0c03]: Intel Corporation 8
            Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 05)
            IOMMU group 5
                    00:16.0 Communication controller [0780]: Intel
            Corporation 8 Series/C220 Series Chipset Family MEI
            Controller #1 [8086:8c3a] (rev 04)
            IOMMU group 6
                    00:19.0 Ethernet controller [0200]: Intel Corporation
            Ethernet Connection I217-V [8086:153b] (rev 05)
            IOMMU group 7
                    00:1a.0 USB controller [0c03]: Intel Corporation 8
            Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d]
            (rev 05)
            IOMMU group 8
                    00:1b.0 Audio device [0403]: Intel Corporation 8
            Series/C220 Series Chipset High Definition Audio Controller
            [8086:8c20] (rev 05)
            IOMMU group 9
                    00:1c.0 PCI bridge [0604]: Intel Corporation 8
            Series/C220 Series Chipset Family PCI Express Root Port #1
            [8086:8c10] (rev d5)
            IOMMU group 10
                    00:1c.3 PCI bridge [0604]: Intel Corporation 8
            Series/C220 Series Chipset Family PCI Express Root Port #4
            [8086:8c16] (rev d5)
            IOMMU group 11
                    00:1c.4 PCI bridge [0604]: Intel Corporation 8
            Series/C220 Series Chipset Family PCI Express Root Port #5
            [8086:8c18] (rev d5)
            IOMMU group 12
                    00:1d.0 USB controller [0c03]: Intel Corporation 8
            Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26]
            (rev 05)
            IOMMU group 13
                    00:1f.0 ISA bridge [0601]: Intel Corporation Z87
            Express LPC Controller [8086:8c44] (rev 05)
                    00:1f.2 SATA controller [0106]: Intel Corporation 8
            Series/C220 Series Chipset Family 6-port SATA Controller 1
            [AHCI mode] [8086:8c02] (rev 05)
                    00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220
            Series Chipset Family SMBus Controller [8086:8c22] (rev 05)
            IOMMU group 14
                    04:00.0 VGA compatible controller [0300]: Advanced
            Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290]
            [1002:67b1]
                    04:00.1 Audio device [0403]: Advanced Micro Devices,
            Inc. [AMD/ATI] Hawaii HDMI Audio [1002:aac8]






            _______________________________________________
            vfio-users mailing list
            vfio-users redhat com <mailto:vfio-users redhat com>
            https://www.redhat.com/mailman/listinfo/vfio-users



        _______________________________________________
        vfio-users mailing list
        vfio-users redhat com <mailto:vfio-users redhat com>
        https://www.redhat.com/mailman/listinfo/vfio-users



_______________________________________________
vfio-users mailing list
vfio-users redhat com
https://www.redhat.com/mailman/listinfo/vfio-users

_______________________________________________
vfio-users mailing list
vfio-users redhat com
https://www.redhat.com/mailman/listinfo/vfio-users




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]