On Wed, 2009-11-11 at 16:33 -0700, Aaron Benner wrote: > Final follow up here for the archives. I managed to clear the services in the locked state by: > > 1) remove the virtual machine service definition from the cluster configuration. > 2) stop the virtual machine using 'xm shutdown domU'. > 3) re-creae the virtual machine service definition which will appear in the stopped state frozen. > 4) unfreeze the virtual machine service. > 5) start the virtual machine service. > > This allowed me to clear the freeze without restarting the cluster entirely which was what I needed to accomplish. This problem won't exhibit itself in 3.0.5. The 'migrating' state is no longer needed. Either migration will work or it won't; no more half-migrations or wedged 'migrating' states. There are still a couple of bits to clean up around error checking when migrations fail; whether this makes 3.0.5 I can't say for sure. -- Lon -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
