[SOLVED] Windows VM with a passed through GPU slows down whole host to near not responding when powered on

V

vaxis

New Member
Sep 24, 2026
5
0
1
Initial setup of the Win VM with the GPU pass through worked with no issues. The issue only started when I installed a m.2 to sata expansion card on my mITX motherboard THEN passed it through a virtualized TrueNAS.

I have already have separated my IOMMU groups and can also confirm that the new m.2 to sata adapter is on its own separate group. Currently host is up and has been up for a few weeks but I had to remove the passed through GPU to the Windows VM.

This is my first time posting and seeking help from here please let me know which logs i need to share to further help diagnose the issue
 
I’m not very familiar with this area, but I think the following information would help narrow down the cause:

- PVE version

- Hardware specifications

- Configuration of each affected VM:

Code: 
qm config <VMID>

- PCI device information:

Code: 
lspci -nnk

- IOMMU group information, if PCI passthrough is being used

- System journal from around the time the issue occurs

Please also provide information about CPU, memory, and storage I/O usage when the issue occurs.

Please post the complete command output as text in code blocks rather than as screenshots.
 
Thanks for suggesting these information, will be putting them below.

PVE Version and HW specs

Code: 
OS: Proxmox VE 9.2.2 x86_64
Host: B550i AORUS PRO AX
Uptime: 10 days, 3 hours
CPU: AMD Ryzen 5 5600G (12) @ 4.46 GHz
GPU1: AMD Radeon Vega Series / Radeon Vega [Integrated]
GPU2: NVIDIA GeForce GTX 1660 Ti [Dedicated]
Memory: 24.46GiB / 30.72 GiB
Disk: (/): 35.33 GiB / 93.93 GiB

PCIE Devices (lspci -nnk)
Code: 
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex [1022:1630]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex [1022:1630]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU [1022:1631]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU [1022:1631]
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1633]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1453]
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
00:02.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1453]
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:02.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1453]
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635]
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 51)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
        Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 0 [1022:166a]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 1 [1022:166b]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 2 [1022:166c]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 3 [1022:166d]
        Kernel driver in use: k10temp
        Kernel modules: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 4 [1022:166e]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 5 [1022:166f]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 6 [1022:1670]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 7 [1022:1671]
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1)
        Subsystem: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182]
        Kernel driver in use: vfio-pci
        Kernel modules: nvidiafb, nouveau, nova_core
01:00.1 Audio device [0403]: NVIDIA Corporation TU116 High Definition Audio Controller [10de:1aeb] (rev a1)
        Subsystem: NVIDIA Corporation Device [10de:2182]
        Kernel driver in use: vfio-pci
        Kernel modules: snd_hda_intel
01:00.2 USB controller [0c03]: NVIDIA Corporation TU116 USB 3.1 Host Controller [10de:1aec] (rev a1)
        Subsystem: NVIDIA Corporation Device [10de:2182]
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
01:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU116 USB Type-C UCSI Controller [10de:1aed] (rev a1)
        Subsystem: NVIDIA Corporation Device [10de:2182]
        Kernel driver in use: nvidia-gpu
        Kernel modules: i2c_nvidia_gpu
02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset USB 3.1 XHCI Controller [1022:43ee]
        Subsystem: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller [1b21:1142]
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset SATA Controller [1022:43eb]
        Subsystem: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:1062]
        Kernel driver in use: ahci
        Kernel modules: ahci
02:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset Switch Upstream Port [1022:43e9]
        Subsystem: ASMedia Technology Inc. Device [1b21:0201]
        Kernel driver in use: pcieport
        Kernel modules: shpchp
03:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset Switch Downstream Port [1022:43ea]
        Subsystem: ASMedia Technology Inc. Device [1b21:3308]
        Kernel driver in use: pcieport
        Kernel modules: shpchp
03:08.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset Switch Downstream Port [1022:43ea]
        Subsystem: ASMedia Technology Inc. Device [1b21:3308]
        Kernel driver in use: pcieport
        Kernel modules: shpchp
03:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset Switch Downstream Port [1022:43ea]
        Subsystem: ASMedia Technology Inc. Device [1b21:3308]
        Kernel driver in use: pcieport
        Kernel modules: shpchp
04:00.0 Non-Volatile memory controller [0108]: Kingston Technology Company, Inc. KC3000/FURY Renegade NVMe SSD [E18] [2646:5013] (rev 01)
        Subsystem: Kingston Technology Company, Inc. KC3000/FURY Renegade NVMe SSD [E18] [2646:5013]
        Kernel driver in use: nvme
        Kernel modules: nvme
