Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
slpnix
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
Show HN: KrunAI – A CLI tool for running AI agents inside microVM sandboxes
(github.com)
1 points
by
slpnix
7mo ago
|
0 comments
2.
▲
by
slpnix
2y ago
Podman supports this since quite a while with the krun variant of the crun runtime ( https://github.com/containers/crun/blob/main/krun.1 ), provided in Fedora by the "crun-krun" package. Just add
3.
▲
Show HN: Enabling containers to access the GPU on macOS
(sinrega.org)
2 points
by
slpnix
3y ago
|
0 comments
4.
▲
Finding a Wasm Runtime Unikernel for Libkrun
(slp.prose.sh)
3 points
by
slpnix
4y ago
|
0 comments
5.
▲
Running Linux MicroVMs on macOS (M1/M2)
(slp.prose.sh)
29 points
by
slpnix
4y ago
|
2 comments
6.
▲
by
slpnix
5y ago
Behind the scenes, it's using QEMU with Alex Graf's patches for hvf (Hypervisor.framework) support, so it's Virtualization, not emulation. In other words, the performance is really good ;-) BTW, in case you don't want to
7.
▲
by
slpnix
6y ago
I can't comment on the comparison with Docker for Mac bacause, honestly, I have never used it. With krunvm, each session initiated with "krunvm start" is an independent lightweight VM. The maximum amount of RAM the VM can use
8.
▲
by
slpnix
6y ago
The key is that libkrun ( https://github.com/containers/libkrun ), the library that krunvm uses for running the VMs, as recently integrated support for Hypervisor.framework on ARM64, in addition to KVM. As for buildah, t
9.
▲
by
slpnix
6y ago
krunvm uses libkrun ( https://github.com/containers/libkrun ) for executing the VM, and while the later is also based in rust-vmm and shares some code with Firecracker and Cloud-Hypervisor, it's specialized in the p
10.
▲
Show HN: krunvm – Create and run lightweight VMs from OCI images
(github.com)
82 points
by
slpnix
6y ago
|
8 comments
11.
▲
by
slpnix
7y ago
I think the slide 14 from the talk "Reports of my Bloat Have Been Greatly Exaggerated" [1] presented by Paolo Bonzini at KVM Forum 2019 gives some good perspective about QEMU's security track: "Of the top 100 vulnerabili
12.
▲
by
slpnix
7y ago
That's correct. The initial versions of the microvm patch series did require KVM, but the one that got upstreamed does work with TCG [1], thanks to the QEMU's maintainers feedback. That said, I'm not sure for which kind of us
13.
▲
by
slpnix
7y ago
From the guest perspective, the differences are minimal. Even boot time of the guest (thinking about a custom-built minimalist Linux kernel here) is roughly the same. On the host side, things are more interesting. Firecraker has a smaller T
14.
▲
Show HN: microvm – a minimalist machine type for QEMU inspired by Firecracker
(github.com)
145 points
by
slpnix
7y ago
|
20 comments
15.
▲
Show HN: Flatkvm – A tool to easily run Flatpak apps isolated with QEMU/KVM
(github.com)
3 points
by
slpnix
8y ago
|
0 comments