@imil I patched Firecracker to use that CPUID leaf. I can't remember if that patch got merged though; at one point it was being held up because there was work in progress to change how Firecracker did it's CPU config stuff.

@emaste @david_chisnall @encthenet If you can provide scripts I'd be happy to run them on EC2 as part of my weekly snapshot regression testing. I think bofh is going to be giving me some scripts for testing build reproducibility soon too.

@david_chisnall @encthenet @emaste In fact the January 2024 regression is what prompted me to start collecting and graphing this data regularly. It took way too long for me to notice that issue.

@david_chisnall @encthenet @emaste The jump in January 2024 (main) and July 2024 (stable/14) was an EC2 issue related to the snapshot size; as you can see, now fixed. No idea what happened with stable/11 and I don't think it's worth investigating.

@encthenet Yeah I need to look up how to put text sideways in mpgraph.

@encthenet @emaste Looks like "-alpha remove" does what I wanted. This looks good with no bogus transparency right?

@emaste BTW the big improvement a few weeks ago was fixing the EFI RNG code -- arm64 was hanging waiting for entropy.

@encthenet @emaste Sorry, generated with metapost+latex and converted from PDF to PNG with imagemagick. Not sure what the magic is to remove transparency.

@emaste @ChuckMcManis @frameworkcomputer Now available, BTW.

@emaste @ChuckMcManis @frameworkcomputer Thursday around noon PDT. The builds start at midnight UTC.

@grahamperrin The snapshot build failed partway through, before it got to the point of staging the ftp bits.

@grahamperrin Sometimes builds break. That happened last week, and also this week for different reasons.

This is part of the reason why we do snapshots. ;-)

@josephholsten configinit is something I wrote for EC2 images because I wanted a light weight alternative to cloud unit (with e.g. no python). But if you're shipping images with cloud init I would recommend you keep doing that.

@tqbf No problem, just wanted to make sure; I had a temporary ENOSPC on my mail server.

@tqbf Just in case it got lost somewhere: I haven't seen an email from you yet.

@tqbf at FreeBSD.org or Tarsnap, they both end up in the same inbox.

@tqbf Sounds like we might need eBPF in FreeBSD then. I'm sure it's doable, just a bit more work.

If you want to send me an email with some details of what sort of eBPF code you're writing I might be able to think of other options though. Hard to say without knowing more.

@tqbf Would it help if you could write a FreeBSD kernel module in Rust? ;-)

@tqbf Does it need to be ebpf? It's your trusted code; why not just a kernel module?

@tqbf Agreed that the launcher code which sits inside the VM but outside of the container would need to be ported, but that might pay for itself by revealing bugs -- porting FreeBSD to Firecracker has certainly revealed plenty of Firecracker issues.