Hyacin (He/Him)

  • 0 Posts
  • 6 Comments
Joined 2 years ago
cake
Cake day: December 29th, 2023

help-circle

  • Currently messing around with Talos Linux in a VM.

    Yes!! Now LOVE Talos, after, drumroll, trying it out in my lab on my Proxmox boxes!! Figured it out ‘good enough’, and then rolled a live cluster with it - also on the same Proxmox hardware!! Labs, production services, loaner ‘lab boxes’ for people doing certs - with hardware to spare! LOVE Proxmox so much!!!


  • Proxmox.

    /thread

    Anything else you want to run, you can run in Proxmox. If it’s too much hardware for what you’re doing, all the more reason to run Proxmox. You can build an Arch VM, and NixOS VM, and whatever else you want in it!

    If you go with just one of them right on the hardware, that’s all you can do with it, you’re done, you’re stuck.

    When you have Proxmox on it, you can try every OS! And then some! It is a superpower for learning.


  • Hardware Acceleration for Jellyfin: On the EliteDesk, I’d like to enable hardware acceleration for a VM running Jellyfin (in Docker) using the i7-9700’s UHD 630 iGPU. Can anyone recommend a clear guide specific to this CPU? The Proxmox documentation isn’t very detailed for Intel GPUs.

    I feel like I’ve done this, but it was a VERY long time ago. It certainly wasn’t from a guide specific for this, but from adapting other instructions. Whole idea with a home lab - learn stuff, break stuff, figure stuff out! :-)

    Wish I could be more helpful! But iirc, once you understand the gist of passing the hardware through, blocking kernel models on the host, and installing the required drivers in the guest, it’s applicable to basically everything.

    As for Backblaze for ‘home lab’ backups, that sounds expensive? I run PBS on a container on my NAS for my backups - keeps it all local and effectively ‘free’. Only the things I REALLY care about - like my git server with all the code I’ve written for the lab, and even some of the more complex/outside the box configurations get backed up to the public cloud. Simple ‘cattle’ VMs do not justify additional expenses for me.

    It’s fun as hell! I’ve been running Proxmox for many years now and still enjoy it VERY much. I’ve recently added 3x 12GB bus-powered A2000s to my Dell workstations. Having oodles of fun running things like piper, whisper, ollama and frigate models on them in a new k8s cluster I spun up just for ML workloads.



  • I mostly agree, and did the same with my second gen lab build - instead of shiny new NUCs like I had used round 1, I bought old off lease Dell Xeon boxes. SO MANY PROS -

    • Got them up to 14c/28t each
    • They can take GPUs and actually do heavy transcoding/ML work
    • They can take up to like, 128GB of memory, which is GREAT when they’re all hypervisors

    The downsides can’t be denied though -

    • Even without the GPUs and beefed up CPUs, they are power hogs - the CPU alone uses more than an ENTIRE NUC
    • They run HOT
    • They run LOUD

    The same holds true for off-lease SFF stuff, Lenovo and the likes …

    So while reuse/repurpose is absolutely of the utmost importance, no question - when it comes to technology and how quickly it advances and miniaturizes, a thorough and logical pros/cons list is often required.

    I’d add another option though - if you do need what a Pi brings to the table - do you really need a shiny new Pi 5? Is it possible a used Pi 3 or Pi 4 would do the trick, and check the reuse box?