On 01/21/2013 03:03 PM, Itamar Heim wrote:
On 21/01/2013 03:35, Roy Golan wrote:
On 01/20/2013 07:25 PM, Jim Kinney wrote:
They are marked "highly available" but I thought that was for migration only. I saw a database boolean but other than an update command, I see no other way to boot on powerup.
your VMs probably failed to restart on your hosts. maybe storage isn't connected yet. check the engine.log
question is if engine should move VM to a status of "start pending resources" and try to run them again when a host becomes available. HighlyAvailableVmsDirector (intentionally unused in the code) will take care of that and now after Arik fixed the persisting of a VM.existStatus we should start using it.
On Jan 20, 2013 1:38 AM, "Roy Golan" <rgolan@redhat.com <mailto:rgolan@redhat.com>> wrote:
On 01/18/2013 08:27 PM, Jim Kinney wrote:
How do I mark a VM to startup if a node fails?
2 hosts in cluster, windows domain controller on one host, backup on second host. Both are marked high priority. "Bad Things" happen and both hosts get rebooted. I want those domain controllers to automatically restart.
are those VMs also marked as "Highly available" under High Availability tab?
I'm assuming the failure of the hosts did not knock down the manager. (I have them on separate floors, power, etc). -- -- James P. Kinney III //// ////Every time you stop a school, you will have to build a jail. What you gain at one end you lose at the other. It's like feeding a dog on his own tail. It won't fatten the dog. - Speech 11/23/1900 Mark Twain //// http://electjimkinney.org http://heretothereideas.blogspot.com/ ////
_______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users