[RESOLVED] - "The guest has not initialized the display (yet)" when adding a PCIe GPU (2023)

2 drugged

New member
February 6, 2020
24
1
3
31
  • April 24, 2020
  • #1

I am trying to pass an AMD RX580 GPU to a VM, which boots fine without the GPU. When the GPU is added as a "general purpose" PCIe device, I only get thatThe guest has not (yet) initialized the screenconsole message.

CPU: AMD Ryzen 3950X, motherboard: Gigabyte Aorus Ultra, virtualization related things (virtualization, IOMMU, ARI, ACS) are enabled in BIOS.

My virtual machine setup is as follows:

Code:

agente: 1balloon: 8192bios: ovmfbootdisk: scsi0cores: 12cpu: hostefidisk0: VMstorage:vm-102-disk-1,size=1Mhostpci0: 0a:00,pcie=1ide2: local:iso/ubuntu-20.04-desktop-amd64.iso, media=cdrommachine: q35memory: 60000name: Ubuntunet0: virtio=B2:5E:C6:CA:A0:A5,bridge=vmbr0,firewall=1numa: 1ostype: l26scsi0: VMstorage:vm-102-disk-0,cache=writeback, descartar=activado,tamaño=32G,ssd=1scsihw: virtio-scsi-pcishares: 5000smbios1: uuid=bd85f4fe-370e-4299-9ce2-a39f2f997fe9sockets: 1vmgenid: fdfa3441-a8f0-48f5-8063-2d633183ffa4

The syslog is as follows (only boots this virtual machine):

Code:

