Re:So you think you want to write a deterministic hypervisor?
by bobafett-9902 on Friday March 22, 2024 @12:40AM
(#39787530)
I believe they have a discord for asking questions directly to their engineers https://discord.gg/75cBWkbC
Re:So you think you want to write a deterministic hypervisor?
by fuzzybear3965 on Friday March 22, 2024 @06:00PM
(#39795316)
Thanks!
Re:So you think you want to write a deterministic hypervisor?
by yencabulator on Monday March 25, 2024 @04:10PM
(#39820740)
The relevant part is
> The Antithesis environment simulates one or more computers using a collection of containers, all running within a single virtual machine managed by our hypervisor.
No mocking needed, but everything needs to share the single VM.
And it sure sounds like they run a custom kernel in the guest, so this is not for kernelspace testing:
> Since the Antithesis platform controls the guest’s scheduler,
We currently run CI tests using QEMU VMs. These VMs comprise a few systems representative of those that we deploy to production.
Does adopting Antithesis mean that all non-containerized applications would need to be OCI-ified and every interaction would need to be mocked? There's a sort of combinatorial explosion that I'm concerned about when I'm thinking about testing/adding a new service to a system: All services on which it depends need to be mocked and all services which depend on it require creating a mocked version of it.
Seems like a lot of work. Can someone please help clarify things for me?
Also, how could we test the behavior of non-application code like drivers or the kernel itself?