arcbox-vm-driver 0.8.0

The VM driver port: the vocabulary of a VM on this host — spec, driver/handle traits, capabilities, guest-network port — that VMM adapters implement and orchestrators consume.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36

//! Fakes and the contract test-kit (feature `testkit`).
//!
//! - [`FakeDriver`] — an in-memory [`VmDriver`](crate::VmDriver) with a
//!   real state machine, events, every capability, and scripted failures.
//!   Runtime unit tests drive their real actors and state machines against
//!   it on any host, no KVM required.
//!
//! - [`FakeNetwork`] — an in-memory [`GuestNetwork`](crate::net::GuestNetwork)
//!   handing out `10.200.0.0/16` leases with a quarantine ledger and the
//!   [`NetworkReconcile`](crate::net::NetworkReconcile) token protocol.
//!
//! - [`contract`] — the checks every adapter must pass, packaged as the
//!   [`driver_contract!`](crate::driver_contract) macro over a
//!   [`ContractHarness`]; the fake passes them too (`tests/fake_contract.rs`).

use std::sync::{Mutex, MutexGuard, PoisonError};

pub mod contract;
pub mod fake_driver;
pub mod fake_network;
mod fake_prepared;
mod fake_staging;
mod fake_vm;
mod fake_vsock;

pub use contract::{ContractHarness, FakeHarness};
pub use fake_driver::{FakeDriver, FakeDriverBuilder};
pub use fake_network::FakeNetwork;
pub use fake_vm::{CHECKPOINT_FORMAT, FakeVm};

/// Locks `mutex`, tolerating poison: a fake that panicked while holding a
/// lock has already failed the test, and the state behind it is still the
/// most useful thing to show.
pub(crate) fn lock<T>(mutex: &Mutex<T>) -> MutexGuard<'_, T> {
    mutex.lock().unwrap_or_else(PoisonError::into_inner)
}