GPU passthrough - Guest won't boot, stay in uefi screen

J

joaoac

New Member
Oct 6, 2022
12
0
1
My system specs:
HP Elitedesk 705 G4 sff
Ryzen 2004G
8gb RAM DDR4 2666
512GB SSD NVME
GPU: R7 430 2G OEM
My idea is upgrade to a rx 6400, but i need confirm if its works.

Proxmox VE 7.2-11
VM: W11 pro.

I then created a new VM and carefully worked through all the steps here, here and here. Passthrough actually seems to be working because I can complete a Windows installation and even boot into the OS using HDMI out from the GPU, however as soon as I enable network connectivity and Windows update installs the AMD GPU driver the system locks up. Starting the guest after GPU drivers are installed may freeze the host and require a reset or the guest can't boot and stops at this (always shows the spinning "stars" but only sometimes shows the EFI boot messages).edited.jpg

Confim my configs:

Code: 
#  cat /etc/default/grub
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt video=vesafb:off,efifb:off"
GRUB_CMDLINE_LINUX=""
# Some other commented lines

Code: 
# dmesg | grep -e DMAR -e IOMMU
[    1.342720] pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
[    1.343421] pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40
[    1.344279] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank).
[    6.300524] AMD-Vi: AMD IOMMUv2 loaded and initialized

Code: 
# cat /etc/modules
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd

Code: 
# dmesg | grep 'remapping'
[    1.343427] AMD-Vi: Interrupt remapping enabled

Code: 
# cat /etc/modprobe.d/iommu_unsafe_interrupts.conf
options vfio_iommu_type1 allow_unsafe_interrupts=1

Code: 
# find /sys/kernel/iommu_groups/ -type l
/sys/kernel/iommu_groups/7/devices/0000:00:18.3
/sys/kernel/iommu_groups/7/devices/0000:00:18.1
/sys/kernel/iommu_groups/7/devices/0000:00:18.6
/sys/kernel/iommu_groups/7/devices/0000:00:18.4
/sys/kernel/iommu_groups/7/devices/0000:00:18.2
/sys/kernel/iommu_groups/7/devices/0000:00:18.0
/sys/kernel/iommu_groups/7/devices/0000:00:18.7
/sys/kernel/iommu_groups/7/devices/0000:00:18.5
/sys/kernel/iommu_groups/5/devices/0000:0c:00.0
/sys/kernel/iommu_groups/5/devices/0000:00:08.0
/sys/kernel/iommu_groups/5/devices/0000:0c:00.3
/sys/kernel/iommu_groups/5/devices/0000:00:08.1
/sys/kernel/iommu_groups/5/devices/0000:0c:00.2
/sys/kernel/iommu_groups/3/devices/0000:00:04.0
/sys/kernel/iommu_groups/1/devices/0000:00:02.0
/sys/kernel/iommu_groups/6/devices/0000:00:14.3
/sys/kernel/iommu_groups/6/devices/0000:00:14.0
/sys/kernel/iommu_groups/4/devices/0000:0b:00.2
/sys/kernel/iommu_groups/4/devices/0000:0b:00.0
/sys/kernel/iommu_groups/4/devices/0000:00:07.0
/sys/kernel/iommu_groups/4/devices/0000:0b:00.3
/sys/kernel/iommu_groups/4/devices/0000:00:07.1
/sys/kernel/iommu_groups/2/devices/0000:00:03.1
/sys/kernel/iommu_groups/2/devices/0000:0a:00.0
/sys/kernel/iommu_groups/2/devices/0000:00:03.0
/sys/kernel/iommu_groups/2/devices/0000:0a:00.1
/sys/kernel/iommu_groups/0/devices/0000:03:00.0
/sys/kernel/iommu_groups/0/devices/0000:02:00.2
/sys/kernel/iommu_groups/0/devices/0000:00:01.2
/sys/kernel/iommu_groups/0/devices/0000:02:00.0
/sys/kernel/iommu_groups/0/devices/0000:00:01.0
/sys/kernel/iommu_groups/0/devices/0000:03:06.0
/sys/kernel/iommu_groups/0/devices/0000:01:00.0
/sys/kernel/iommu_groups/0/devices/0000:06:00.4
/sys/kernel/iommu_groups/0/devices/0000:06:00.2
/sys/kernel/iommu_groups/0/devices/0000:03:05.0
/sys/kernel/iommu_groups/0/devices/0000:06:00.0
/sys/kernel/iommu_groups/0/devices/0000:02:00.1
/sys/kernel/iommu_groups/0/devices/0000:03:01.0
/sys/kernel/iommu_groups/0/devices/0000:03:04.0
/sys/kernel/iommu_groups/0/devices/0000:03:07.0
/sys/kernel/iommu_groups/0/devices/0000:06:00.3
/sys/kernel/iommu_groups/0/devices/0000:00:01.4
/sys/kernel/iommu_groups/0/devices/0000:06:00.1