05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:e000]
        Kernel driver in use: r8169
        Kernel modules: r8169
06:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8852CE PCIe 802.11ax Wireless Network Controller [10ec:c852] (rev 01)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8852CE PCIe 802.11ax Wireless Network Controller [10ec:c852]
        Kernel driver in use: rtw89_8852ce
        Kernel modules: rtw89_8852ce
07:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1166 Serial ATA Controller [1b21:1166] (rev 02)
        Subsystem: ZyDAS Technology Corp. Device [2116:2116]
        Kernel driver in use: vfio-pci
        Kernel modules: ahci
08:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c9)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu
08:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller [1002:1637]
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller [1002:1637]
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
08:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df]
        Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df]
        Kernel driver in use: ccp
        Kernel modules: ccp
08:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639]
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5007]
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
08:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639]
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5007]
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
08:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h/19h/1ah HD Audio Controller [1022:15e3]
        DeviceName: Realtek ALC1220
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:a0c3]
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel

IOMMU Groups
Code: 
IOMMU Group 0:
        00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
IOMMU Group 1:
        00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1633]
IOMMU Group 2:
        00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
IOMMU Group 3:
        00:02.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634]
IOMMU Group 4:
        00:02.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634]
IOMMU Group 5:
        00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
IOMMU Group 6:
        00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635]
IOMMU Group 7:
        00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 51)
        00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
IOMMU Group 8:
        00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 0 [1022:166a]
        00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 1 [1022:166b]
        00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 2 [1022:166c]
        00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 3 [1022:166d]
        00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 4 [1022:166e]
        00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 5 [1022:166f]
        00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 6 [1022:1670]
        00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 7 [1022:1671]
IOMMU Group 9:
        01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1)
IOMMU Group 10:
        01:00.1 Audio device [0403]: NVIDIA Corporation TU116 High Definition Audio Controller [10de:1aeb] (rev a1)
IOMMU Group 11:
        01:00.2 USB controller [0c03]: NVIDIA Corporation TU116 USB 3.1 Host Controller [10de:1aec] (rev a1)
IOMMU Group 12:
        01:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU116 USB Type-C UCSI Controller [10de:1aed] (rev a1)
IOMMU Group 13:
        02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset USB 3.1 XHCI Controller [1022:43ee]
IOMMU Group 14:
        02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset SATA Controller [1022:43eb]
IOMMU Group 15:
        02:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset Switch Upstream Port [1022:43e9]
IOMMU Group 16:
        03:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset Switch Downstream Port [1022:43ea]
IOMMU Group 17:
        03:08.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset Switch Downstream Port [1022:43ea]
IOMMU Group 18:
        03:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset Switch Downstream Port [1022:43ea]
IOMMU Group 19:
        04:00.0 Non-Volatile memory controller [0108]: Kingston Technology Company, Inc. KC3000/FURY Renegade NVMe SSD [E18] [2646:5013] (rev 01)
IOMMU Group 20:
        05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
IOMMU Group 21:
        06:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8852CE PCIe 802.11ax Wireless Network Controller [10ec:c852] (rev 01)
IOMMU Group 22:
        07:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1166 Serial ATA Controller [1b21:1166] (rev 02)
IOMMU Group 23:
        08:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c9)
IOMMU Group 24:
        08:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller [1002:1637]
IOMMU Group 25:
        08:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df]
IOMMU Group 26:
        08:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639]
IOMMU Group 27:
        08:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639]
IOMMU Group 28:
        08:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h/19h/1ah HD Audio Controller [1022:15e3]

Affected VM Config (Windows VM) -- **Please note, as I have mentioned I removed the pass-through so I can use the VM and the Host**
Code: 
args: -cpu host,-hypervisor,kvm=off, -smbios type=0,vendor="American Megatrends International",version=FE,date="03/22/2024"
balloon: 0
bios: ovmf
boot: order=sata0;net0
cores: 12
cpu: host,hidden=1
efidisk0: MSWin:vm-100-disk-0,efitype=4m,ms-cert=2023k,pre-enrolled-keys=1,size=4M
machine: pc-q35-11.0
memory: 8096
meta: creation-qemu=11.0.0,ctime=1788419098
name: WINDOWS
net0: e1000=bc:24:11:45:18:e0,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
sata0: MSWin:vm-100-disk-1,cache=writeback,size=550G
scsihw: lsi
smbios1: uuid=03ff0210-04e0-056d-4806-090700080009,manufacturer=R2lnYWJ5dGUgVGVjaG5vbG9neSBDby4sIEx0ZC4=,product=QjU1MEkgQU9SVVMgUFJPIEFY,family=QjU1MCBNQg==,base64=1
sockets: 1
tpmstate0: MSWin:vm-100-disk-2,size=4M,version=v2.0
vmgenid: 04976d90-0cb1-4afa-9797-0b03bcf79288

