21–30 of 52 posts
back when I used to use cursor I build this mcp but it should work for codex or claude
it lets me easily spin up vms with specs
its tough to create boxes now due to ram prices but got mine at a great time when it was very cheap; i just wish i had bought more then
FWWI, we did evaluate and benchmark microVMs back in 2020. Back then it was not really seen worth it the maintenance cost compared to what it brought to the table, but it makes sense to re-evaluate that again soonish; with native dynamic load balancing and affinity rules (and further orchestration improvements being lined up) they might be better leveraged today. Oh, and mailing lists are a bliss to use compared to (…
But when there's the discussion of the amount of time Qemu spends "in grub" and "probing legacy devices", maybe my use case is different, but my VMs aren't constantly being rebooted and when the VM is up it is near native speed so...
proxmox has been great although it comes with a learning curve back when I used to use cursor I build this mcp but it should work for codex or claude it lets me easily spin up vms with specs its tough to create boxes now due to ram prices but got mine at a great time when it was very cheap; i just wish i had bought more then https://github.com/agentify-sh/cursor-proxmox-mcp
This is clever work, especially given that Proxmox is already a very viable VMware replacement and wasn’t originally designed around microVMs as the primary abstraction. I’m glad this is working well for you. We’ve been on a similar journey, but came at it from the opposite direction. We started SlicerVM in 2022 after seeing how slow Multipass felt when launching more than one Linux VM, even though it is relatively l…
> We started SlicerVM .... Shame you did not mention once in your long post that you are based on Firecracker, because I'm sure I'm not the first who was about to post "why is this better than Firecracker". Also it is a shame you've adopted the subscription billing model instead of allowing people to buy perpetual licenses. I dislike the subscription model in a pure sense, but also I dislike the "but its 'only' $x a…
Creating a single VM, with vm within vm (performance hit would be negligible for the orchestration work of agents), and it might offer some alternatives without having to customize Proxmox as much?
I'm curious if there's more than one way to achieve this. Creating a single VM, with vm within vm (performance hit would be negligible for the orchestration work of agents), and it might offer some alternatives without having to customize Proxmox as much?
Just be careful with the virtualized file systems to not create write amplification issues.
Also replacing network access with af-vsock is actually interesting if you want to simplify bring-up. SSH does some magic with vsocks these days too.
< 300ms boot with HW isolation sounds very nice but the pve-daemon patching approach is risky and might break at every eye-blink.
anyway, the author posted the sources on github and got in touch with the proxmox people, maybe they want to absorb that into the product (which would be very very cool).
This is clever work, especially given that Proxmox is already a very viable VMware replacement and wasn’t originally designed around microVMs as the primary abstraction. I’m glad this is working well for you. We’ve been on a similar journey, but came at it from the opposite direction. We started SlicerVM in 2022 after seeing how slow Multipass felt when launching more than one Linux VM, even though it is relatively l…
> We started SlicerVM .... Shame you did not mention once in your long post that you are based on Firecracker, because I'm sure I'm not the first who was about to post "why is this better than Firecracker". Also it is a shame you've adopted the subscription billing model instead of allowing people to buy perpetual licenses. I dislike the subscription model in a pure sense, but also I dislike the "but its 'only' $x a…
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…
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...