You are not logged in.

#1 2020-04-12 21:05:27

lolop
Member
Registered: 2015-02-19
Posts: 37

[Solved] Passthrough card graphic vega8

Hello,

I have 2 gpu on my machine:
lspci -nn | grep VGA
             01: 00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD / ATI] Baffin [Radeon Pro WX 4100] [1002: 67e3]
             09: 00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD / ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002: 15dd] (rev c8)

I have configured my system to use passthrough on the vega chipset:
sudo dmesg | grep -i vfio
            [7.615963] VFIO - User Level meta-driver version: 0.3
            [7.627976] vfio-pci 0000: 09: 00.0 : vgaarb: changed VGA decodes: olddecodes = io + mem, decodes = io + mem: owns = none
            [7.646875] vfio_pci: add [1002: 15dd [ffffffff: ffffffff]] class 0x000000 / 00000000
            [13.130571] vfio-pci 0000: 09: 00.0:  vgaarb: changed VGA decodes: olddecodes = io + mem, decodes = io + mem: owns = none

lspci -nnk -d 1002: 15dd
            09: 00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD / ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002: 15dd] (rev c8)
            Subsystem: ASUSTeK Computer Inc. Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1043: 876b]
            Kernel driver in use: vfio-pci
            Kernel modules: amdgpu

I configured a guest with virt-manager by adding the card in question and deleted QXL and spice.

Already when I start the guest my machine is slowed down I pers the use of my Corsair Gaming SABER mouse via daemon ckb-next.
In short, I plug another mouse into USB and switch the screen connected to the Vega chipset, but there is nothing.
And the pc starts to crash and I can't find a log.

Do you have any tracks to explore?

Thank you

Last edited by lolop (2020-04-19 20:14:13)

Offline

#2 2020-04-13 12:21:51

lolop
Member
Registered: 2015-02-19
Posts: 37

Re: [Solved] Passthrough card graphic vega8

I come to clarify with a dmesg which gets carried away at the launch of the vm:

