I Broke My Proxmox Home Lab with a GPU Passthrough - Here's How I Fixed It
The author experienced a crash loop in their Proxmox home lab after attempting to implement GPU passthrough for a Kubernetes worker VM. The issue arose when the VM automatically started at boot, causing the system to crash due to the GPU being grabbed by the VM. The solution involved intervening at the GRUB level to prevent the VM from starting automatically.
- ▪The home lab setup included various self-hosted services running on Proxmox.
- ▪The crash loop was triggered by the automatic startup of a VM configured for GPU passthrough.
- ▪The author had to physically access the machine to modify boot parameters at the GRUB level to resolve the issue.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 862755) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Pendela BhargavaSai Posted on May 19 I Broke My Proxmox Home Lab with a GPU Passthrough - Here's How I Fixed It #kubernetes #linux #devops #proxmox How a Kubernetes worker VM with a passed-through AMD GPU sent my entire home lab into an infinite crash loop — and the GRUB-level trick that saved it. What I Was Trying to Do My home lab runs on a Mini PC with Proxmox as the hypervisor.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
