Skip to content

Guest Control Fabric

hypersdk edited this page Aug 7, 2026 · 1 revision

Guest Control Fabric

Zyvor does not require guest networking for VM intelligence. The API picks the best transport per VM and per operation.

Deep docs: guest-control-fabric.md.

Transport ladder

Tier Transport When
1 virtio-serial Zyvor agent + QGA channel
2 qga-exec QGA → guest-exec → agent JSON-RPC
3 qga-builtin guest-ping, guest-file-*, freeze/thaw
4 in-guest-socket Local agent socket via QGA exec
5 https-push Push report / HTTP agent proxy
6 offline-disk Halted VM → GuestKit on root PVC
7 console-only Running, no QGA — structured error

Each pull records attempts: [{ tier, ok, latencyMs, error }] for Agent Doctor.

Control states (UI)

State Meaning
full_agent Agent with network or push
airgap_live Agent + QGA, no guest network
qga_only QGA up, Zyvor agent missing
disk_only Stopped VM — offline repair
console_only Running, no QGA
blind_vm No live or offline path

Capability contract

GET /api/v1/kubevirt/vms/{ns}/{name}/guest/capabilitiestransport, controlState, capabilities.supports (evidence / exec / freeze / pushTelemetry), warnings + recommended actions.

Related

Assurance: Home · Cutover · Day-0 · Passport · Packages · Env

CLI: Commands · Interactive · Explore · TUI

Platform: Web · Zeus · KubeVirt · GCF · Agent

More: Demos · FAQ · Docs · Blog Posts

Clone this wiki locally