TrueNAS VM Config
Code: 
boot: order=scsi0;net0
cores: 2
cpu: x86-64-v2-AES
hostpci0: 0000:07:00
memory: 8192
meta: creation-qemu=11.0.0,ctime=1788518166
name: TrueNAS
net0: virtio=BC:24:11:A1:03:25,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: VMs:vm-107-disk-0,iothread=1,size=16G
scsihw: virtio-scsi-single
smbios1: uuid=7aa5b175-219b-427a-81b9-28357db345a0
sockets: 1
vmgenid: 44db38b3-5adc-4cff-b03c-9a659070b5e8

As for the other logs, I don't have any current ones as I haven't tried it in maybe 2 weeks.
 
Last edited:
Your CPU only has 6 cores with 2 threads each and you are giving at least one VM 12 VCPUs while Proxmox (and other VMs) also needs to do stuff like graphs and emulating the e1000. Try giving your VMs no more than 4 cores (each) and Proxmox will be much more responsive.

Proxmox VE, as a clustered enterprise hypervisor, is not designed for low-latency or giving all or al resource to a single VM. Maxing out a resource (like cores/threads) gives latency issues and stutters as other threads on this forum will show. Best to not give more than 4 or 5 cores to all VMs together that need low latency (and don't run other VMs when you want to enjoy the low latency). You can try fine-tuning it from there.
 
  • Like
Reactions: UdoB
leesteken said:
Your CPU only has 6 cores with 2 threads each and you are giving at least one VM 12 VCPUs while Proxmox (and other VMs) also needs to do stuff like graphs and emulating the e1000. Try giving your VMs no more than 4 cores (each) and Proxmox will be much more responsive.

Proxmox VE, as a clustered enterprise hypervisor, is not designed for low-latency or giving all or al resource to a single VM. Maxing out a resource (like cores/threads) gives latency issues and stutters as other threads on this forum will show. Best to not give more than 4 or 5 cores to all VMs together that need low latency (and don't run other VMs when you want to enjoy the low latency). You can try fine-tuning it from there.
Click to expand...
Tried lowering the allocated vCPU from 12 to 4 to this VM and re-added the GPU on the VM. Still getting the same issue. Currently trying to generate journalctl via an active ssh connection but it's taking a while, vm is still also "starting"

EDIT: here's the journalctl output
Code: 
Sep 24 23:12:33 CMDC01 pvedaemon[247920]: start VM 100: UPID:CMDC01:0003C870:053A467D:6AB53DE1:qmstart:100:root@pam:
Sep 24 23:12:33 CMDC01 pvedaemon[236597]: <root@pam> starting task UPID:CMDC01:0003C870:053A467D:6AB53DE1:qmstart:100:root@pam:
Sep 24 23:12:33 CMDC01 kernel: vfio-pci 0000:01:00.0: resetting
Sep 24 23:12:33 CMDC01 kernel: vfio-pci 0000:01:00.0: reset done
Sep 24 23:12:33 CMDC01 systemd[1]: Started 100.scope.
Sep 24 23:12:34 CMDC01 kernel: tap100i0: entered promiscuous mode
Sep 24 23:12:34 CMDC01 kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Sep 24 23:12:34 CMDC01 kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Sep 24 23:12:34 CMDC01 kernel: fwpr100p0: entered allmulticast mode
Sep 24 23:12:34 CMDC01 kernel: fwpr100p0: entered promiscuous mode
Sep 24 23:12:34 CMDC01 kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Sep 24 23:12:34 CMDC01 kernel: vmbr0: port 2(fwpr100p0) entered forwarding state
Sep 24 23:12:34 CMDC01 kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Sep 24 23:12:34 CMDC01 kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Sep 24 23:12:34 CMDC01 kernel: fwln100i0: entered allmulticast mode
Sep 24 23:12:34 CMDC01 kernel: fwln100i0: entered promiscuous mode
Sep 24 23:12:34 CMDC01 kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Sep 24 23:12:34 CMDC01 kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Sep 24 23:12:34 CMDC01 kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Sep 24 23:12:34 CMDC01 kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Sep 24 23:12:34 CMDC01 kernel: tap100i0: entered allmulticast mode
Sep 24 23:12:34 CMDC01 kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Sep 24 23:12:34 CMDC01 kernel: fwbr100i0: port 2(tap100i0) entered forwarding state
Sep 24 23:12:54 CMDC01 pveproxy[4074176]: proxy detected vanished client connection
Sep 24 23:12:56 CMDC01 systemd-journald[544]: Under memory pressure, flushing caches.
Sep 24 23:12:58 CMDC01 pvedaemon[244881]: <root@pam> successful auth for user 'root@pam'
Sep 24 23:12:59 CMDC01 pvestatd[1555]: got timeout
Sep 24 23:13:00 CMDC01 pveproxy[246044]: proxy detected vanished client connection
Sep 24 23:13:00 CMDC01 pveproxy[246044]: proxy detected vanished client connection
Sep 24 23:13:00 CMDC01 systemd-journald[544]: Under memory pressure, flushing caches.
Sep 24 23:13:02 CMDC01 pvestatd[1555]: status update time (10.110 seconds)
Sep 24 23:13:04 CMDC01 systemd-journald[544]: Under memory pressure, flushing caches.
Sep 24 23:13:34 CMDC01 pveproxy[4074176]: proxy detected vanished client connection
Sep 24 23:13:37 CMDC01 systemd-journald[544]: Under memory pressure, flushing caches.
Sep 24 23:13:42 CMDC01 pveproxy[246044]: proxy detected vanished client connection
Sep 24 23:14:08 CMDC01 pve-firewall[1556]: firewall update time (59.549 seconds)
Sep 24 23:14:08 CMDC01 pvestatd[1555]: status update time (65.633 seconds)
Sep 24 23:14:11 CMDC01 pvedaemon[236597]: <root@pam> successful auth for user 'root@pam'
Sep 24 23:14:15 CMDC01 systemd-journald[544]: Under memory pressure, flushing caches.
Sep 24 23:14:16 CMDC01 systemd-journald[544]: Under memory pressure, flushing caches.
Sep 24 23:15:01 CMDC01 pvedaemon[247920]: start failed: command '/usr/bin/kvm -id 100 -name WINSTAR -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qm>
Sep 24 23:15:20 CMDC01 systemd-journald[544]: Under memory pressure, flushing caches.
Sep 24 23:15:22 CMDC01 systemd-journald[544]: Under memory pressure, flushing caches.

EDIT2:
Yep, host is now completely unresponsive, still responding to pings but the webui is down as well as all my services.
 
Last edited:
Code: 
Sep 24 23:14:15 CMDC01 systemd-journald[544]: Under memory pressure, flushing caches.

That doesn't look good either. What else is running on the machine? The one VM alone shouldn't cause memory pressure.

Here's a theory: You have over committed memory elsewhere and the reason passing in the GPU slows everything down is because PCI pass-through causes all of the memory for the VM to be committed on startup, whereas without the pass-through the VM initially uses only part of its assigned memory.
 
  • Like
Reactions: leesteken
BobhWasatch said:
Code: 
Sep 24 23:14:15 CMDC01 systemd-journald[544]: Under memory pressure, flushing caches.

That doesn't look good either. What else is running on the machine? The one VM alone shouldn't cause memory pressure.

Here's a theory: You have over committed memory elsewhere and the reason passing in the GPU slows everything down is because PCI pass-through causes all of the memory for the VM to be committed on startup, whereas without the pass-through the VM initially uses only part of its assigned memory.
Click to expand...
This is what I am currently testing now, leaving all other LXCs and VMs powered off, reducing the allocated memory on the problematic VM

EDIT:
Confirmed, I did in fact, over commit my memory. Decreasing the allocated RAM on the problematic VM -4GB did the trick, disabling ballooning also did not help, will be keeping this feature turned on. Just because it's a home server and not in an Enterprise Production environment, doesn't mean capacity planning is no longer important lol.

Thanks @BobhWasatch for pointing that out. Marking this as solved
 
Last edited:
vaxis said:
Fake, meaning? can you please elaborate on this more?
Click to expand...
The IOMMU groups are supposed to reflect the isolation of devices. Two devices that can't be stopped from potentially messing with each other get put in the same group. Then stuff like VMs can look at the groups to avoid situations where the lack of isolation can cause problems.

But there is a somewhat popular patch (acs_override) that allows to insert fake isolation. The devices don't actually get isolated from each other but the kernel thinks they are and the groups reflect that. Basically like taking a can of paint to a cage, drawing a line in the middle and defining both halves to be their own cage to "work around" the "don't put the sheep in the same cage as the tiger" rule.

In OPs case everything is in its own group including the various functions of both GPUs. Imho that's unlikely to be real. Instead it looks more like the "yeah, everything's isolated, trust me bro" approach.
 
  • Like
Reactions: leesteken
You must log in or register to reply here.
Top Bottom
Back