On 09/28/2012 04:20 PM, Patrick Hurrelmann wrote:
On 28.09.2012 15:10, Itamar Heim wrote:
> On 09/28/2012 03:04 PM, Patrick Hurrelmann wrote:
>>>> Is there anything I can do to reset that stuck state and bring the VM
>>>> back to live?
>>>> Best regards
>>> try moving all vm's from that host (migrate them to the other hosts),
>>> then fence it (or shutdown manually and right click, confirm shutdown)
>>> to try and release the vm from it.
>> In the web interface it is shown with icon for stopped VMs and an empty
>> host, but status is showing "Not Responding". So the stuck VM is not
>> assigned to any host? All 3 hosts and the engine itself have already
>> been rebooted since the storage crash (The hosts one by one and going to
>> maintenance before).
> shortest solution is for you to change the status of the VM in the db to
> unlock it, but would be nice to try and understand why this specific vm
> got into this state to fix the bug.
yes, sure. If there is more information that I can provide to help,
please let me now. My setup is based on CentOS 6.3 using dreyou's repo.
On hosts: vdsm 4.10.0-0.42.13.el6
On engine: ovirt-engine 3.1.0-3.19.el6
please attach also vdsm log (from the host
running that orphan VM) and
the engine log