EC2 Spot Instance & Xenbus Diagnostic Troubleshooter
Use the interactive troubleshooter below to identify your Spot Instance or Xenbus error by symptom, review the raw error log, understand the root cause, and apply the recommended fix.
🚨 Step 1: What specific error symptom are you experiencing?
Please click the most accurate description:
Quick Reference Table
| # | Scenario | Key Error Signal | Root Cause | The Fix |
|---|---|---|---|---|
| 1 | Spot Instance metadata interruption notice (stop) | {"action": "stop"} | Amazon EC2 is preparing to stop the Spot Instance because it needs the capacity back. | N/A |
| 2 | Spot Instance metadata interruption notice (terminate) | {"action": "terminate"} | Amazon EC2 is preparing to terminate the Spot Instance because it needs the capacity back. | N/A |
| 3 | Spot Instance legacy termination time notice | 2015-01-05T18:02:00Z | Amazon EC2 has marked the instance for termination and provided the approximate time the shutdown signal will be received. | N/A |
| 4 | Xenbus device driver missing causing root device mount failure | XENBUS: Device with no driver: device/vbd/2048 | The instance has a missing or incorrectly configured virtual block device driver, or a device enumeration clash. | N/A |
| 5 | Xenbus timeout connecting to devices during boot | XENBUS: Timeout connecting to devices! | The block device is not connected to the instance, or the instance is using an old instance kernel. | N/A |