Skip to content

Certification

This provider is certified: it passes every behavior in the BigFleet conformance program — the same bar every provider must clear — so you can trust it to create, configure, drain, and delete machines correctly under load, failure, and restart. You do not need to run anything here to use it in production; this page exists if you want to reproduce that verdict yourself.

“Certified” here means exactly what it means in the conformance program: the provider passes both the upstream authoritative baseline and this repo’s extension suite, with no failures and no skipped-as-failed behaviors.

One command

Terminal window
make certify-libvirt

That target (hack/run-certify.sh libvirt) is fully credential-free. It:

  1. Resolves the bigfleet checkout that owns the authoritative contract — reusing $BIGFLEET_SRC if set, otherwise cloning the exact version pinned in the provider’s go.mod into .cache/bigfleet-src.
  2. Builds ./bin/libvirt and boots it with --provider=certify --seed-count=256. It uses --use-fake-backend, so no hypervisor is touched — the extension suite consumes a fresh machine per behavior, hence the generous seed.
  3. Runs the upstream baseline (test/conformance/ in the bigfleet repo), then the extension suite (conformance/suite, build-tagged certify), both dialing that one endpoint.
  4. Prints CERTIFIED: libvirt passed the upstream baseline + the extension suite — or fails non-zero on the first failing behavior, tearing the provider down.

Override the port with PORT=....

Profiles the libvirt provider claims

The harness certifies a provider against the profiles it advertises; behaviors outside a claimed profile skip-as-pass.

  • core — every provider (lifecycle, errors, fencing, concurrency, metadata, field-shape, list, property).
  • cloud — implements Delete (Idle → Speculative). The default on_demand libvirt pool does (Delete = virDomainDestroy + virDomainUndefine + overlay delete is meaningful), so it claims cloud. If you run a fixed --capacity-type bare_metal pool instead, you claim bare-metal and Delete is never sent (M73).
  • spot — exposes SPOT capacity. Local KVM has no preemption market, so the provider does not claim spot; the SPOT-interruption_probability > 0 behaviors skip-as-pass. See Pricing & interruption for why a zero interruption probability is the correct value here.
  • fault / durable / scale — failure→FAILED, restart recovery, and scale lanes. These come from providerkit and pass by construction for any kit-based provider; run them through the report runner.

make certify-libvirt runs the credential-free core gate (baseline + the black-box extension). The complete certification — every applicable lane — runs through the bfconformance runner and emits a JUnit + JSON report with a verdict:

Terminal window
make report-libvirt PROFILE=core,cloud
# -> VERDICT: CERTIFIED, writes conformance-report/libvirt/{report.json,junit.xml}

Running the full multi-lane set confirms the kit-provided lanes pass too:

Terminal window
make report-libvirt PROFILE=core,cloud,fault,durable,scale
# behaviors: 93 total — 93 passed, 0 failed, 0 skipped, 0 not-implemented
# -> VERDICT: CERTIFIED

Certifying a real endpoint

make certify-libvirt certifies the fake backend in CI. To certify the provider talking to real libvirt, run it yourself against your hosts and point the extension suite at it:

Terminal window
# 1. Boot the provider against real libvirt (see Install & deploy / Configuration).
./bin/libvirt \
--addr 127.0.0.1:9099 \
--connect 'rack1=qemu+libssh://bigfleet@host-a/system?keyfile=./id_ed25519&known_hosts=./known_hosts&known_hosts_verify=normal' \
--image ubuntu-24.04.qcow2 \
--offerings ./offerings.json
# 2. In another shell, run the extension suite against that endpoint.
go -C conformance test -tags=certify -count=1 ./suite/... -target=127.0.0.1:9099

A real run exercises the full lifecycle — define + start → wait-running → guest-agent Configure/Drain → destroy + undefine — so the endpoint needs a reachable host (see Credentials) and a base image that runs qemu-guest-agent and ships the bootstrap hook. It will create and destroy real domains; certify against a throwaway host and clean up afterwards.

See also