12:01 p.m.
If you are sure that the host (node) running the vm has reset, and the vm is no longer
running on that host you can select the host and manually "Confirm host has been
rebooted" (from the webadmin, not sure exactly how to do it from ovirt-shell).
Gadi Ickowicz
----- Original Message -----
From: "Simon Barrett" <Simon.Barrett(a)tradingscreen.com>
To: "Omer Frenkel" <ofrenkel(a)redhat.com>, "Meital Bourvine"
<mbourvin(a)redhat.com>
Cc: users(a)ovirt.org
Sent: Wednesday, March 26, 2014 10:44:15 AM
Subject: Re: [Users] VM Status "Unknown"
Was this ever resolved? I have a similar situation where a node was reset while a VM was
running on it. Now the VM is in an unknown state and I cannot stop/start etc. I also
cannot put the node into maintenance mode as it thinks it still has running VM’s
[oVirt shell (connected)]# list vms --query
"id=807593a5-8667-4265-a0ab-b3e37feb1fc1" --show-all | grep status
status-state : unknown
[oVirt shell (connected)]# action vm 807593a5-8667-4265-a0ab-b3e37feb1fc1 stop
============================ ERROR ====================================
status: 409
reason: Conflict
detail: Cannot stop VM. VM is not running.
=======================================================================
[oVirt shell (connected)]# action host d3a555b1-b5dd-48d1-802c-03096bdf8b00 deactivate
============================ ERROR ====================================
status: 409
reason: Conflict
detail: Cannot switch Host to Maintenance mode.
Host still has running VMs on it and is in Non Responsive state.
=======================================================================
Thanks,
From: users-bounces(a)ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Omer Frenkel
Sent: 12 January 2014 08:47
To: Meital Bourvine
Cc: users(a)ovirt.org
Subject: Re: [Users] VM Status "Unknown"
From: "Meital Bourvine" < mbourvin(a)redhat.com >
To: "Ryan Womer" < Ryan.Womer(a)cytechservices.com >
Cc: users(a)ovirt.org
Sent: Friday, January 10, 2014 11:54:51 AM
Subject: Re: [Users] VM Status "Unknown"
Can you please provide vdsm.log (of both hosts) and engine.log?
also, what version are you using?
we had some bugs around this solved for 3.3
From: "Ryan Womer" < Ryan.Womer(a)cytechservices.com >
To: users(a)ovirt.org
Sent: Thursday, January 9, 2014 10:43:37 PM
Subject: [Users] VM Status "Unknown"
During a migration, the destination host lost connectivity to the san and crashed.
Once the server came back up, 3 VMs that didn’t finish migrating have been stuck in status
“Unknown.” Vdsclient doesn’t list any of the vms on either host. Qemu doesn’t have them
listed as mounted on either host. Action vm start and stop result in “Status: 409”.
The disks for all 3 VMs are listed as green in the WebAdmin. I’ve tried “action vm
<name> start” “action vm <name> stop” “update vm <name> --status-state
down” no joy. They remain in “unknown.”
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users