Hi, On Fri, Mar 19, 2010 at 12:53:50PM +0100, Alain.Moulle wrote: > Hi > No, I meant that after the virsh start vm , there is a while > (about 20s) where the vm is "starting" not started, then > there is a while (about 5 to 10 s) where the vm is started, responding > to a ping, but not "ssh-able" , and then I can definitively > connect via ssh to the vm to get status of inside services.
Then I also don't understand how comes that it didn't work. The start process is like this: 1. virsh start vm 2. loop until the monitor action succeeds (that includes your script) Thanks, Dejan > Alain > > It clears something up. > > You say "after the first ssh vm hostname is successful" > > > > You are at first able to ssh into vm, > > then later, you are (temporarily?) no longer able to do so? > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
