----- Original Message ----- > From: "Simon Barrett" <[email protected]> > To: "Omer Frenkel" <[email protected]>, "Meital Bourvine" > <[email protected]> > Cc: [email protected] > 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, your host in non-responsive, means the engine cant verify its status and the vms status on it. if you dont have power management (i guess you dont) and you absolutely sure the vms are really not running there anymore you can mark the host as been rebooted, and clear the its state. in the UI - right click the host and choose "confirm rebooted" in rest i think its called manual fence > From: [email protected] [mailto:[email protected]] On Behalf Of > Omer Frenkel > Sent: 12 January 2014 08:47 > To: Meital Bourvine > Cc: [email protected] > Subject: Re: [Users] VM Status "Unknown" > ----- Original Message ----- > > From: "Meital Bourvine" < [email protected] > > > > To: "Ryan Womer" < [email protected] > > > > Cc: [email protected] > > > 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 > > ----- Original Message ----- > > > > From: "Ryan Womer" < [email protected] > > > > > > > To: [email protected] > > > > > > 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 > > > > > > [email protected] > > > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > _______________________________________________ > > > Users mailing list > > > [email protected] > > > http://lists.ovirt.org/mailman/listinfo/users >
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
