Hi, > Hmm, stop used to be xm shutdown -w > (at least as coded originally... > then Xen 3.2 added its registration ideas; > and I guess various changes have been made; > so that e.g. if Heartbeat is managing the > Xen VM; it's defined also via xm new, since we > wanted the VM to also be visible to other tools > that depend on registration - e.g. virtman...)
Excuse me for a bit of an irrelevant hijack but why is this fuzz about xenstore or I just missed something? (xm new, xenstore sync, etc) Xenstore is not necessary for HA managed VMs is it? We need few lines of config to start, stop, monitor, migrate the VM resources by HA, this is it. Once the VM is HA managed no traditional management tool should be used for VMs like xm and virtman or HA gets confused. Currently I deleted all my VMs from xenstore, when all shut down virtman shows nothing. When xm create <> starts a resource virtman will display the running VM so if you need the GUI graphs, etc you can still have it but nobody should manage the VM (start/stop, etc) without notifying HA so monitoring is the only thing it's useful for. Perhaps that's the basic usage and something just cannot be stored in xm config files. If so what is it? Thanks, Ivan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
