On Mon, Oct 19, 2009 at 10:02 AM, Sebastian Reitenbach
wrote:
> Hi,
>
> I plan on updating heartbeat from heartbeat 2.1.X to now use pacemaker. I
> installed a test cluster. Further I want to use XEN VM live migration.
> Everything works fine so far, also the live migration, just one glitch I don'
Hi,
I plan on updating heartbeat from heartbeat 2.1.X to now use pacemaker. I
installed a test cluster. Further I want to use XEN VM live migration.
Everything works fine so far, also the live migration, just one glitch I don't
know where to fix.
When initiating a migration of a VM, then, on t
Try using a larger timeout value for the stop operation. I don't know if that
is intentional (and I'm still waiting for an answer about that ;-) ) but the
timeout value for migrate_from and/or migrate_to seems driven by the stop
timeout value.
Alain
Le 19 octobre 2009 11:41:09, Dejan Muhamedagi
Hi,
On Mon, Oct 19, 2009 at 10:45:19AM +0200, Sebastian Reitenbach wrote:
> Hi,
>
> I plan on updating heartbeat from heartbeat 2.1.X to now use pacemaker. I
> installed a test cluster. Further I want to use XEN VM live migration.
> Everything works fine so far, also the live migration, just on
Hi,
I plan on updating heartbeat from heartbeat 2.1.X to now use pacemaker. I
installed a test cluster. Further I want to use XEN VM live migration.
Everything works fine so far, also the live migration, just one glitch I don't
know where to fix.
When initiating a migration of a VM, then, on t