Code: 
# cat /etc/modprobe.d/vfio.conf
options vfio-pci ids=1002:6611,1002:aab0 disable_vga=1

Code: 
# cat /etc/modprobe.d/blacklist.conf
blacklist radeon
blacklist nouveau
blacklist nvidia

Code: 
# cat /etc/modprobe.d/vfio.conf
options vfio-pci ids=1002:6611,1002:aab0 disable_vga=1

AND, the end:

Code: 
# cat /etc/pve/qemu-server/100.conf
#machine%3A pc-q35-7.0
#machine%3A q35
acpi: 0
agent: 1
args: -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=NV43FIX,kvm=off'
balloon: 1024
bios: ovmf
boot: order=scsi0;ide2;net0;ide0
cores: 16
cpu: host,hidden=1,flags=+pcid
efidisk0: local-lvm:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
hostpci0: 0000:0a:00,pcie=1,x-vga=1
ide0: local:iso/virtio.iso,media=cdrom,size=519030K
ide2: local:iso/windows11.iso,media=cdrom,size=5155160K
kvm: 1
machine: pc-q35-7.0
memory: 6096
meta: creation-qemu=7.0.0,ctime=1664816339
name: Win11
net0: e1000=56:DE:A4:5C:15:D3,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
scsi0: local-lvm:vm-100-disk-1,size=132G
scsihw: virtio-scsi-pci
smbios1: uuid=71a27d78-c631-4570-8540-dfe9376ed4b2
sockets: 1
tpmstate0: local-lvm:vm-100-disk-2,size=4M,version=v2.0
vmgenid: f6a23745-fa77-4712-a341-5381ab04f43f

I tried several different ways, I tried reinstalling the guest, I also tried changing some kernel and guest boot flags, none of them worked. I really want help
 
joaoac said:
GPU: R7 430 2G OEM
My idea is upgrade to a rx 6400, but i need confirm if its works.
Click to expand...
joaoac said:
I then created a new VM and carefully worked through all the steps here, here and here. Passthrough actually seems to be working because I can complete a Windows installation and even boot into the OS using HDMI out from the GPU, however as soon as I enable network connectivity and Windows update installs the AMD GPU driver the system locks up. Starting the guest after GPU drivers are installed may freeze the host and require a reset or the guest can't boot and stops at this (always shows the spinning "stars" but only sometimes shows
Click to expand...
Looks like PCIe passthrough works on your system. as you have output to the physical display during Windows installation.
It looks to me to be an AMD Windows driver issue, about which I have no experience, sorry. You could try an Ubuntu VM or Live installer, which has all drivers included.
Please note that if you could fix this issues with your R7 430 then that gives no guarantees that your RX6400 will work.
Maybe your time would be better spend searching for success reports about RX6400 and making sure you buy one that works with passthrough.
 
Maybe I missed some important data above, I didn't perform the entire installation with the options x-vga=1 and pcie=1, when I enable them the same problem shown in the image above happens. all screen images were taken using the display port cable connected directly to the video card on the monitor, even because my ryzen doesn't have integrated video support.

