惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Blog — PlanetScale
Blog — PlanetScale
J
Java Code Geeks
N
Netflix TechBlog - Medium
Martin Fowler
Martin Fowler
A
About on SuperTechFans
腾讯CDC
B
Blog RSS Feed
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Microsoft Azure Blog
Microsoft Azure Blog
D
Docker
Y
Y Combinator Blog
Microsoft Security Blog
Microsoft Security Blog
F
Fortinet All Blogs
I
InfoQ
博客园 - 【当耐特】
美团技术团队
GbyAI
GbyAI
量子位
宝玉的分享
宝玉的分享
爱范儿
爱范儿
有赞技术团队
有赞技术团队
博客园 - Franky
L
LangChain Blog
阮一峰的网络日志
阮一峰的网络日志

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
/dev/dri/renderD128 group mismatch after update – best pr...
invalid@exam · 2026-06-17 · via Proxmox Support Forum

Hello everyone,

I have a small but annoying issue with GPU passthrough (/dev/dri/renderD128) on my Proxmox host (Community Edition).

The problem appeared after a recent update. The device node somehow got assigned to the messagebus group:

bash
ls -all /dev/dri/renderD128
crw-rw---- 1 root messagebus 226, 128 Jun 16 18:10 /dev/dri/renderD128
On the host, render has GID 993, while messagebus has GID 992. My Debian Trixie containers use GID 992 for render by default.

So I'm stuck with a mismatch:

  • Host expects GID 993 for render
  • Containers expect GID 992
  • The device is stuck on GID 992 (messagebus)

Options I see:

  1. Change all Trixie containers to GID 993 (groupmod -g 993 render) and fix the host udev rule.
  2. Keep containers on GID 992 and assign the device to GID 992 on the host (but that would mean it stays under messagebus, which feels wrong).

I'm leaning toward option 1, but I wanted to ask: What is the cleanest/best practice way to handle this?

Has anyone else seen this after a recent Community Edition update? Any advice would be much appreciated!

Thanks in advance!