11 a.m.
--Apple-Mail=_CB1BBFEC-A7A9-45F9-B3D1-80014558EFE2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
On 31 Mar 2016, at 19:48, Andrew Wippler =
<Andrew.Wippler(a)lancasterbaptist.org> wrote:
=20
Mark,
=20
Hopefully you have resolved your stuck VM issue by now (nearly two =
months later).
I came across this email from a google search. I was =
having the same exact problem with VMs being stuck in migration mode. =
The trigger to the VM migration issue was that I was setting my Host =
into maintenance mode. It migrated half of the active VMs successfully =
and the other half were stuck.
Hi,
It would be great to get logs from the system, or at least describe the =
specifics (anything special? gluster? old version?)
otherwise no one will ever be able to help;)
Thanks,
michal
=20
There were two things I had to do to fix all of my stuck VMs:
1. I shut down the host (long enough for oVirt to fence it and notice =
that it was
down). I then powered it on and "confirmed host as =
rebooted." This reset the active VM count on the host and turned on my =
HA VMs on other hosts.
2. For the one VM that was still stuck after a host reboot, I had to
=
login to postgres and set the status to 0 on that VM. This allowed me to =
shut down the migrating VM and start it back up. (I do not think I would =
have had to do this step if I did not alter the database entry for this =
VM before rebooting the host.)
=20
For step 2, I used the methods described here: =
https://access.redhat.com/discussions/688043 =
<https://access.redhat.com/discussions/688043> and as seen below:
ssh ovirt-engine
su postgres
psql
\connect engine
SELECT vm_guid status FROM vm_static WHERE vm_name=3D'XXXX';
UPDATE vm_dynamic SET status=3D0 WHERE vm_guid=3D'xxxxxxxx';
UPDATE vm_dynamic SET run_on_vds =3D null WHERE vm_guid=3D'xxxxxxxx';
\q
(I was then able to shut down the VM)
=20
--=20
Andrew Wippler <andrew.wippler(a)lancasterbaptist.org> =
<x-msg://533/andrew.wippler@lancasterbaptist.org%3E> | Sr. Systems =
Administrator | Lancaster Baptist Church
=20
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--Apple-Mail=_CB1BBFEC-A7A9-45F9-B3D1-80014558EFE2
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
charset=us-ascii
<html><head><meta http-equiv="Content-Type"
content="text/html charset=us-ascii"></head><body
style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break:
after-white-space;" class=""><br
class=""><div><blockquote type="cite"
class=""><div class="">On 31 Mar 2016, at 19:48, Andrew
Wippler <<a href="mailto:Andrew.Wippler@lancasterbaptist.org"
class="">Andrew.Wippler(a)lancasterbaptist.org</a>&gt;
wrote:</div><br class="Apple-interchange-newline"><div
class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"
class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break:
after-white-space;" class="">
<div class="">Mark,</div>
<div class=""><br class="">
</div>
<div class="">Hopefully you have resolved your stuck VM issue by now
(nearly two months later). I came across this email from a google search. I was having the
same exact problem with VMs being stuck in migration mode. The trigger to the VM migration
issue was that
I was setting my Host into maintenance mode. It migrated half of the active VMs
successfully and the other half were
stuck.</div></div></div></blockquote><div><br
class=""></div><div>Hi,</div>It would be great to get logs
from the system, or at least describe the specifics (anything special? gluster? old
version?)</div><div>otherwise no one will ever be able to
help;)</div><div><br
class=""></div><div>Thanks,</div><div>michal</div><div><br
class=""><blockquote type="cite" class=""><div
class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;" class="">
<div class=""><br class="">
</div>
<div class="">There were two things I had to do to fix all of my stuck
VMs:</div>
<div class="">1. I shut down the host (long enough for oVirt to fence it
and notice that it was down). I then powered it on and "confirmed host as
rebooted." This reset the active VM count on the host and turned on my HA VMs on
other hosts.</div>
<div class="">2. For the one VM that was still stuck after a host reboot,
I had to login to postgres and set the status to 0 on that VM. This allowed me to shut
down the migrating VM and start it back up. (I do not think I would have had to do this
step if I did not
alter the database entry for this VM before rebooting the host.)</div>
<div class=""><br class="">
</div>
<div class="">For step 2, I used the methods described
here: <a href="https://access.redhat.com/discussions/688043"
class="">https://access.redhat.com/discussions/688043</a&...
as seen below:</div>
<div class="">ssh ovirt-engine</div>
<div class="">su postgres</div>
<div class="">psql</div>
<div class="">\connect engine</div>
<div class="">SELECT vm_guid status FROM vm_static WHERE
vm_name='XXXX';</div>
<div class="">UPDATE vm_dynamic SET status=0 WHERE
vm_guid='xxxxxxxx';</div>
<div class="">UPDATE vm_dynamic SET run_on_vds = null WHERE
vm_guid='xxxxxxxx';</div>
<div class="">\q</div>
<div class="">(I was then able to shut down the VM)</div>
<div class=""><br class="">
</div>
<div class=""><span class="">-- <br
class="">
Andrew Wippler <<a
href="x-msg://533/andrew.wippler@lancasterbaptist.org%3E"
class="">andrew.wippler(a)lancasterbaptist.org&gt;</a>&nbsp;| Sr.
Systems Administrator | Lancaster Baptist Church</span></div>
<div class=""><br class="">
</div>
</div>
_______________________________________________<br class="">Users mailing
list<br class=""><a href="mailto:Users@ovirt.org"
class="">Users(a)ovirt.org</a><br
class="">http://lists.ovirt.org/mailman/listinfo/users<br
class=""></div></blockquote></div><br
class=""></body></html>
--Apple-Mail=_CB1BBFEC-A7A9-45F9-B3D1-80014558EFE2--