Playbooks¶
These are the canonical VM troubleshooting playbooks. Use the root playbooks first when you need scenario-driven guidance for the most common production failures, then branch into the nested library for older or more specialized flows.
Diagnostic Entry Map¶
flowchart TD
A[VM incident] --> B{Primary symptom}
B --> C[VM Boot Failures]
B --> D[Disk Performance Issues]
B --> E[Network Connectivity Issues]
B --> F[RDP and SSH Connection Failures]
B --> G[Specialized legacy playbooks]Recommended First-Line Playbooks¶
| Playbook | When to use it |
|---|---|
| VM Boot Failures | The VM does not complete boot or never becomes remotely usable. |
| Disk Performance Issues | Latency, queue depth, or throughput bottlenecks affect the workload. |
| Network Connectivity Issues | East-west, north-south, or dependency traffic fails after network changes. |
| RDP and SSH Connection Failures | Administrative sign-in or Bastion-based access fails. |
| Boot Diagnostics and Serial Console | You need low-level evidence or recovery access after boot failure. |