Firecracker is pretty great, good to see it can be used in a CI environment like this, definitely peaking my interest.
I know its the backbone of what runs fly.io[0] as well
I know its the backbone of what runs fly.io[0] as well
https://aws.amazon.com/blogs/aws/firecracker-lightweight-vir...
There's also similar microVM project with a bit more container-focused support called Kata
I'm assuming that Firecracker is somewhat constrained in some way.
Or they could do what QEMU has done and put out a separate product/mode: https://github.com/qemu/qemu/blob/a082fab9d25/docs/system/i3...
> The recommended way to trigger a guest-initiated shut down is by generating a triple-fault, which will cause the VM to initiate a reboot
Doesn’t that mean it can’t distinguish an intentional triple fault to trigger reboot from an accidental triple fault caused by a guest kernel bug which corrupts the IDT? I think it would be better if there was some kind of call the guest could make to the hypervisor to reboot-one is less likely to invoke that service by accident than to triple fault by accident.