Skip to content

Native KVM Readiness

Readiness explains why a host cannot accept work. Diagnostics are read-only and never fabricate a live check.

What is checked

  • KVM present and accessible (/dev/kvm).
  • libvirt and QEMU availability.
  • CPU virtualization extensions enabled.
  • IOMMU status (for passthrough workloads).
  • Nested virtualization.
  • NUMA / hugepage capacity.
  • Assignable PCI devices.
  • Storage roots and free space.
  • Network interfaces.

Commands

pterocloud-agent diagnostics
pterocloud-agent verify

php artisan pterocloud:native:readiness
php artisan pterocloud:diagnose:hypervisor <uuid> --json

Interpreting readiness

  • A host that is not ready reports the exact reasons (missing component, disabled feature, no capacity).
  • An offline agent does not imply the host is down; diagnostics report the last-seen time and never fabricate a live check.
  • ProvisioningReady() is hard-wired false until live libvirt integration lands. A host can be enrolled and report capabilities while still not being provisioning-ready.