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

推荐订阅源

N
Netflix TechBlog - Medium
I
InfoQ
Engineering at Meta
Engineering at Meta
Jina AI
Jina AI
Recent Announcements
Recent Announcements
T
The Blog of Author Tim Ferriss
P
Proofpoint News Feed
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
D
Docker
Microsoft Security Blog
Microsoft Security Blog
宝玉的分享
宝玉的分享
Last Week in AI
Last Week in AI
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
GbyAI
GbyAI
博客园 - Franky
博客园 - 聂微东
Microsoft Azure Blog
Microsoft Azure Blog
博客园 - 叶小钗
酷 壳 – CoolShell
酷 壳 – CoolShell
B
Blog RSS Feed
WordPress大学
WordPress大学
MyScale Blog
MyScale 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!