[Pacemaker] Migrating VMs that depend on other VMs

Lars Marowsky-Bree lmb at suse.com
Wed May 15 11:10:34 EDT 2013

On 2013-05-15T09:32:25, Lindsay Todd <rltodd.ml1 at gmail.com> wrote:

> In my testing, I reappropriated two VMs, just to make sure I
> understood the constraints on VM migrations:
> primitive vm-compute-test ocf:ccni:xcatVirtualDomain \
> primitive vm-swbuildsl6 ocf:ccni:xcatVirtualDomain \
> order o-vm-swbuildsl6-after-compute-test inf: vm-compute-test vm-swbuildsl6
> order o-vm-compute-test inf: c-p-libvirtd vm-compute-test
> order o-vm-swbuildsl6 inf: c-p-libvirtd vm-swbuildsl6
> So it is just an ordering dependency.  I can freely migrate
> vm-compute-test, although it induces a stop/start on vm-swbuildsl6.
> Attempts to migrate vm-swbuildsl6 are always done as stop/start.  This
> doesn't make sense to me, but is what the documentation describes.

I think that is an avoidable deficiency. Can you open a bug report with
a hb_report attached?


Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

More information about the Pacemaker mailing list