Proxmox? Reboot Thrice - Now with More Prism 🌈 (HDGL)

It’s almost winter. That means it’s time to fire back up the old Proxmox array. Only in recent weeks, things have changed drastically. Do we still need Proxmox? I’m sort of… leaning towards not really. And I’m not pointing towards another alternative 3rd party software. No, no, that would be too… 3rd party. This time, my loyal sport fans and friendemies, my solution is being developed in-house…

Just kidding, I’ll still use Proxmox. But I’m not planning on letting that old dusty rack fire back up without my proprietary custom prismatic analog computer (in software) as a special man-in-the middle (OS-agnostic; nay, invisible in its primitives) layer.

This probably isn’t important, I just like its simplicity and don’t want to forget the thought that it helped me find. GitHub - dell/dkms: Dynamic Kernel Module Support

To attend:

Firmware Augment + Bootstrap + Kernel Augment

v0.1 (ALPHA - USE AT YOUR OWN RISK)


Stay tuned..

This is an analog computer demo running on top of binary. It is capable of multiple discrete instances (like Windows/Linux, only much simpler at this time) sharing the same analog fabric. Placing load upon each of the 32 slots has a unique impact upon individual slots until the system levels off the load. Although it’s optimal to run analog programs on native-analog, it’s possible to install discrete binary programs as our proof of concept. And, since most programs are in binary, this is an important milestone in development. You can see a similar effect when you hit alt + ctrl + del on your own computer, but on your computer this would be processor cores, while in this demo it is virtualized analog “cores” (32 of them) called slots.
Actually, that three-fingered salute has similar origin stories to this visualizer. It’s simple but depicts what it needs to.
These 32 slots are arranged by eight strands, which you might notice is no accident - each of these eight is labelled the same as musical notes. The eighth note is a harmonic of the 1st, just as with music, and we can easily add more.



See how the bands taper off into one band under no load?



Seen this before? It’s actually pretty useful - https://www.youtube.com/watch?v=jhaTULO2Zkc

DEMO - Index of /demo/

A calculator that runs on analog logic, and a few other bells and whistles

A casual observer might assume I’m just rendering fancy drawings. A more detailed observation will note that these renderings are not possible at this level of detail on the hardware you probably have. Snappy, even, you might be correct to say? These run on an analog computer which rides on a traditional binary computer.

This is no ordinary analog computer. This analog computer runs on superposition, sacred geometry, recursion, prisms a few other tricks I have developed. The analog computer lives in a script which runs on your phone or laptop, but that analog computer could be made into a kernel. Kernels are what operating systems run off of.

https://josefkulovany.com/demo/9.22.25%20-%20radio2/fibdonut/fibdonut17.html

You know how countries fight over chip manufacturers like TSMC? They need not…











At this magnitude, it literally won’t let me go to zero. I can go pretty much anywhere else but zero, but it’s almost like how a magnet feels trying to grab zero!







NOTE: This is not an elegant solution, as 1 GPU = 1 Container.

In my use case, I have an Ubuntu desktop for my testbed where Proxmox lives inside of Ubuntu and beside also Windows. This is a bit of a pain to get going, but after it’s set up my testbed is one computer. This is particularly useful for me, as during the summer it gets very hot here and I don’t need the full cluster for testing various containers on-the-fly without the need for redundancy (yet).

It’s sort of the blight of many Proxmox users at this time, I think, to scrap everything and start over time to time. Sure there are better ways to do this but sometimes it’s just faster to scrap and reset literally everything (just being honest).

Now if you’re down to one computer, that’s when it’s really nice to have lots of threads. For me I finally got around to switching to my workhorse - a Threadripper 1950X which was last year the mothership of my stack and this year is my main squeeze. I finally treated myself to an RTX 2060 12GB (not 6, mind!), so now my new primary has team red (RX 480 8GB) and team green Nvidia for that CUDA as well.

Why RTX 2060? Well, it’s the last Nvidia card to (technically) support SLi and it came with 12GB which manufacturers are skimping you on for newer cards.

I will probably get around to using MSI afterburner to cool things off next summer and keep this hardware lasting for as long as possible. So far I’ve completely amortized the Radeon card ($150 in 2016) and here’s to hoping EVGA is still the quality my computer shop has lived by. These are really my only two consumer cards that aren’t ancient, though some might say even this computer tech’s setup is getting quite dusty. It just goes to show you, new hardware is overrated (mostly), though if I wanted to go thin, nimble, and local I would opt for the newer hardware in that case.

Speaking of case, I’m rocking a CoolerMaster LAN party. It has proved very future-proof and relatively discrete, maybe even a good conversation piece.

I’ve not discussed it in depth, but most of my work is seasonal as with the seasons. Things really “heat up” around here in winter, while in summer I’m on the thinnest client I can limp along with, which unfortunately for me is still largely on the cloud. Hopefully by next summer local AI is easier to work with and more powerful.

You can run your full stack year round, but then you encounter the power usage competing your air conditioner with your space heater. Much better for me to only use what I need, all else equal. If I had all the money in the world, I’d throw money at both year-round, youuuu betcha.

For our Windows virtualized inside of Ubuntu latest setup, I’ve found Qemu/KVM is the most practical. I don’t much care for its UI nor default parameters revolving around GPU passthrough, but the rest I chose simply because my preferred Oracle solution was conflicting with Qemu/KVM, so Qemu/KVM won the day.

The alternative is using WSL inside of Windows. Now this is getting simpler to use here in 2025, but still has some trouble with network or port conflicts and my Visual Studio co-pilot really likes to spend tokens forgetting whether it’s in powershell or WSL which are tiring to override.

Actually right now I’m dual-booting 1) Windows with WSL 2.0 (Ubuntu) inside of it on one M.2. and 2) My newer instance which is Ubuntu Latest with both Proxmox and Windows installed on another M.2. It’s a good idea to have a Raid1 (Mirror) backup array and an external cold storage USB 3.1 hard drive or even tape drive (have you heard of such a thing?!) if you’re down to only one client.

Yes, it is possible to window yourself where you forget what environment you’re actually in if you’re not paying attention to your workflow. Careful consideration of the parameters of your preferred setup before you roll up your sleeves is a must - measure twice, cut once. Or just dual-boot and virtualize in each. What’s your fancy?

I do see why Threadripper is overpriced. It took me some haggling with an old customer and with Ebay to frankenstein my 1950X 32-fast-thread with an ebay board that came with an extra 1900X that is just waiting to be re-sold. But man, when I finally got it going, I have ample wiggle room for lot of cards including also a PCI-e M.2 SSD and with eight memory slots I can expand to 128GB for about average competition with new gear, not bad for old hardware.

I do really want to get my stack online. Part of the problem is my chosen environment is a cold basement and I’m kind of a lightweight. Factor the need for a jacket and a good attitude in the cold if you’ve chosen the right spot, I’ve often said.

As with most things, the computer goes at exactly one speed but the human’s gotta feed the monkey. Factor that in too, if you’re being honest.