Apr 24 4:18:00 pvehost systemd[1]: Starting Proxmox VE Replication Runner...24. Apr 4:18:00 pvehost systemd[1]: pvesr.service: Success. Apr 24 16:18:00 pvehost systemd[1]: Proxmox VE replication corridor has started. Apr 24 16:18:27 pvehost pvedaemon[5286]:start VM 102: UPID:pvehost:000014A6:00012328:5EA2F533:qmstart:102:root@pam: Apr 24 16:18:27 pvehost pvedaemon[1520]: < root @pam> Start task UPID:pvehost:000014A6:00012328:5EA2F533:qmstart:102:root@pam:Apr 24 16:18:27 pvehost kernel: pcieport 0000:00:03.1: AER: Uncorrected (non-fatal) error ) Received: 0000:00:03.1 Apr 24 16:18:27 pvehost kernel: pcieport 0000:00:03.1: AER: PCIe bus error: severity = uncorrected (non-fatal), type = transaction level, (ID from requestor) 24. Apr 16 : 18:27 pvehost kernel: pcieport 0000:00:03.1: AER: device [1022:1483] error status/mask=00100000/04400000 Apr 24 16:18:27 pvehost kernel: pcieport 0000:00:03.1: AER : [ 20 ] UnsupReq (first) Apr 24 16:18:27 kernel pvehost: pcieport 0000:00:03.1: AER: TLP header: 34000000 0a000010 00000000 80008000 Apr 24 16:18:27 kernel pvehost: pcieport 0030.1:0 recovery successful apr 24 16:18:27 pvehost systemd[1]: started 102.scope.Apr 24 16:18:27 pvehost systemd- udevd [5290]: Using default interface naming scheme "v240". Apr 24 16:18:27 pvehost systemd-udevd [5290]: link_config: auto-negotiation is not configured or enabled, speed and duplex cannot be written. Apr 24 16:18:27 pvehost systemd-udevd[5290]: Cannot generate permanent MAC address for tap102i0: No such file or directory Apr 24 16:18:27 pvehost kernel: Device tap102i0 is in mode promiscuous Mode entered systemd-udevd[ 5290 ]: link_config: auto-negotiation is on or off, speed and duplex not writable. 18:27 pvehost systemd-udevd[5289]: link_config: auto-negotiation is not configured or enabled, speed and duplex cannot be written. Apr 24 16:18:27 pvehost syste md-udevd [5296]: link_config: auto-negotiation is disabled or enabled, speed and duplex cannot be written. Apr 24 16:18:27 pvehost systemd-udevd[5289]: Using default interface naming scheme "v240". Apr 24 16:18:27 pvehost systemd-udevd[5296]: Using default interface naming scheme "v240". Apr 24 16:18:27 pvehost systemd-udevd[5296]: Cannot generate permanent MAC address for fwln102i0: No such file or directory Apr 24 16:18:27 pvehost systemd-udevd[5289]: MAC permanent Unable to generate an address for fwpr102p0 : No such file or directory Apr 24 16:18:27 pvehost kernel: fwbr102i0: port 1 (fwln102i0) in blocked state Apr 24 16:18:27 pvehost kernel: fwbr102i0: port 1 (fwln102i0) in disabled state Apr 24 16:18:27 pvehost kernel: fwln102i0 device entered promiscuous mode Apr 24 16:18:27 18:27 pvehost kernel: vmbr0: port 2 (fwpr102p0) entered promiscuous mode crash state on Apr 24 16:18:27 pvehost kernel: vmbr0: port 2 ( fwpr102p0) entered disabled state on Apr 24 at 16:18:27 pvehost kernel: device fwpr102p0 entered promiscuous mode on Apr 24 apr 16:18:apr 27 pvehost kernel: vmbr0: port 2 (fwpr102p0) entered blocking state on april 24 at 16:18:27 pvehost kernel: vmbr0: port 2 (fwpr102p0) entered forwarding state ng state on Apr 24 16:18:27 pvehost kernel: fwbr102i0: port 2 (tap102i0) entered blocking state 24 apr 16:18:27 pvehost kernel: fwbr102i0: port 2 (tap102i0) entered disabled state apr 24 16:18:27 pvehost kernel: fwbr102i0: port 2 (tap102i0) entered blocked state apr 24 16: 18:27 pvehost kernel: fwbr102i0 : port 2 (tap102i0) entered forwarding state on Apr 24 16:18:33 pvehost kernel: vfio-pci 0000:0a:00.0: vfio_ecap_init: hidden ecap 0x19@0x270 Apr 24 '16 :18:33 pvehost kernel: vfio-pci 0000:0a:00.0: vfio_ecap_init: hidden ecap 0x1b@ 0x2d0Apr 24 16:18:33 pvehost kernel: vfio-pci 0000:0a:00.0: vfio_ecap_init: hidden ecap 0x1e@0x370 16:18 pvehost kernel: pcieport 0000.1: AER.03: unfixed (non-fatal) error received: 0000:00:03.1Apr 24 16:18:34 kernel pvehost: pcieport 0000:00:03.1: AER: slash error Action from PCIe: severity = unresolved (non-fatal), type = transaction layer, (question id) Apr 24 4:18:34 pvehost kernel: pcieport 0000:00:03.1: aer: device [1022:1483] error status/mask =00100000/04400000 Apr 24 16:18:34 pvehost kernel: pcieport 0000:00:03.1: AER: [ 20 ] UnsupReq (First) Apr 24 16:18:34 pvehost kernel: pcieport 0000:00:03.1 : AER : TLP Header: 34000000 0a000010 00000000 80008000Apr 24 16:18:34 phost kernel pcieport 0000:00:03 restore device. successful Apr 24 16:18:34 pvehost pvedaemon[1520]: <root@pam> end task UPID:pvehost4:00.0 :00012328:5EA2F533:qmstart:102:root@pam: OK Apr 24 16:19:00 pvehost systemd[1 ]: Starting Proxmox VE replication runner... Apr 24 16:19:00 pvehost systemd[1]: pvesr.service: Success. Apr 24 16:19:00 pvehost systemd[1 ]: Starts the Proxmox VE replication corridor. Apr 24 4:20:00 pvehost systemd[1]: Starting Proxmox VE replication running... Apr 24 4:20:00 pvehost systemd[1]: pvesr.service: Success. Apr 24 16:20:00 pvehost systemd[1]: Proxmox VE replication corridor has started. systemd[1]: Starting Proxmox VE replication corridor... Apr 24 4:21:00 pvehost systemd[1]: pvesr.service: Success. Apr 24 16:21:05 pvehost systemd[1]: Starting to clean up temporary directories... Apr 24 4:21:05 pvehost systemd[1]: systemd-tmpfiles-clean.service: success.24 Apr 16 : 21:05 pvehost systemd[1]: Started cleaning up temporary directories. Apr 24 4:21:37 pvehost pvedaemon[1520]: <root@pam> authentication successful for user 'root@pam' Apr 24 4:22:00 pvehost systemd[1]: starting Proxmox VE replication corridor .. Apr 24 4:22:00 pvehost systemd[1]: pvesr.service: Successful. Apr 24 4:22:00 pvehost systemd[1]: Proxmox VE replication runner started. Apr 24 4:23:00 pvehost systemd[1]: Starting Proxmox VE Replication Runner...24. Apr 4:23:00 pvehost systemd[1]: pvesr.service: Success. Apr 24 4:23:00 pvehost systemd[1]: Proxmox VE replication runner started. :vncproxy:102:root@pam:April 24 16:23:02 pvehost pvedaemon[1520]: <root@pam> start task UPID:pvehost:000017CE:00018E7A:5EA2F646:vncproxy:102:root@pam:24 Apr 16 :23:05 pvehost pvedaemon[1520]: <root@pam> End task UPID:pvehost:000017CE:00018E7A:5EA2F646:vncproxy:102:root@pam: OKServer View

