On Tue, Oct 9, 2012 at 3:49 PM, Itamar Heim <span dir="ltr"><<a href="mailto:iheim@redhat.com" target="_blank">iheim@redhat.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 10/09/2012 09:23 PM, Alan Johnson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Anyway, is there anyway to convince the engine that a VM is down so I<br>
can bring it back up again, like with "Confirm 'host has been rebooted'"<br>
on hosts?<br>
<br>
</blockquote>
<br></div>
which hosts are they supposedly on?<br></blockquote><div><br></div><div>The host column is blank for these VMs. Also, running `virsh --readonly list` on the remaining hosts matches the VMs oVirt shows as running and does not list the "Unknown" VMs on either host.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
does 'confirm host shutdown' on the host not release them?<br>
</blockquote></div><div><br></div>It did not. I also removed the host since I will need to add it back in after re-installing the OS on a more stable boot drive. Still no change. <div><br></div><div>You have me thinking... perhaps oVirt thinks they are running on the host they were being migrated to. If so, maybe putting that host into maintenance will clear it up. I'll try that as soon as I get the down host back up.<div>
<br></div></div>