I try to install Ubuntu 22.04 using the same settings, pcie=1, x-vga=1, even works in grub, shows install options, secure graphics, etc.
IMG_20221006_075111.jpg

However, when trying to start in any option the boot apparently crashes. Clicking E and disabling silent mode gives the following error: EFI stub: UEFI Secure Boot is enable.
Forcing boot using the flag: dis_ucode_ldr the display generates artifacts.
IMG_20221006_075003.jpg
After that, I tried to start with the first option and leave it for a long time, again errors were presented and generated video artifacts, and again it stopped there.

Sem título.jpg
I really don't understand what could be happening, however, I believe it's not a problem with the video card, as I was already using windows natively without problems, and proxmox also boots without problems.
 
Can you try without secure boot?
 
How i disable secure boot in my vms?

In my proxmox ve installation, secure boot it's already disabled and this feature is disabled in bios.
 
On boot press `ESC` to enter the UEFI menu. From there you should be able to disable it.
 
Disabling secure boot didn't work, but I noticed a strange thing.
When i first boot pve and verify if iommu is enable, my output is:
Code: 
# dmesg | grep -e DMAR -e IOMMU
[    1.342720] pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
[    1.343421] pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40
[    1.344279] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank).
[    6.300524] AMD-Vi: AMD IOMMUv2 loaded and initialized
But, after booting my w11 guest and verify again iommu is enable, output is empty:
Code: 
# dmesg | grep -e DMAR -e IOMMU
I dont understand, but does this mean iommu is being disabled?
 
joaoac said:
Disabling secure boot didn't work, but I noticed a strange thing.
When i first boot pve and verify if iommu is enable, my output is:
Code: 
# dmesg | grep -e DMAR -e IOMMU
[    1.342720] pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
[    1.343421] pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40
[    1.344279] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank).
[    6.300524] AMD-Vi: AMD IOMMUv2 loaded and initialized
Click to expand...
You are using a test for Intel IOMMU; amd_iommu is enabled by default (if not disabled by BIOS). Check you IOMMU groups as the definite answer if IOMMU is on (there are more than one group).
joaoac said:
But, after booting my w11 guest and verify again iommu is enable, output is empty:
Code: 
# dmesg | grep -e DMAR -e IOMMU
I dont understand, but does this mean iommu is being disabled?
Click to expand...
No, this probably means that you have so many log lines that the previous results got lost. Probably your "w11" is causing a lot of repeated messages about what is going wrong, but you are not seeing them because they don't contain those words.
 
joaoac said:
How y check if my IOMMU grups are defined and enabled?
Click to expand...

E.g. with:
Bash: 
for d in /sys/kernel/iommu_groups/*/devices/*; do n=${d#*/iommu_groups/*}; n=${n%%/*}; printf 'IOMMU group %s ' "$n"; lspci -nns "${d##*/}"; done
 
