GitHub user prashanthr2 added a comment to the discussion: How is KVM HA
expected to work (HW without IPMI)
@zidz I agree with what @chunkyen is suggesting here. Based on what we see in
the logs ( snippet below). Cloudstack has detected the VM is not running and
has initiated HA worker threads as well. However the VM is not started else
where as the host is still running and reachable
2026-01-27 12:01:05,712 DEBUG [c.c.h.HighAvailabilityManagerExtImpl]
(HA-Worker-0:[ctx-837f2660, work-554]) (logid:8894ff2b) **_VM VM instance
{"id":215,"instanceName":"i-6-215-VM","state":"Running","type":"User","uuid":"16f60c4c-4cb5-46be-8ddc-62c774f3e502"}
is found to be alive by KVMInvestigator_**
2026-01-27 12:01:05,713 INFO [c.c.h.HighAvailabilityManagerExtImpl]
(HA-Worker-0:[ctx-837f2660, work-554]) (logid:8894ff2b) **_VM instance
{"id":215,"instanceName":"i-6-215-VM","state":"Running","type":"User","uuid":"16f60c4c-4cb5-46be-8ddc-62c774f3e502"}
is alive and host is up. No need to restart it._**
2026-01-27 23:02:53,845 DEBUG [c.c.h.HighAvailabilityManagerExtImpl]
(HA-Worker-3:[ctx-85d9be02, work-602]) (logid:f52990b8) VM VM instance
{"id":215,"instanceName":"i-6-215-VM","state":"Running","type":"User","uuid":"16f60c4c-4cb5-46be-8ddc-62c774f3e502"}
**is found to be alive by KVMInvestigator**
2026-01-27 23:02:53,845 INFO [c.c.h.HighAvailabilityManagerExtImpl]
(HA-Worker-3:[ctx-85d9be02, work-602]) (logid:f52990b8) VM instance
{"id":215,"instanceName":"i-6-215-VM","state":"Running","type":"User","uuid":"16f60c4c-4cb5-46be-8ddc-62c774f3e502"}
**is alive and host is up. No need to restart it.**
>From what I see in the code ( with my limited ability to read code and using
>gemini), the above lines indicate cloudstack assumes the VM to be up as the
>host is up and is writing its heartbeat to storage.
GitHub link:
https://github.com/apache/cloudstack/discussions/12528#discussioncomment-15641729
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