Proxmox is up to date and I already have kernel 5.4 installed.

Code:

proxmox-ve: 6.1-2 (Kernel en Ausführung: 5.4.27-1-pve)pve-manager: 6.1-8 (Versión en Ausführung: 6.1-8/806edfe1)pve-kernel-5.4: 6.1-8pve-kernel- Helfer: 6.1-8pve-kernel-5.3: 6.1-6pve-kernel-5.4.27-1-pve: 5.4.27-1pve-kernel-5.3.18-3-pve: 5.3.18-3pve-kernel-5.3. 18-2-pve: 5.3.18-2ceph-fuse: 12.2.11+dfsg1-2.1+b1corosync: 3.0.3-pve1criu: 3.11-3glusterfs-client: 5.5-3ifupdown: 0.8.35+pve1ksm-control-daemon: 1.3-1libjs-extjs: 6.0.1-10libknet1: 1.15-pve1libpve-access-control: 6.0-6libpve-apiclient-perl: 3.0-3libpve-common-perl: 6.0-17libpve-guest-common-perl: 3.0-5libpve- servidor-http-perl: 3.0-5libpve-storage-perl: 6.1-5libqb0: 1.0.5-1libspice-server1: 0.14.2-4~pve6+1lvm2: 2.03.02-pve4lxc-pve: 3.2.1-1lxcfs: 4.0. 1-pve1novnc-pve: 1.1.0-1proxmox-mini-journalreader: 1.1-1proxmox-widget-toolkit: 2.1-3pve-cluster: 6.1-4pve-container: 3.0-23pve-docs: 6.1-6pve-edk2-firmware: 2.20200229-1pve-Cortafuegos: 4.0-10pve-Firmware: 3.0-7pve-ha-Manager: 3.0-9pve-i18n: 2.0-4pve-qemu-kvm: 4.1.1-4pve-xtermjs: 4.3.0-1qemu-Servidor: 6.1-7smartmontools: 7.1-pve2spiceterm: 3.1-1vncterm: 1.6-1zfsutils-linux: 0.8.3-pve1

In GRUB I have the following line:GRUB_CMDLINE_LINUX_DEFAULT="net.ifnames=0 biosdevname=0 ruhig amd_iommu=on iommu=pt"

I get the same "guest not..." message with a virtual machine running Arch Linux and a very similar configuration.

