<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Jul 10, 2017 at 4:45 PM, Martin Sivak <span dir="ltr"><<a href="mailto:msivak@redhat.com" target="_blank">msivak@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> In the 'hosted-engine' script itself, in the function cmd_vm_start,<br>
> there is a comment:<br>
> # TODO: Check first the sanlock status, and if allows:<br>
><br>
> Perhaps ha-agent checks sanlock status before starting the VM?<br>
> Adding Martin.<br>
<br>
</span>QEMU does that by itself. It starts, asks for a lease and dies if it<br>
can't get it.<br>
<br>
So:<br>
<span class=""><br>
>>> I see that the qemu-kvm process for the engine starts on two hosts and<br>
>>> then on one of them it gets a "kill -15" and stops<br>
>>> Is it expected behaviour?<br>
<br>
</span>This is how it should behave, unless the reason for it is something else.<br>
<span class="HOEnZb"><font color="#888888"><br>
Martin<br>
</font></span><div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>Ok. </div><div>My question was: no operating system is loaded at all before getting the lease, so that don't have any risk of corruption?</div><div>It seems so and that only the qemu process is started...</div><div>Thanks</div><div>Gianluca </div></div></div></div>