<div dir="ltr">Dear Milan,<div>Today, i just found that oVirt 4.2 support iLO5 and power management was set on all hosts (hypervisor).</div><div>I found that if i choose VM lease and shutdown iSCSI network, the VM was shutdown.</div><div>Then the VM will migrate to another host if the iSCSI network was resumed.</div><div><br></div><div>If i just choose enable HA on VM setting, the VM was successfully migrate to another hosts.</div><div><br></div><div>But i want to ask another question, what if the management network is down?</div><div>What VM and hosts behavior would you expect?</div><div><br></div><div>Regards</div><div>Terry Hung</div></div><div class="gmail_extra"><br><div class="gmail_quote">2018-02-28 22:29 GMT+08:00 Milan Zamazal <span dir="ltr"><<a href="mailto:mzamazal@redhat.com" target="_blank">mzamazal@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Terry hey <<a href="mailto:recreationh@gmail.com">recreationh@gmail.com</a>> writes:<br>
<br>
> I am testing iSCSI bonding failover test on oVirt, but i observed that VM<br>
> were paused and did not migrate to another host. Please see the details as<br>
> follows.<br>
><br>
> I have two hypervisors. Since they are running iLO 5 and oVirt 4.2 cannot<br>
> support iLO 5, thus i cannot setup power management.<br>
><br>
> For the cluster setting, I set "Migrate Virtual Machines" under the<br>
> Migration Policy.<br>
><br>
> For each hypervisor, I bonded two iSCSI interface as bond 1.<br>
><br>
> I created one Virtual machine and enable high availability on it.<br>
> Also, I created one Virtual machine and did not enable high availability on<br>
> it.<br>
><br>
> When i shutdown one of the iSCSI interface, nothing happened.<br>
> But when i shutdown both iSCSI interface, VM in that hosts were paused and<br>
> did not migrate to another hosts. Is this behavior normal or i miss<br>
> something?<br>
<br>
</span>A paused VM can't be migrated, since there are no guarantees about the<br>
storage state. As the VMs were paused under erroneous (rather than<br>
controlled such as putting the host into maintenance) situation,<br>
migration policy can't help here.<br>
<br>
But highly available VMs can be restarted on another host automatically.<br>
Do you have VM lease enabled for the highly available VM in High<br>
Availability settings? With a lease, Engine should be able to restart<br>
the VM elsewhere after a while, without it Engine can't do that since<br>
there is danger of resuming the VM on the original host, resulting in<br>
multiple instances of the same VM running at the same time.<br>
<br>
VMs without high availability must be restarted manually (unless storage<br>
domain becomes available again).<br>
<br>
HTH,<br>
Milan<br>
</blockquote></div><br></div>