The feature that lets you create self-contained binaries seems like a potentially simpler way to package JVM apps than GraalVM Native. Probably a lot of other neat usecases for this, too smolvm pack create --image python:3.12-alpine -o ./python312 ./python312 run -- python3 --version # Python 3.12.x — isolated, no pyenv/venv/conda needed
Show HN: Smol machines – subsecond coldstart, portable virtual machines
71–80 of 162 posts
Re: Show HN: Smol machines – subsecond coldstart, portable virtual machines
#72Re: Show HN: Smol machines – subsecond coldstart, portable virtual machines
#73https://shellbox.dev is a hosted version of something very similar
So, if I use a "16 vCPUs, 32GB RAM, 400GB SSD" machine for a period of intense compute, and then want to scale that down to "2 vCPUs, 4GB RAM", most of my storage disappears?
That rather ruins the potential of the advertised scalability.
Re: Show HN: Smol machines – subsecond coldstart, portable virtual machines
#74Earlier quoted context omitted.
that was one of my inspirations but I don't think they went far enough in innovation. microvm space is still underserved.
> that was one of my inspirations Colins FreeBSD work or Emiles NetBSD work?
You'll see that philosophy in this project as well (i hope).
freeBSD focuses on features, which is great too.
Re: Show HN: Smol machines – subsecond coldstart, portable virtual machines
#75Re: Show HN: Smol machines – subsecond coldstart, portable virtual machines
#76Looks really nice btw. Hot resize mem/cpu would be nice. This could become a nice tech for a one-backend-per-customer infra orchestrator then.
Re: Show HN: Smol machines – subsecond coldstart, portable virtual machines
#77Earlier quoted context omitted.
Really appreciate the suggestion! By "live migration", do you mean keeping the existing files and migrate them elsewhere with the vm? Thanks
I mean making any given VM stop on host A and appear on host B; e.g. standard Qemu/KVM: virsh migrate --live GuestName DestinationURL This is feasible when network storage is available and useful when a host needs to be drained for maintenance.
Re: Show HN: Smol machines – subsecond coldstart, portable virtual machines
#78Hello, I'm building a replacement for docker containers with a virtual machine with the ergonomics of containers + subsecond start times. I worked in AWS previously in the container space + with firecracker. I realized the container is an unnecessary layer that slowed things down + firecracker was a technology designed for AWS org structure + usecase. So I ended up building a hybrid taking the best of containers with…
What percentage of this code was written by LLM/AI?
Re: Show HN: Smol machines – subsecond coldstart, portable virtual machines
#79Hello, I'm building a replacement for docker containers with a virtual machine with the ergonomics of containers + subsecond start times. I worked in AWS previously in the container space + with firecracker. I realized the container is an unnecessary layer that slowed things down + firecracker was a technology designed for AWS org structure + usecase. So I ended up building a hybrid taking the best of containers with…
Re: Show HN: Smol machines – subsecond coldstart, portable virtual machines
#80Hello, I'm building a replacement for docker containers with a virtual machine with the ergonomics of containers + subsecond start times. I worked in AWS previously in the container space + with firecracker. I realized the container is an unnecessary layer that slowed things down + firecracker was a technology designed for AWS org structure + usecase. So I ended up building a hybrid taking the best of containers with…
What were the biggest challenges in terms of designing the VM to have subsecond start times? And what are the current bottlenecks for deceasing the start time even further?
Linux was built in the 90s. Hardware improved more than a 1000x. Linux virtual machine startup times stayed relatively the same.
Turns out we kept adding junk to the linux kernel + bootup operations.
So all I did was cut and remove unnecessary parts until it still worked.
This ended up also getting boot up times to under 1s. The kernel changes are the 10 commits I made, you can verify here: https://github.com/smol-machines/libkrunfw
There's probably more fat to cut to be honest.