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

推荐订阅源

Engineering at Meta
Engineering at Meta
人人都是产品经理
人人都是产品经理
aimingoo的专栏
aimingoo的专栏
M
MIT News - Artificial intelligence
Recent Announcements
Recent Announcements
V
Visual Studio Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
MyScale Blog
MyScale Blog
Hugging Face - Blog
Hugging Face - Blog
宝玉的分享
宝玉的分享
H
Hackread – Cybersecurity News, Data Breaches, AI and More
博客园 - 叶小钗
博客园 - 聂微东
U
Unit 42
F
Fortinet All Blogs
Microsoft Security Blog
Microsoft Security Blog
GbyAI
GbyAI
IT之家
IT之家
The GitHub Blog
The GitHub Blog
Stack Overflow Blog
Stack Overflow Blog
MongoDB | Blog
MongoDB | Blog
Y
Y Combinator Blog
A
About on SuperTechFans
博客园 - 三生石上(FineUI控件)

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
Proxmox + Older NVIDIA GPUs (GTX 1060 / P4000 / V100) LXC...
invalid@exam · 2026-06-17 · via Proxmox Support Forum

Recommended Configurations​

Most Proven Configuration​

Code:

Proxmox Kernel 6.14 / 6.17
NVIDIA Driver 575.57.08
CUDA 12.9.1

Works well with:

  • GTX 1060 / 1070 / 1080
  • Quadro P4000 / P5000
  • Tesla V100

New Configuration (Kernel 7.x)​

Code:

Proxmox Kernel 7.x
NVIDIA Driver 580.159.04
CUDA 13.x

Reported working with:

  • Tesla V100
  • Various Volta-based GPUs

Kernel 7.x support is still evolving for older Pascal cards. If stability is your top priority, stay on Kernel 6.x.


HOST INSTALLATION​

Install build tools:

Code:

apt update
apt install -y build-essential dkms pve-headers-$(uname -r)

Download NVIDIA driver:

575 branch:

Code:

wget https://us.download.nvidia.com/tesla/575.57.08/NVIDIA-Linux-x86_64-575.57.08.run

580 branch:

Code:

wget https://us.download.nvidia.com/tesla/580.159.04/NVIDIA-Linux-x86_64-580.159.04.run

Make executable:

Code:

chmod +x NVIDIA-Linux-x86_64-580.159.04.run

Install:

Code:

./NVIDIA-Linux-x86_64-580.159.04.run

Installer recommendations:

  • YES to DKMS
  • NO to OpenGL libraries (headless server)

Reboot:

Verify:



LXC GPU PASSTHROUGH​

Edit container config:

Add:

Code:

lxc.cgroup2.devices.allow: c 195:* rwm
lxc.cgroup2.devices.allow: c 509:* rwm
lxc.cgroup2.devices.allow: c 511:* rwm

lxc.mount.entry: /dev/nvidia0 dev/nvidia0 none bind,optional,create=file
lxc.mount.entry: /dev/nvidiactl dev/nvidiactl none bind,optional,create=file
lxc.mount.entry: /dev/nvidia-modeset dev/nvidia-modeset none bind,optional,create=file
lxc.mount.entry: /dev/nvidia-uvm dev/nvidia-uvm none bind,optional,create=file
lxc.mount.entry: /dev/nvidia-uvm-tools dev/nvidia-uvm-tools none bind,optional,create=file

Restart:



MULTIPLE GPU SETUPS​

Check GPU numbering:

Example:

Code:

GPU 0: Tesla V100
GPU 1: Quadro P4000
GPU 2: GTX 1060

Pass only a specific GPU:

Code:

lxc.mount.entry: /dev/nvidia1 dev/nvidia1 none bind,optional,create=file

Pass multiple GPUs:

Code:

lxc.mount.entry: /dev/nvidia0 dev/nvidia0 none bind,optional,create=file
lxc.mount.entry: /dev/nvidia2 dev/nvidia2 none bind,optional,create=file

Limit CUDA visibility:

Code:

export CUDA_VISIBLE_DEVICES=0

or

Code:

export CUDA_VISIBLE_DEVICES=0,1


INSIDE THE CONTAINER​

Download the same driver version as the host.

Example:

Code:

wget https://us.download.nvidia.com/tesla/580.159.04/NVIDIA-Linux-x86_64-580.159.04.run

Install userspace libraries only:

Code:

chmod +x NVIDIA-Linux-x86_64-580.159.04.run

./NVIDIA-Linux-x86_64-580.159.04.run --no-kernel-module

Verify:



OPTIONAL CUDA INSTALLATION​

CUDA 12.9.1 (575 branch):

Code:

wget https://developer.download.nvidia.com/compute/cuda/12.9.1/local_installers/cuda_12.9.1_575.57.08_linux.run

Install:

Code:

chmod +x cuda_12.9.1_575.57.08_linux.run

./cuda_12.9.1_575.57.08_linux.run

Skip driver installation during CUDA setup.


CURRENT RECOMMENDATION​

For Tesla V100:

For mixed environments (GTX 1060 + P4000 + V100):

Code:

Kernel 6.14/6.17 + 575.57.08

until broader Kernel 7.x compatibility is consistently confirmed across Pascal GPUs.

Last edited:

Didn't you post this already? I remember answering to this with some suggestions.