Code: 
# find /sys/kernel/iommu_groups/ -type l
/sys/kernel/iommu_groups/7/devices/0000:00:18.3
/sys/kernel/iommu_groups/7/devices/0000:00:18.1
/sys/kernel/iommu_groups/7/devices/0000:00:18.6
/sys/kernel/iommu_groups/7/devices/0000:00:18.4
/sys/kernel/iommu_groups/7/devices/0000:00:18.2
/sys/kernel/iommu_groups/7/devices/0000:00:18.0
/sys/kernel/iommu_groups/7/devices/0000:00:18.7
/sys/kernel/iommu_groups/7/devices/0000:00:18.5
/sys/kernel/iommu_groups/5/devices/0000:0c:00.0
/sys/kernel/iommu_groups/5/devices/0000:00:08.0
/sys/kernel/iommu_groups/5/devices/0000:0c:00.3
/sys/kernel/iommu_groups/5/devices/0000:00:08.1
/sys/kernel/iommu_groups/5/devices/0000:0c:00.2
/sys/kernel/iommu_groups/3/devices/0000:00:04.0
/sys/kernel/iommu_groups/1/devices/0000:00:02.0
/sys/kernel/iommu_groups/6/devices/0000:00:14.3
/sys/kernel/iommu_groups/6/devices/0000:00:14.0
/sys/kernel/iommu_groups/4/devices/0000:0b:00.2
/sys/kernel/iommu_groups/4/devices/0000:0b:00.0
/sys/kernel/iommu_groups/4/devices/0000:00:07.0
/sys/kernel/iommu_groups/4/devices/0000:0b:00.3
/sys/kernel/iommu_groups/4/devices/0000:00:07.1
/sys/kernel/iommu_groups/2/devices/0000:00:03.1
/sys/kernel/iommu_groups/2/devices/0000:0a:00.0
/sys/kernel/iommu_groups/2/devices/0000:00:03.0
/sys/kernel/iommu_groups/2/devices/0000:0a:00.1
/sys/kernel/iommu_groups/0/devices/0000:03:00.0
/sys/kernel/iommu_groups/0/devices/0000:02:00.2
/sys/kernel/iommu_groups/0/devices/0000:00:01.2
/sys/kernel/iommu_groups/0/devices/0000:02:00.0
/sys/kernel/iommu_groups/0/devices/0000:00:01.0
/sys/kernel/iommu_groups/0/devices/0000:03:06.0
/sys/kernel/iommu_groups/0/devices/0000:01:00.0
/sys/kernel/iommu_groups/0/devices/0000:06:00.4
/sys/kernel/iommu_groups/0/devices/0000:06:00.2
/sys/kernel/iommu_groups/0/devices/0000:03:05.0
/sys/kernel/iommu_groups/0/devices/0000:06:00.0
/sys/kernel/iommu_groups/0/devices/0000:02:00.1
/sys/kernel/iommu_groups/0/devices/0000:03:01.0
/sys/kernel/iommu_groups/0/devices/0000:03:04.0
/sys/kernel/iommu_groups/0/devices/0000:03:07.0
/sys/kernel/iommu_groups/0/devices/0000:06:00.3
/sys/kernel/iommu_groups/0/devices/0000:00:01.4
/sys/kernel/iommu_groups/0/devices/0000:06:00.1
that the same thing as doing that?
 
