<p dir="ltr">Not able to access through console ,SSH, even the migration option is not getting highlighted unable to perform any actions.</p>
<p dir="ltr">To reboot host I need to migrate remaining vms to other host , that is time consuming.</p>
<p dir="ltr">Any commands to kill the process without rebooting the host?</p>
<div class="gmail_quote">On Apr 28, 2016 5:42 PM, "Michal Skrivanek" <<a href="mailto:michal.skrivanek@redhat.com">michal.skrivanek@redhat.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div class="quoted-text"><blockquote type="cite"><div>On 28 Apr 2016, at 14:11, Budur Nagaraju <<a href="mailto:nbudoor@gmail.com" target="_blank">nbudoor@gmail.com</a>> wrote:</div><br><div><p dir="ltr">Earlier it was working ,now not able to power on/off shutdown. deploy in another host etc.</p><div><br></div></div></blockquote><div><br></div></div>I don’t mean in ovirt, I mean the guest itself. Can you get to the console? Can you ssh to that guest? Does it do anythign?</div><div>if so it might be worth trying to save it (e.g. migrate), if not, just kill it from the host…or migrate everything else away and reboot the host</div><div class="elided-text"><div><br><blockquote type="cite"><div>
<div class="gmail_quote">On Apr 28, 2016 5:38 PM, "Michal Skrivanek" <<a href="mailto:michal.skrivanek@redhat.com" target="_blank">michal.skrivanek@redhat.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><blockquote type="cite"><div>On 28 Apr 2016, at 14:01, Budur Nagaraju <<a href="mailto:nbudoor@gmail.com" target="_blank">nbudoor@gmail.com</a>> wrote:</div><br><div><p dir="ltr">ovirt node is having 50vms and one VM is having issues, by restarting libvirt will the other vms get affect? And am not getting the option to delete.</p><div><br></div></div></blockquote><div><br></div>it will not affect the running VMs, they will keep running</div><div>again, does that one VM actually work?</div><div><br><blockquote type="cite"><div>
<div class="gmail_quote">On Apr 28, 2016 5:26 PM, "Michal Skrivanek" <<a href="mailto:michal.skrivanek@redhat.com" target="_blank">michal.skrivanek@redhat.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> On 28 Apr 2016, at 13:49, Budur Nagaraju <<a href="mailto:nbudoor@gmail.com" target="_blank">nbudoor@gmail.com</a>> wrote:<br>
><br>
> Any commands to check the same ?<br>
<br>
so does the VM actually work?<br>
what’s the status of the process?<br>
<br>
if it works, restart libvirtd (that will induce a vdsm restart as well), and check if it makes any difference. If not then I guess you’re out of luck and you can try to kill the qemu process yourself…or reboot the box<br>
<br>
> On Apr 28, 2016 5:10 PM, "Michal Skrivanek" <<a href="mailto:michal.skrivanek@redhat.com" target="_blank">michal.skrivanek@redhat.com</a>><br>
> wrote:<br>
><br>
>><br>
>>> On 28 Apr 2016, at 10:03, Budur Nagaraju <<a href="mailto:nbudoor@gmail.com" target="_blank">nbudoor@gmail.com</a>> wrote:<br>
>>><br>
>>> HI<br>
>>><br>
>>> One of the vm is showing "?" and unable to perform any actions below<br>
>> are the logs ,let me know is there any ways to bring it back ?<br>
>><br>
>> then it’s probably broken in lower layers. check/add vdsm.log from that<br>
>> period, but it is likely that libvirt lost control over the qemu process.<br>
>> You may want to check that particular qemu process if it is alright or .g<br>
<br>
</blockquote></div>
</div></blockquote></div><br></div></blockquote></div>
</div></blockquote></div><br></div></div></blockquote></div>