[ 1959.169380] vfio-pci 0000:09:00.0: enabling device (0000 -> 0003)
[ 1959.276077] vfio-pci 0000:09:00.0: vfio_ecap_init: hiding ecap 0x19@0x270
[ 1959.276097] vfio-pci 0000:09:00.0: vfio_ecap_init: hiding ecap 0x1b@0x2d0
[ 1960.015241] virbr0: port 2(vnet0) entered learning state
[ 1961.976336] AMD-Vi: Completion-Wait loop timed out
[ 1962.117486] AMD-Vi: Completion-Wait loop timed out
[ 1962.147093] virbr0: port 2(vnet0) entered forwarding state
[ 1962.147095] virbr0: topology change detected, propagating
[ 1962.253630] AMD-Vi: Completion-Wait loop timed out
[ 1962.394779] AMD-Vi: Completion-Wait loop timed out
[ 1962.530922] AMD-Vi: Completion-Wait loop timed out
[ 1962.661057] AMD-Vi: Completion-Wait loop timed out
[ 1962.661348] r8168 0000:06:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0xfec7f8e0 flags=0x0050]
[ 1962.661355] r8168 0000:06:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0xfec7f900 flags=0x0050]
[ 1962.786190] AMD-Vi: Completion-Wait loop timed out
[ 1962.841171] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=09:00.0 address=0x42ed8a640]
[ 1962.977333] AMD-Vi: Completion-Wait loop timed out
[ 1963.102467] AMD-Vi: Completion-Wait loop timed out
[ 1963.238610] AMD-Vi: Completion-Wait loop timed out
[ 1963.363742] AMD-Vi: Completion-Wait loop timed out
[ 1963.499885] AMD-Vi: Completion-Wait loop timed out
[ 1963.641111] AMD-Vi: Completion-Wait loop timed out
[ 1963.777255] AMD-Vi: Completion-Wait loop timed out
[ 1963.842189] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=09:00.0 address=0x42ed8a710]
[ 1963.978329] AMD-Vi: Completion-Wait loop timed out
[ 1964.108467] AMD-Vi: Completion-Wait loop timed out
[ 1964.244628] AMD-Vi: Completion-Wait loop timed out
[ 1964.374766] AMD-Vi: Completion-Wait loop timed out
[ 1964.510908] AMD-Vi: Completion-Wait loop timed out
[ 1964.641044] AMD-Vi: Completion-Wait loop timed out
[ 1964.777186] AMD-Vi: Completion-Wait loop timed out
[ 1964.843326] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=09:00.0 address=0x42ed8a780]
[ 1964.980757] AMD-Vi: Completion-Wait loop timed out
[ 1965.117484] AMD-Vi: Completion-Wait loop timed out
[ 1965.247620] AMD-Vi: Completion-Wait loop timed out
[ 1965.383763] AMD-Vi: Completion-Wait loop timed out
[ 1965.520066] AMD-Vi: Completion-Wait loop timed out
[ 1965.656836] AMD-Vi: Completion-Wait loop timed out
[ 1965.794025] AMD-Vi: Completion-Wait loop timed out
[ 1965.844226] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=09:00.0 address=0x42ed8a7f0]
[ 1965.980359] AMD-Vi: Completion-Wait loop timed out
[ 1966.117050] AMD-Vi: Completion-Wait loop timed out
[ 1966.254147] AMD-Vi: Completion-Wait loop timed out
[ 1966.390311] AMD-Vi: Completion-Wait loop timed out
[ 1966.526530] AMD-Vi: Completion-Wait loop timed out
[ 1966.662690] AMD-Vi: Completion-Wait loop timed out
[ 1966.798849] AMD-Vi: Completion-Wait loop timed out
[ 1966.845246] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=09:00.0 address=0x42ed8a840]
[ 1966.981378] AMD-Vi: Completion-Wait loop timed out
[ 1967.118743] AMD-Vi: Completion-Wait loop timed out
[ 1967.255998] AMD-Vi: Completion-Wait loop timed out
[ 1967.392966] AMD-Vi: Completion-Wait loop timed out
[ 1967.529182] AMD-Vi: Completion-Wait loop timed out
[ 1967.665895] AMD-Vi: Completion-Wait loop timed out
[ 1967.803007] AMD-Vi: Completion-Wait loop timed out
[ 1967.846264] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=09:00.0 address=0x42ed8a890]
[ 1967.903290] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
[ 1967.903398] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
[ 1967.903502] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
[ 1967.982400] AMD-Vi: Completion-Wait loop timed out
[ 1968.119527] AMD-Vi: Completion-Wait loop timed out
[ 1968.256926] AMD-Vi: Completion-Wait loop timed out
[ 1968.393874] AMD-Vi: Completion-Wait loop timed out
[ 1968.530333] AMD-Vi: Completion-Wait loop timed out
[ 1968.667244] AMD-Vi: Completion-Wait loop timed out
[ 1968.804111] AMD-Vi: Completion-Wait loop timed out
[ 1968.847282] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=09:00.0 address=0x42ed8a8e0]
[ 1968.983420] AMD-Vi: Completion-Wait loop timed out
[ 1969.120772] AMD-Vi: Completion-Wait loop timed out
[ 1969.257133] AMD-Vi: Completion-Wait loop timed out
[ 1969.393953] AMD-Vi: Completion-Wait loop timed out
[ 1969.530750] AMD-Vi: Completion-Wait loop timed out
[ 1969.608700] xhci_hcd 0000:09:00.4: xHCI host not responding to stop endpoint command.
[ 1969.608722] xhci_hcd 0000:09:00.4: xHCI host controller not responding, assume dead
[ 1969.608730] xhci_hcd 0000:09:00.4: HC died; cleaning up
[ 1969.608743] usb 5-1: USB disconnect, device number 2
[ 1969.668395] AMD-Vi: Completion-Wait loop timed out
[ 1969.809663] AMD-Vi: Completion-Wait loop timed out
[ 1969.848300] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=09:00.0 address=0x42ed8a950]
[ 1969.984437] AMD-Vi: Completion-Wait loop timed out
[ 1970.120592] AMD-Vi: Completion-Wait loop timed out
[ 1970.256752] AMD-Vi: Completion-Wait loop timed out
[ 1970.393535] AMD-Vi: Completion-Wait loop timed out
[ 1970.529685] AMD-Vi: Completion-Wait loop timed out
[ 1970.659821] AMD-Vi: Completion-Wait loop timed out
[ 1970.795963] AMD-Vi: Completion-Wait loop timed out
[ 1970.849443] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=09:00.0 address=0x42ed8a9a0]

Offline

#3 2020-04-13 15:27:22

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,096

Re: [Solved] Passthrough card graphic vega8

Full dmesg and/or journal please .

output of the script mentioned at https://wiki.archlinux.org/index.php/PC … _are_valid

Are both of your cards discrete videocards ?
What is brand, model and firmware version in use on your system / motherboard ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#4 2020-04-19 08:37:03

lolop
Member
Registered: 2015-02-19
Posts: 37

Re: [Solved] Passthrough card graphic vega8

the problem came from using the IGPU vega 8 which is integrated into the processor.
I did the passthrought that the pci graphics card that I had in addition without problem.

Offline

#5 2020-04-19 10:56:04

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,096

Re: [Solved] Passthrough card graphic vega8

Yup, passing through an iGPU is technically possible but depends on processor , motherboard and chipset manufacturers to have things setup correctly to achieve it.
Usually atleast one of them (often all three) overlook something that is essential to make passing through an iGPU work.

Please prepend [Solved] to the thread title (edit first post) .


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

Board footer

Powered by FluxBB