Black screen after starting qemu

Support Virtualization
, ,
1

Hi,
Being new to Linux, I followed SomeOrdinaryGamer’s manjaro installation guide based on the Arch wiki’s PCIE Passthrough via VFIO and was able to follow up to point where he passed in his gpu and started qemu. I don’t have two gpu but I have a iGPU and dGPU, but when I started qemu, my monitor went black and I was forced to restart my pc. Is this because my monitor isnt using the iGPU? If so, how do I make it use it?

inxi -Fazy

System:
  Kernel: 5.15.84-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
    root=UUID=6ed1d02d-8a17-4577-b0b5-d1f424d462f6 rw quiet
    vfio.pci.ids=1002:73df resume=UUID=86bd610e-ef0b-4d79-9b61-a8294c4f55eb
    udev.log_priority=3
  Desktop: KDE Plasma v: 5.26.4 tk: Qt v: 5.15.7 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: MAG X570S TOMAHAWK MAX WIFI (MS-7D54)
    v: 1.0 serial: <superuser required> UEFI: American Megatrends LLC. v: 1.10
    date: 12/17/2021
CPU:
  Info: model: AMD Ryzen 5 5600G with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22
    process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
    microcode: 0xA50000C
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 16 MiB
    desc: 1x16 MiB
  Speed (MHz): avg: 2583 high: 3883 min/max: 1400/4464 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1478 2: 2486
    3: 2395 4: 2395 5: 2395 6: 2394 7: 3082 8: 3112 9: 2469 10: 3883 11: 2515
    12: 2394 bogomips: 93466
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl and seccomp
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M]
    vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
    process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16
    ports: active: DP-1 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 12:00.0
    chip-ID: 1002:73df class-ID: 0300
  Device-2: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
    driver: amdgpu v: kernel arch: GCN-5.1 code: Vega-2 process: TSMC n7 (7nm)
    built: 2018-21 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s ports: active: HDMI-A-2 empty: DP-4,HDMI-A-3 bus-ID: 30:00.0
    chip-ID: 1002:1638 class-ID: 0300 temp: 29.0 C
  Display: x11 server: X.Org v: 21.1.6 compositor: kwin_x11 driver: X:
    loaded: amdgpu unloaded: modesetting,radeon alternate: fbdev,vesa
    dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 4480x1440 s-dpi: 96 s-size: 1185x381mm (46.65x15.00")
    s-diag: 1245mm (49.01")
  Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,left
    model: LG (GoldStar) ULTRAGEAR serial: <filter> built: 2022 res: 2560x1440
    dpi: 93 gamma: 1.2 size: 697x392mm (27.44x15.43") diag: 800mm (31.5")
    ratio: 16:9 modes: max: 2560x1440 min: 640x480
  Monitor-2: HDMI-A-2 mapped: HDMI-A-1-1 pos: right model: Samsung
    serial: <filter> built: 2009 res: 1920x1080 hz: 60 dpi: 3048 gamma: 1.2
    size: 16x9mm (0.63x0.35") diag: 5mm (0.2") ratio: 4:3 modes: max: 1920x1080
    min: 640x480
  API: OpenGL v: 4.6 Mesa 22.3.1 renderer: AMD Radeon RX 6700 XT (navi22
    LLVM 14.0.6 DRM 3.42 5.15.84-1-MANJARO) direct render: Yes
Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel
    bus-ID: 3-5:2 pcie: gen: 4 chip-ID: 0db0:a073 speed: 16 GT/s class-ID: 0300
    lanes: 16 bus-ID: 12:00.1 chip-ID: 1002:ab28 class-ID: 0403
  Device-2: AMD Renoir Radeon High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 30:00.1 chip-ID: 1002:1637
    class-ID: 0403
  Device-3: AMD Family 17h/19h HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 30:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  Device-4: Micro Star USB Audio type: USB
    driver: hid-generic,snd-usb-audio,usbhid
  Sound API: ALSA v: k5.15.84-1-MANJARO running: yes
  Sound Server-1: JACK v: 1.9.21 running: no
  Sound Server-2: PulseAudio v: 16.1 running: yes
  Sound Server-3: PipeWire v: 0.3.63 running: yes
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 26:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp38s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 28:00.0 chip-ID: 8086:2725
    class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-4:2
    chip-ID: 8087:0032 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 931.51 GiB used: 329.43 GiB (35.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: 5B2QGXA7 temp: 34.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 922.42 GiB size: 906.86 GiB (98.31%)
    used: 253.21 GiB (27.9%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 312 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
  System Temperatures: cpu: 32.9 C mobo: N/A
  Fan Speeds (RPM): N/A
  GPU: device: amdgpu temp: 37.0 C mem: 34.0 C fan: 0 watts: 6.00
    device: amdgpu temp: 29.0 C
Info:
  Processes: 327 Uptime: 20m wakeups: 0 Memory: 27.3 GiB used: 2.53 GiB (9.3%)
  Init: systemd v: 252 default: graphical tool: systemctl Compilers:
  gcc: 12.2.0 clang: 14.0.6 Packages: 1374 pm: pacman pkgs: 1360 libs: 357
  tools: pamac,yay pm: flatpak pkgs: 14 Shell: Zsh v: 5.9 default: Bash
  v: 5.1.16 running-in: konsole inxi: 3.3.24
2

Hello,

The GPU (either iGPU or dGPU0 you passthrough can’t be used by the host, so no monitor connected to it will have signal from host. From inxi provided you seem to have 2 monitors, each one connected to one of the GPU’s.

3

Thanks for the reply, I noticed that two monitors as well and once I disconnected my samsung soundbar it stopped mentioning the second monitor.

However, I tried running qemu again and got the same result. Should my monitor automatically switch to the iGPU or should it not switch at all since the dGPU should be isolated and be inaccessible?

4

Go slow to each pointer regarding it PCI passthrough via OVMF - ArchWiki
Not only will provide more context, but you can also check what you did or did not.

5

Resolved
My dGPU wasnt isolated correctly for some reason since system monitor still detected it and my monitor needed to be plugged in to the motherboard to use the iGPU.

6

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.