LXC iGPU Host Crash

Lip90

Well-Known Member
Dec 12, 2018
31
0
46
34
I installed frigate on debian lxc and Docker with access to the 5650GE iGPU. Everytime frigate use the hardware acceleration the hole proxmox system crash completly. Does anyone have an idea what I can do? I've already googled but haven't found anything.
 
Hi,

I would check the syslog when the Proxmox VE crashes and look for interesting messages. This will give you/us more information about what happened.
 
@Moayad thanks for your reply

Here is the output from the last crash:

I have bolded the error which was marked in red in the output. It seems that the problem has something to do with Groups. Unfortunately my knowledge is not sufficient to fix this. Can you help me?

Bash:
root@pve:~# journalctl --since=19:18:00
Apr 11 19:18:02 pve systemd[1]: Stopping user@0.service - User Manager for UID 0...
Apr 11 19:18:02 pve systemd[3655051]: Activating special unit exit.target...
Apr 11 19:18:02 pve systemd[3655051]: Stopped target default.target - Main User Target.
Apr 11 19:18:02 pve systemd[3655051]: Stopped target basic.target - Basic System.
Apr 11 19:18:02 pve systemd[3655051]: Stopped target paths.target - Paths.
Apr 11 19:18:02 pve systemd[3655051]: Stopped target sockets.target - Sockets.
Apr 11 19:18:02 pve systemd[3655051]: Stopped target timers.target - Timers.
Apr 11 19:18:02 pve systemd[3655051]: Closed dbus.socket - D-Bus User Message Bus Socket.
Apr 11 19:18:02 pve systemd[3655051]: Closed dirmngr.socket - GnuPG network certificate management daemon.
Apr 11 19:18:02 pve systemd[3655051]: Closed gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web>
Apr 11 19:18:02 pve systemd[3655051]: Closed gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Apr 11 19:18:02 pve systemd[3655051]: Closed gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Apr 11 19:18:02 pve systemd[3655051]: Closed gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Apr 11 19:18:02 pve systemd[3655051]: Removed slice app.slice - User Application Slice.
Apr 11 19:18:02 pve systemd[3655051]: Reached target shutdown.target - Shutdown.
Apr 11 19:18:02 pve systemd[3655051]: Finished systemd-exit.service - Exit the Session.
Apr 11 19:18:02 pve systemd[3655051]: Reached target exit.target - Exit the Session.
Apr 11 19:18:02 pve (sd-pam)[3655052]: pam_unix(systemd-user:session): session closed for user root
Apr 11 19:18:02 pve systemd[1]: user@0.service: Deactivated successfully.
Apr 11 19:18:02 pve systemd[1]: Stopped user@0.service - User Manager for UID 0.
Apr 11 19:18:02 pve systemd[1]: Stopping user-runtime-dir@0.service - User Runtime Directory /run/user/0...
Apr 11 19:18:02 pve systemd[1]: run-user-0.mount: Deactivated successfully.
Apr 11 19:18:02 pve systemd[1]: user-runtime-dir@0.service: Deactivated successfully.
Apr 11 19:18:02 pve systemd[1]: Stopped user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Apr 11 19:18:02 pve systemd[1]: Removed slice user-0.slice - User Slice of UID 0.
Apr 11 19:18:37 pve kernel: br-8a993983158b: port 1(vethbfaef56) entered blocking state
Apr 11 19:18:37 pve kernel: br-8a993983158b: port 1(vethbfaef56) entered disabled state
Apr 11 19:18:37 pve kernel: vethbfaef56: entered allmulticast mode
Apr 11 19:18:37 pve kernel: vethbfaef56: entered promiscuous mode
[B]Apr 11 19:18:37 pve systemd-udevd[799]: /etc/udev/rules.d/70-amdgpu.rules:1 Invalid operator for GROUP.[/B]
Apr 11 19:18:37 pve kernel: eth0: renamed from vetheecb0d9
Apr 11 19:18:37 pve kernel: br-8a993983158b: port 1(vethbfaef56) entered blocking state
Apr 11 19:18:37 pve kernel: br-8a993983158b: port 1(vethbfaef56) entered forwarding state
-- Boot 0638f6ef52ac4ff6b9e73836b1cc349a --
Apr 11 19:21:25 pve kernel: Linux version 6.5.13-3-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian>
Apr 11 19:21:25 pve kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.13-3-pve root=/dev/mapper/pve-root ro initcall_blacklist=acpi_c>
Apr 11 19:21:25 pve kernel: KERNEL supported cpus:
Apr 11 19:21:25 pve kernel:   Intel GenuineIntel
Apr 11 19:21:25 pve kernel:   AMD AuthenticAMD
Apr 11 19:21:25 pve kernel:   Hygon HygonGenuine
Apr 11 19:21:25 pve kernel:   Centaur CentaurHauls
Apr 11 19:21:25 pve kernel:   zhaoxin   Shanghai
Apr 11 19:21:25 pve kernel: BIOS-provided physical RAM map:
Apr 11 19:21:25 pve kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Apr 11 19:21:25 pve kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Apr 11 19:21:25 pve kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009ca5fff] usable
Apr 11 19:21:25 pve kernel: BIOS-e820: [mem 0x0000000009ca6000-0x0000000009ffffff] reserved
Apr 11 19:21:25 pve kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
Apr 11 19:21:25 pve kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20efff] ACPI NVS
Apr 11 19:21:25 pve kernel: BIOS-e820: [mem 0x000000000a20f000-0x000000009cd12fff] usable
Apr 11 19:21:25 pve kernel: BIOS-e820: [mem 0x000000009cd13000-0x000000009cd13fff] reserved
Apr 11 19:21:25 pve kernel: BIOS-e820: [mem 0x000000009cd14000-0x000000009cd3cfff] usable
Apr 11 19:21:25 pve kernel: BIOS-e820: [mem 0x000000009cd3d000-0x000000009cd3dfff] reserved
Apr 11 19:21:25 pve kernel: BIOS-e820: [mem 0x000000009cd3e000-0x00000000b9114fff] usable
Apr 11 19:21:25 pve kernel: BIOS-e820: [mem 0x00000000b9115000-0x00000000ba86efff] reserved
Apr 11 19:21:25 pve kernel: BIOS-e820: [mem 0x00000000ba86f000-0x00000000ba8bcfff] ACPI data

Code:
root@pve:~# pveversion -v
proxmox-ve: 8.1.0 (running kernel: 6.5.13-3-pve)
pve-manager: 8.1.10 (running version: 8.1.10/4b06efb5db453f29)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.5.13-3-pve-signed: 6.5.13-3
proxmox-kernel-6.5: 6.5.13-3
proxmox-kernel-6.5.13-1-pve-signed: 6.5.13-1
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.3
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.5
libpve-cluster-perl: 8.0.5
libpve-common-perl: 8.1.1
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.6
libpve-network-perl: 0.9.6
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.1.4
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.5-1
proxmox-backup-file-restore: 3.1.5-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.5
proxmox-widget-toolkit: 4.1.5
pve-cluster: 8.0.5
pve-container: 5.0.9
pve-docs: 8.1.5
pve-edk2-firmware: 4.2023.08-4
pve-firewall: 5.0.3
pve-firmware: 3.9-2
pve-ha-manager: 4.0.3
pve-i18n: 3.2.1
pve-qemu-kvm: 8.1.5-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.1.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.3-pve1
 
Last edited:

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!

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!