Re: [ovirt-users] oVirt 3.5.2 Hypervisor crash, guest VMs not migrating

2015-04-17 Thread Patrick Russell
If you turn the host back on, do the VM then power up on the host that was 
never down?

If so, we have filed a bug around this in our 3.5.1 environment.

https://bugzilla.redhat.com/show_bug.cgi?id=1192596

-Patrick

 On Apr 16, 2015, at 7:01 PM, Ron V ronv...@abacom.com wrote:
 
 Hello,
 
 I am testing guest VM migration in the event of a host crash, and I am 
 surprised to see that guests that are selected to be highly available do not 
 migrate when a host is forcibly turned off.
 
 I have a 2 host cluster using iSCSI for storage, and when one of the hosts, 
 either the SPM or normal, is forcibly turned off, although the engine sees 
 the host as non-responsive, the VMs that were running on it remain on that 
 crashed host, and a question mark (?) appears next to them.  Other than 
 checking highly available, is there another step that needs to be made for 
 a VM to be restarted on a working host should the host it is running on fail?
 
 Thanks,
 
 R.
 
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt 3.5.2 Hypervisor crash, guest VMs not migrating

2015-04-17 Thread Ron V



On 4/17/2015 10:46 AM, Patrick Russell wrote:

If you turn the host back on, do the VM then power up on the host that was 
never down?

If so, we have filed a bug around this in our 3.5.1 environment.

https://bugzilla.redhat.com/show_bug.cgi?id=1192596

-Patrick



Hello,

yes this is exactly what happens.  The engine is reporting trying to 
fence the down host, and while the host is marked non-responsive. In my 
scenario I am testing by yanking the power on one of the hosts, and the 
idrac5 that is used to fence becomes unresponsive as well as a result, 
which might be a contributing factor.  In any case, VMs remain in a (?) 
state and so long as I don't click host has been manually rebooted) 
they don't come online elsewhere even after a few hours.



R.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt 3.5.2 Hypervisor crash, guest VMs not migrating

2015-04-16 Thread Ernest Beinrohr

Dňa 17.04.2015 o 02:01 Ron V napísal(a):

Hello,

I am testing guest VM migration in the event of a host crash, and I am 
surprised to see that guests that are selected to be highly available 
do not migrate when a host is forcibly turned off.


I have a 2 host cluster using iSCSI for storage, and when one of the 
hosts, either the SPM or normal, is forcibly turned off, although the 
engine sees the host as non-responsive, the VMs that were running on 
it remain on that crashed host, and a question mark (?) appears next 
to them.  Other than checking highly available, is there another 
step that needs to be made for a VM to be restarted on a working host 
should the host it is running on fail?


Migration does not work when the host crashes. If you have fencing 
enabled, the engine can restart the dead host and start the vms on 
another host. This works for us. But you have to have power management 
for the hosts.

--
Ernest Beinrohr, AXON PRO
Ing http://www.beinrohr.sk/ing.php, RHCE 
http://www.beinrohr.sk/rhce.php, RHCVA 
http://www.beinrohr.sk/rhce.php, LPIC 
http://www.beinrohr.sk/lpic.php, VCA http://www.beinrohr.sk/vca.php,

+421-2-62410360 +421-903-482603
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] oVirt 3.5.2 Hypervisor crash, guest VMs not migrating

2015-04-16 Thread Ron V

Hello,

I am testing guest VM migration in the event of a host crash, and I am 
surprised to see that guests that are selected to be highly available do 
not migrate when a host is forcibly turned off.


I have a 2 host cluster using iSCSI for storage, and when one of the 
hosts, either the SPM or normal, is forcibly turned off, although the 
engine sees the host as non-responsive, the VMs that were running on it 
remain on that crashed host, and a question mark (?) appears next to 
them.  Other than checking highly available, is there another step 
that needs to be made for a VM to be restarted on a working host should 
the host it is running on fail?


Thanks,

R.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users