Neobin said:
E.g. with:
Bash: 
for d in /sys/kernel/iommu_groups/*/devices/*; do n=${d#*/iommu_groups/*}; n=${n%%/*}; printf 'IOMMU group %s ' "$n"; lspci -nns "${d##*/}"; done
Click to expand...
After researching in depth what you meant, I finally understood that for the pass to work it is necessary for the gpu to be in an isolated iommu group, I repeated the process and got this output:
Code: 
Group:  0   0000:00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
Group:  0   0000:00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453]   Driver: pcieport
Group:  0   0000:00:01.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453]   Driver: pcieport
Group:  0   0000:01:00.0 Non-Volatile memory controller [0108]: Silicon Motion, Inc. SM2263EN/SM2263XT SSD Controller [126f:2263] (rev 03)   Driver: nvme
Group:  0   0000:02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset USB 3.1 xHCI Controller [1022:43bb] (rev 02)   Driver: xhci_hcd
Group:  0   0000:02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset SATA Controller [1022:43b7] (rev 02)   Driver: ahci
Group:  0   0000:02:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43b2] (rev 02)   Driver: pcieport
Group:  0   0000:03:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02)   Driver: pcieport
Group:  0   0000:03:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02)   Driver: pcieport
Group:  0   0000:03:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02)   Driver: pcieport
Group:  0   0000:03:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02)   Driver: pcieport
Group:  0   0000:03:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02)   Driver: pcieport
Group:  0   0000:03:07.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02)   Driver: pcieport
Group:  0   0000:06:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0e)   Driver: r8169
Group:  0   0000:06:00.1 Serial controller [0700]: Realtek Semiconductor Co., Ltd. RTL8111xP UART #1 [10ec:816a] (rev 0e)   Driver: serial
Group:  0   0000:06:00.2 Serial controller [0700]: Realtek Semiconductor Co., Ltd. RTL8111xP UART #2 [10ec:816b] (rev 0e)   Driver: serial
Group:  0   0000:06:00.3 IPMI Interface [0c07]: Realtek Semiconductor Co., Ltd. RTL8111xP IPMI interface [10ec:816c] (rev 0e)
Group:  0   0000:06:00.4 USB controller [0c03]: Realtek Semiconductor Co., Ltd. RTL811x EHCI host controller [10ec:816d] (rev 0e)   Driver: ehci-pci
Group:  1   0000:00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
Group:  2   0000:00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
Group:  2   0000:00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453]   Driver: pcieport
Group:  2   0000:0a:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R5 430 OEM / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87)   Driver: vfio-pci
Group:  2   0000:0a:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series] [1002:aab0]   Driver: vfio-pci
Group:  3   0000:00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
Group:  4   0000:00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
Group:  4   0000:00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454]   Driver: pcieport
Group:  4   0000:0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function [1022:145a]
Group:  4   0000:0b:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor [1022:1456]   Driver: ccp
Group:  4   0000:0b:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller [1022:145f]   Driver: xhci_hcd
Group:  5   0000:00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
Group:  5   0000:00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454]   Driver: pcieport
Group:  5   0000:0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function [1022:1455]
Group:  5   0000:0c:00.2 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51)   Driver: ahci
Group:  5   0000:0c:00.3 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller [1022:1457]   Driver: snd_hda_intel
Group:  6   0000:00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 59)
Group:  6   0000:00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
Group:  7   0000:00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1460]
Group:  7   0000:00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1461]
Group:  7   0000:00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1462]
Group:  7   0000:00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1463]   Driver: k10temp
Group:  7   0000:00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1464]
Group:  7   0000:00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1465]
Group:  7   0000:00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1466]
Group:  7   0000:00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 [1022:1467]

Notably the gpu is in the same group as the chipset, so the pass-through won't work, is that right?
If this is the problem is there a solution?
 
GOOD NEWS: Finally works!!!!!!!
Im add all itens in iommu group 2 to /etc/modprobe.d/vfio.conf reboot and pass gpu i passed the gpu as i did before and boots hehe

Code: 
root@pve:~# lspci -n -s 00:03
00:03.0 0600: 1022:1452
00:03.1 0604: 1022:1453
root@pve:~# lspci -n -s 0a:00
0a:00.0 0300: 1002:6611 (rev 87)
0a:00.1 0403: 1002:aab0
root@pve:~# cat /etc/modprobe.d/vfio.conf
options vfio-pci ids=1002:6611,1002:aab0,1022:1452,1022:1453 disable_vga=1
 
BAD NEWS, Not working anymore!

it was working perfectly, I created a new machine with w11 and installed everything directly from the monitor connected to the video card, at the end of formatting and downloading all the drivers and windows updates, the entire proxmox crashed, I restarted using the power button and from there the passtrough it didn't work anymore.
 
Working again, thanks @leesteken !!!

I use this solution!

Ironically it seems that following the steps of the official tutorial is not always the best choice, I reverted all the configs made leaving only grub with the flag: GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=en video=vesafb:off"
I also left the modules enabled in /etc/modules.
I left unsafe interrupts enabled.
After that I updated the grub restarted the computer, the gpu worked as the main output of proxmox, displaying the shell on my monitor, I just accessed the web interface, I linked the gpu to w11 with all functions enabled (x-vga=1, pcie= 1), the moment I turned on the machine, the proxmox shell gave way to the windows vm bios screen and the boot went perfectly, I updated all the drivers, restarted a few times and everything is working perfectly.
 
@joaoac Would you please share all the detail, trying to get this running but most of the time proxmox just reboots :-D I can see the card on guest but that's it
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom