[ovirt-users] VM paused rather than migrate to another hosts

[Milan Zamazal]

Terry hey <recreationh at gmail.com> writes:

> I am testing iSCSI bonding failover test on oVirt, but i observed that VM
> were paused and did not migrate to another host. Please see the details as
> follows.
>
> I have two hypervisors. Since they are running iLO 5 and oVirt 4.2 cannot
> support iLO 5, thus i cannot setup power management.
>
> For the cluster setting, I set "Migrate Virtual Machines" under the
> Migration Policy.
>
> For each hypervisor, I bonded two iSCSI interface as bond 1.
>
> I created one Virtual machine and enable high availability on it.
> Also, I created one Virtual machine and did not enable high availability on
> it.
>
> When i shutdown one of the iSCSI interface, nothing happened.
> But when i shutdown both iSCSI interface, VM in that hosts were paused and
> did not migrate to another hosts. Is this behavior normal or i miss
> something?

A paused VM can't be migrated, since there are no guarantees about the
storage state.  As the VMs were paused under erroneous (rather than
controlled such as putting the host into maintenance) situation,
migration policy can't help here.

But highly available VMs can be restarted on another host automatically.
Do you have VM lease enabled for the highly available VM in High
Availability settings?  With a lease, Engine should be able to restart
the VM elsewhere after a while, without it Engine can't do that since
there is danger of resuming the VM on the original host, resulting in
multiple instances of the same VM running at the same time.

VMs without high availability must be restarted manually (unless storage
domain becomes available again).

HTH,
Milan