On Thu, Mar 03, 2011 at 05:16:06PM +0100, Gianluca Cecchi wrote: > Hello, > in stable 3 I can have this kind of config for a KVM virtual machine > to manage live migration: > > <rm> > <vm .....> > </rm> > > It works ok, but I would like to know the possible parameters I can set. > At http://sources.redhat.com/cluster/wiki/VirtualMachineBehaviors I > can see this piece > "..Most of the behaviors are common with normal services.." > with a reference to start, stop, status monitoring, relocation, recovery > > Where could I find a complete list? > For example are failover domains usable inside the line? > Or autostart option? I know how to manage autostart in a standalone > virt-manager environment, but when in a cluster of hosts? http://sources.redhat.com/cluster/wiki/ServiceOperationalBehaviors http://sources.redhat.com/cluster/wiki/ServicePolicies http://sources.redhat.com/cluster/wiki/FailoverDomains > Or dependency lines such as > > < vm name="vm1" ... > > <vm name="vm2" ... /> > </vm> If you add a child of a VM, you can no longer live-migrate it. > to power on vm2 only after power on of vm1? you can use 'depend=' if you want, but rgmanager's handling of this sort of dependency is rudimentary at best: <vm name="vm1" depend="vm:vm2" /> <vm name="vm2" /> Will work, but if you stop vm2, vm1 will be stopped after vm2. > About "transient domain support": > In the stable3 implementation of rhel6 (or in general in stable 3 if > it applies generally) a line such as this: > > <vm name="myvm" use_virsh="1" xmlfile="/etc/libvirt/qemu/myvm.xml"/> > > where /etc/libvirt/qemu/myvm.xm is not on a shared path, is it > supposed that if I have myvm on node 1 and run > clusvcadm -M vm:myvm -m node2 > > the file is deleted from node 1 and created in node 2 automatically or not? You need to have the description on each host in the cluster. -- Lon Hohberger - Red Hat, Inc. -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