Is there a solution to this problem to successfully bypass a GPU in this case? What do I have to adjust?

Thanks in advance!

2 drugged

New member
February 6, 2020
24
1
3
31
  • April 24, 2020
  • #2

I added the GPU ROM without any change.

2 drugged

New member
February 6, 2020
24
1
3
31
  • April 25, 2020
  • #3

In the host BIOS, I disabled ARI, ACS, and AER. Now I can move the AMD GPU to the Ubuntu 20.04 virtual machine. At first I didn't get any graphical output from the virtual machine. But the GPU was listed inlspci🇧🇷 I had to reboot the host. Now I get the graphics output from the old GPU.
But now I can't login to Ubuntu. I enter my password and press enter. Then the screen goes black and I am back to the login screen.

Edit: When I select "Ubuntu on Wayland", the login is successful.

edit2: every time I shut down the VM, I also have to reboot the host to get the passthrough to work again.

edit3:qm set ID -args '-machine type=q35,kernel_irqchip=on'Sometimes it allows me to successfully reboot the VM from within the VM, but never from the host.

Last edition:

2 drugged

New member
February 6, 2020
24
1
3
31
  • April 25, 2020
  • #4

A few issues remain (you can't shutdown the VM and restart it later via the proxmox GUI, but rebooting inside the VM works), and it seems to work looping through my RX580.

I used the following instructions:[1],[2],[3],[4]

I also had to:

  • Disable AER (and therefore also ACS) in the BIOS
  • GRUB_CMDLINE_LINUX_DEFAULT="net.ifnames=0 biosdevname=0 ruhig amd_iommu=on iommu=pt"
    • whichvideo=efifb:offIt works too, but Ubuntu takes about 10 seconds to show the icons in the "favorite apps bar" on the left(also happens withvideo=efifb:off)
  • blacklistamdgpuDrivers (not Radeon as mentioned in the guides above)

Code:

agente: 1args: -machine type=q35audio0: dispositivo=ich9-intel-hda,driver=spiceballoon: 8192bios: ovmfbootdisk: scsi0cores: 12cpu: hostefidisk0: VMstorage:vm-102-disk-1,size=1Mhostpci0: 0a:00, pcie=1máquina: q35memoria: 60000nombre: Ubuntunet0: virtio=B2:5E:C6:CA:A0:A5,bridge=vmbr0,firewall=1numa: 1ostype: l26scsi0: VMstorage:vm-102-disk-0,cache=writeback, descartar=activado,tamaño=32G,ssd=1scsihw: virtio-scsi-pcishares: 5000smbios1: uuid=bd85f4fe-370e-4299-9ce2-a39f2f997fe9sockets: 1usb0: host=046d:c52b,usb3=1usb1: host=1af3:0001, usb3=1usb2: anfitrión=04d9:0169,usb3=1usb3: anfitrión=046d:0819,usb3=1usb4: anfitrión=048d:8297,usb3=1vga: noevmgenid: fdfa3441-a8f0-48f5-8063-2d633183ffa4

Maybe it will help someone in the future who has a similar problem...[RESOLVED] - "The guest has not initialized the display (yet)" when adding a PCIe GPU (1)

Last edition:

You must login or register to reply here.

References

Top Articles
Latest Posts
Article information

Author: Duane Harber

Last Updated: 28/04/2023

Views: 5967

Rating: 4 / 5 (51 voted)

Reviews: 82% of readers found this page helpful

Author information

Name: Duane Harber

Birthday: 1999-10-17

Address: Apt. 404 9899 Magnolia Roads, Port Royceville, ID 78186

Phone: +186911129794335

Job: Human Hospitality Planner

Hobby: Listening to music, Orienteering, Knapping, Dance, Mountain biking, Fishing, Pottery

Introduction: My name is Duane Harber, I am a modern, clever, handsome, fair, agreeable, inexpensive, beautiful person who loves writing and wants to share my knowledge and understanding with you.