Live data from Hacker News

Running MicroVMs in Proxmox VE, the Easy Way

taoofmac.com

41–50 of 52 posts

Re: Running MicroVMs in Proxmox VE, the Easy Way

#42
post #19

My favorite microVM discovery recently has been tools built around libkrun. See smolvm[0]. The killer feature still missing from microVMs for me is the ability to enable CUDA support without passing through the entire GPU. vfio is just too much of a pain and too limiting. Sometimes I want to use my GPU on the host. Vulkan works fairly well with virtio-gpu and Venus, but I need CUDA. Venus is also still missing some i…

author of smolmachines here, CUDA support is possible based on a cursory dive. I'll keep you posted on it ref: https://thevirtualhorizon.com/2024/05/31/how-to-configure-th...

I think the main blocker is on nvidia's side, which is that vGPU is only available for enterprise customers/products.

Re: Running MicroVMs in Proxmox VE, the Easy Way

#44
This is nice. I have a Proxmox system but hate how much (IMO unnecessary) complexity managing VMs entails. This is definitely a step towards slimmer VMs. I’m generally trying to replicate some of the UX of running containers, so the OCI import being much appreciated.

In my own microVM experiments I’ve actually managed to get the machine to boot from a plain folder (some virtiofs setup, I can look around if anyone’s interested, but there should be more documentation about it now) - I find that pretty awesome.

Re: Running MicroVMs in Proxmox VE, the Easy Way

#45

Earlier quoted context omitted.

I'm not the person you replied to, but I came from using VMware products for 12 years, to using Proxmox this last 1.5 years. These are my impressions. First of all it's a very competent product, mainly thanks to Ceph making it HCI. Without Ceph, I'm not sure what we would do. It's as effective as you design it, make sure to separate storage and cluster traffic to ensure robustness, and speed. Make sure to use at leas…

When it comes to templates, I shut then down and take a backup, and then just restore that backup to a different node

So you deploy a new VM from a template, shut it down, take a backup and then restore that backup to your target node. Is all this done with IaC? Ansible? Even the backup part?

I haven't touched backups with Ansible yet.

Re: Running MicroVMs in Proxmox VE, the Easy Way

#46

Earlier quoted context omitted.

When it comes to templates, I shut then down and take a backup, and then just restore that backup to a different node

So you deploy a new VM from a template, shut it down, take a backup and then restore that backup to your target node. Is all this done with IaC? Ansible? Even the backup part? I haven't touched backups with Ansible yet.

Typically I don't touch templates once I do their initial setup, just shut them down and take a backup (can be done using ansible through the PVE CLI)

The backup restore and the VM startup is done through ansible > PVE CLI.

I also have a testing VM that has a "CLEAN" snapshot that I restore to multiple times a day, using ansible > PVE CLI. Once the VM snapshot is restored I turn it back on as well using the PVE CLI

Re: Running MicroVMs in Proxmox VE, the Easy Way

#47
post #34

Earlier quoted context omitted.

Yeah, I love this from a geek appeal and I have a beefy home lab (Dual Xeon Silver 4116 with 384GB, and 12TB of RAID10 SSD connected via 10gig), but being a homelab I want to eke out all my performance so I keep looking at LXC on my Proxmox box versus the optimization of VMs (does this machine really need 8GB or 6? Or 5?). But when there's the discussion of the amount of time Qemu spends "in grub" and "probing legacy…

I think in most scenarios you don't need to worry so much about kvm ram use, since it looks static but actually it's not and you can over-commit [1]. And of course disk allocation can be dynamic as well. I prefer a lot more security for a bit less flexibility. I am not as ram rich as you are, and still every time I think of my few LXCs, my main thought is 'why did I do that?'. [1] https://docs.redhat.com/en/documenta…

That's true. I know that the dashboard shows the "real" aggregated RAM usage, and truth be told, I'm not particularly utilizing the server to its full extent (I got very lucky, it's a small rack with three PowerEdges, a UPS, 2U Synology box with SSDs, 10 gig switch etc., that I got from a previous employer, and when they found out the cost to ship it all, insured, back across the country when I left them, they looked at the depreciation schedule and said "keep it".

Re: Running MicroVMs in Proxmox VE, the Easy Way

#48

Earlier quoted context omitted.

So you deploy a new VM from a template, shut it down, take a backup and then restore that backup to your target node. Is all this done with IaC? Ansible? Even the backup part? I haven't touched backups with Ansible yet.

Typically I don't touch templates once I do their initial setup, just shut them down and take a backup (can be done using ansible through the PVE CLI) The backup restore and the VM startup is done through ansible > PVE CLI. I also have a testing VM that has a "CLEAN" snapshot that I restore to multiple times a day, using ansible > PVE CLI. Once the VM snapshot is restored I turn it back on as well using the PVE CLI

Oh I see, your restore of template backup is actually how you deploy a new VM. Interesting!

Re: Running MicroVMs in Proxmox VE, the Easy Way

#49
post #38
post #10

One of my Proxmox hosts is glacially slow at running VMs. (Dell R520; I have a same-generation server that is fine at VMs, so not sure what the root cause is). I wonder if this would help performance.

Doubt it because you clearly have a problem there. Same kind of disk?

Yep, 7200 RPM spinning rust.

Re: Running MicroVMs in Proxmox VE, the Easy Way

#50
post #10

One of my Proxmox hosts is glacially slow at running VMs. (Dell R520; I have a same-generation server that is fine at VMs, so not sure what the root cause is). I wonder if this would help performance.

Any chance irq-balance isn't running on the slow one, but is running on the ok one?
Post reply on HN