GitHub user zidz edited a discussion: How is KVM HA expected to work (HW without IPMI)
I do not know if I have unrealistic expectations of Cloudstack 4.22 in regards to KVM HA. I'm running Cloudstack on hardware with no IPMI and expect some failover when a KVM instance is manually stopped on the host, is unexpectedly killed or dies. Cloudstack lists the VM as running and nothing happens, the VM will not be restarted to any extent. What I expect is that the VM should be detected as not running when it's expected to and should be restarted, preferably on another host. Note that I've waited over an hour to give all checks time to trigger a restart of a killed VM. The current setup is running on NFS for primary and secondary right now. I expect the next cluster to have its primary on Ceph RBD and secondary on NFS hosted by Ceph. I've read the HA documentation and I've deactivated all Host HA, as this else will be taken into account before handling the KVM HA (As far as I understand). Checked that the files in the KVMHA are updated with timestamps correctly. NTP is running correctly. All VM's to have HA activated in their offerings, I even forced HA for VM's in the Global configuration. Please tell me how KVM HA is intended to work, if my expectations are off and I would be super grateful for KVM HA test examples I can do to trigger the KVM HA functionality to get the correct expectations of the KVM HA functionality. I've read earlier discussions here in the Q&A section and other sources to try to solve this HA puzzle, but now I'm here asking for assistance.. GitHub link: https://github.com/apache/cloudstack/discussions/12528 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
