Skip to content

Instantly share code, notes, and snippets.

Hey guys, me again. After a day of testing and fucking with VMware/Proxmox/The VM itself, i finially got it working!!!!

I just wanted to come back and make another post to firstly thank everyone who helped me figure this out. So many awesome suggestions. Moment of silence for those awesome people and the sheer amount of people at that! Glad to be a part of this community. Couldn't have done it without you guys!

Now, on to the second part. As i promissed, i am going to walk through all the steps i took to go from a VMware Player 12 VM to a glorious Proxmox VM.

Does it boot (AKA, bricked from the get-go)? Lets find out!

1.0. I first shutdown the VM in VMware Player 12 and copied all .vmdk files to an external HDD so i can start the prod server up again since player didn't have a export function. Technically there is a [ovf exporter tool](https://developer.broadcom.com/tools/open-virtualization-format-ovf-too

Turning a cluster member into a standalone node

TL;DR Making a node that was once part of a cluster standalone again can be counter-intuitive compared to simply removing nodes from list of cluster members.


ORIGINAL POST Turning a cluster member into a standalone node

Proxmox VE nag removal, manually - Proxmox PVE 8.4.2+, PBS 3.4.3+

TL;DR Brief look at what exactly brings up the dreaded notice regarding no valid subscription. Eliminate bad UX that no user of free software should need to endure.

@kenrmayfield
kenrmayfield / Copy-GPU-Drivers-VM.ps1 - PowerShell script to copy GPU drivers to Hyper-V Virtual Machine for passthrough.
Last active September 6, 2025 12:01 — forked from ThioJoe/Copy-GPU-Drivers-VM.ps1
PowerShell script to copy GPU drivers to Hyper-V Virtual Machine for passthrough.
# Description: This script will automatically copy the necessary GPU drivers from your current host machine into a Hyper-V Virtual Machine
# so you can pass through the GPU to the VM. You should run this whenever you update your graphics drivers on the host.
#
# Author: ThioJoe -- https://github.com/ThioJoe
#
# Note: Currently this only works for Nvidia GPUs. But it does support if you have multiple GPUs.
#
# OPTIONAL ARGUMENTS:
# -debug | Enables debug messages that pause the script for each step (No additional string required, just add -debug)
# -name | Sets the virtual machine name so it doesn't need to ask
@kenrmayfield
kenrmayfield / newfile.md
Created September 30, 2025 13:29 — forked from Cordtus/newfile.md
Enabling GPU access by LXC containers

NVIDIA GPU Access in LXC/LXD Containers

This guide explains how to properly configure NVIDIA GPU access for your Telegram Sticker Bot running in an LXC/LXD container.

🎯 Prerequisites

Host System Requirements

  • NVIDIA GPU with drivers installed
  • LXD/LXC properly installed
  • NVIDIA Container Runtime
# 🏡 Home Server Guide: Proxmox + HAOS + Frigate + Coral TPU
(Verified Working Build — Minimal First → Add Complexity Later)
This guide walks through building a reliable, low-maintenance **home-automation** and **NVR setup** using:
* **Proxmox VE** (host virtualization platform)
* **Home Assistant OS (HAOS)** in a VM
* **Frigate NVR** in a Debian 12 LXC (Docker-based)
* *Optional:* **Coral TPU** (object-detection acceleration)
* *Optional:* **GPU decoding** (Intel iGPU)