cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mohd Zainal Abidin Rabani" <>
Subject RE: HA Enabled ACS
Date Thu, 30 Jun 2016 06:53:21 GMT
Is this command to kill a process or what? Is it normal what a cloudstack management page show
some delay after vm start/stop?

-----Original Message-----
From: Nux! [] 
Sent: Thursday, June 30, 2016 12:52 AM
Subject: Re: HA Enabled ACS

+1 what Simon said.
To "kill" host A do a simple:
echo o > /proc/sysrq-trigger

This will properly simulate a "crash".

Sent from the Delta quadrant using Borg technology!


----- Original Message -----
> From: "Simon Weller" <>
> To:
> Sent: Wednesday, 29 June, 2016 13:02:29
> Subject: RE: HA Enabled ACS

> If the host agent shuts down gracefully, I don't believe HA will kick 
> in. In the management console, you'll see the host in state 
> disconnected. If you pull the power on your host, or cause it to 
> kernel panic, the state should be listed as down in the console. The state down should
trigger HA.
> Simon Weller/ENA
> (615) 312-6068
> -----Original Message-----
> From: Mohd Zainal Abidin Rabani []
> Received: Wednesday, 29 Jun 2016, 3:50AM
> To: []
> Subject: HA Enabled ACS
> Hi,
> I have create HA enables from service offering > Compute offering. I 
> install vm using iso. I have 2 host that running kvm and connect to 
> ACS. After install I check vm running on host A. So I shutdown host A. 
> I wait about 1o minute and vm still not up on host B. Storage using 
> ceph. Is it because of ceph or what? From the doc it said support 
> shared (NFS or iSCSI). I'm not sure it support ceph or not. Suppose to be support. Advice
> Thanks.

View raw message