- 已装运
- 2026年9月23日 18:18 UTC
- 作者
- Kamo
- 提交
- d5c3c8d
WAKE_TIMEOUT_MS was 180_000 and sat exactly on top of the VM's readiness probe, whose initialDelaySeconds was 180 and which KubeVirt renders as 190. A computer is only reachable once its Service has endpoints, and that happens when the probe first passes — so the tab gave up BEFORE the guest had been probed even once. Every wake. The member closed the tab, clicked again, and it worked, because by then the endpoints existed. Two numbers chosen independently, each defensible on its own, and together they made waking impossible. The probe now starts at 15s (vm-template.yaml); this is five minutes so that a slow EXTREME resume has room rather than sitting one boundary away from the thing it is waiting for.