Reading the assessment: ready, needs work, blocked

Every machine comes back as one of three things, sorted worst first because the worst ones are the ones you have to do something about.

Blocked means it cannot migrate as-is. Something has to change on the source first — a Raw Device Mapping with no target equivalent, a multi-writer VMDK that is the signature of a clustered pair, PCI passthrough, Fault Tolerance. A blocked machine is never scheduled into a wave and never written into a manifest, because a plan that looks complete and fails on the night is the exact failure this module exists to prevent.

Needs work means it will migrate, and will be wrong or fragile unless somebody acts. Missing VMware Tools, an outstanding snapshot, a guest past vendor support. These are scheduled — treating every warning as a blocker would empty any realistic plan — but somebody should look.

Ready means nothing was found.

The finding is not the point; the remediation is. Expand any machine's findings and each one tells you what to actually do about it, in the order you would do it. A finding that only said "this machine has an RDM" would move the problem from the tool back to you.

Assessment runs on the server, not in your browser. The support matrix moves when KubeVirt moves, so it lives in one place that can be corrected — rather than in a tab that keeps telling you a machine is fine for as long as you leave it open.