Perfect, let’s definitely hang out then! I’ll dm you!
30.01.2026 16:37
👍 2
🔁 0
💬 0
📌 0
Perfect, let’s definitely hang out then! I’ll dm you!
Who’s going to FOSDEM in Brussels next week?
DM me if you'd like to hang out, talk about high performance cloud infrastructure, live migration, eBPF, Spot Instances - or all of the above!
Looking forward to meeting all the cool OSS folks!
Who’s going to re:invent in Las Vegas next week?
DM me if you'd like to hang out, talk about high performance cloud infrastructure, live migration, eBPF, Spot Instances - or all of the above!
Can’t wait to see everyone!
#aws #reinvent #reinvent2025
Nice that one can use network-bypass techniques without crazy vendor frameworks or kernel mods. Even cooler that one can recreate iptables functionality like this for faster inter-host networking
People aren’t ready for the next blog post from @loopholelabs.io
If you thought the XDP post was interesting (linked below) this next one is going to blow your mind.
Here’s a hint:
What do chess engines and NAT’s have in common?
Great post by @alex.sorlie.io
We finally decided to write out how we use XDP in our network plane for live network migrations and more specifically to process outgoing packets!
This is the first in a series of promised deep dives into how Loophole's live migration tech works!
🙋♂️
kccncna2025.sched.com/event/27Fd6/...
Who is coming to KubeCon NA 2025 in Atlanta?
Marked your account for priority!
We’re not just putting this together for CI, we’ll also be connecting it to a CLI so you can just throw your local environment into a cloud VM to run really quickly and be torn down!
RWX looks amazing! I wonder if there’s an opportunity for collaboration there…
I can’t wait to open source our filesystem this month, it’s ridiculous the kind of stuff we jammed into the Linux kernel
I'm getting more and more excited about drop-in, frictionless infrastructure. Lots going on in observability, containers, cloud compute, etc. eBPF is part of it, so is monkey patching. Some interesting ones: @loopholelabs.io, @polarsignals.com, junctionlabs.io ﹩, subtrace.dev ﹩
- How to run VMs anywhere (even without KVM support)
- How to do L3/4 Checksums in eBPF XDP hooks
- How to write an in-kernel filesystem (and why)
- Deduplicating memory between VMs
- Reverse Engineering the CUDA API
Request: Topics for the @loopholelabs.io Blog
I want to start posting some short-form blogs that go through the technical challenges of building @loopholelabs.io and how we’ve solved them.
If folks have requests for content they’d like covered now’s the time to ask!
Topics I have so far 👇
Just got to Malta for the company getaway! It’s really convenient that these EU outlets have a whole THREE USB-C outlets! So great.
boinc.berkeley.edu
You can volunteer your unused compute capacity towards research projects run by Berkeley For things like discovering pulsars, studying climate change, etc.
Donate to BOINC!
Yessir - the price to performance ratio alone makes them exciting but once you factor in power draw it becomes a no-brainer
If Asahi Linux ends up supporting M4 chips this year, I think adoption in datacenters will go through the roof
I think the most excited thing about this blog post is the one we get to publish next - a deep dive into how Architect works under the hood.
There were so many “impossible” problems we had to solve to make Architect a reality - and now that we have I’m having a blast explaining how we did it.
Here’s a demo of us migrating between spot instances across cloud providers all of which have different CPUs (generations, clock speeds, etc.)
loophole.sh/kc2024
Yep - and in those situations we can swap to a different instance type silently. We prefer that over a different region.
One of the more “impossible” problems we had to solve was migrating between different cpu types/generations seamlessly - that’s going to be the highlight of the next post.
So the nice thing about architect is that we can always fall back to on-demand instances if there’s no spot available - or we can switch to a different region, or if we’re really in a pinch we can swap to a completely different cloud provider.
Users can configure what level of fallback they want.
For sure - and we do recommend some level of overprovisioning to help against this, but because we run in your cloud account we generally only have to worry about the size of the individual customer’s workload on a per-region basis
@evanphx.dev this looks pretty cool loopholelabs.io/blog/rethink... built on OSS live migration tech that forked firecracker and related virtualization technology github.com/loopholelabs...
Your mental model is spot on (no pun intended)- though to make it work across spot instances and even cloud providers we had to go far beyond the capabilities of vmotion
This looks super cool. Get up to 75% cost-savings of using spot instances without data loss or interruption. My mental model of what this does is the equivalent of vSphere vMotion, but for spot instance workloads running in the Cloud.
