Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Idea: Proxmox support in every layout (testers wanted)

Abierto
  • ¿Algo no está bien?
#128 2 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@sharmis-tp ya está trabajando en esto.

Desde el 27/10/2026.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go, linux
Área
devtools, infrastructure

Línea de trabajo

Start by reading the Berth documentation and the existing berth env, berth run, and berth vfio entry points. The issue proposes detection and behavior across Proxmox hosts, LXC containers, VMs, GPU drivers, and multiple cards, but does not identify source files or tests. Done means the applicable layouts are detected and reported as described, with berth env remaining read only; the maintainer is still seeking testers before work is ready to try.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement help wanted

A lot of you run local models on Proxmox. Berth should work there in each common layout and tell you which one it is in. I have Proxmox hosts but none with an NVIDIA card, so I need your setups to test against.

Layout Where Berth runs Today Planned for v0.4
GPU on the host, /dev/nvidia* mounted into LXC containers the host Berth sees every container's GPU processes, but as bare PIDs Processes named by container ("LXC 101 (ollama)"). berth run inside a container leases the host's card. A system service for hosts with no user session
GPU passed through to a VM inside the VM Works like any Linux machine A host-side Berth shows the card as passed through and names the VM
One card moved between the host and a VM the host berth hold around qm start berth vfio run drains the card and checks that nothing holds it before your hookscript switches the driver
Berth inside an LXC that has the GPU the container Works for that container's own engines; it cannot see other containers berth env tells you to run it on the host instead
Several GPUs one berthd --gpu N per card Works, but each engine has to pick its daemon Real multi-GPU scheduling is v0.5

berth env will detect the layout: Proxmox host, LXC or VM, which driver owns each card, which VM holds a passed-through card, and which containers mount the GPU. It then says where Berth belongs. It only reads; it changes nothing.

If you run Proxmox for inference, please comment with:

  • your layout from the table, or one it misses
  • GPUs and VRAM
  • Proxmox VE version, and privileged or unprivileged containers
  • the engines you run (Ollama, llama.cpp, vLLM, ComfyUI...)

I'll ping you when there is something to try.

Lenguaje dominante
Go
Estrellas
226
Forks
20
Merge medio
43 min
PR fusionados (30 d)
192

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de T-Crypt/berth

Todos los issues de T-Crypt/berth

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.