<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">All,<div><br></div><div>The documentation provided via the conga cluster recipe (<a href="http://sourceware.org/cluster/conga/cookbook/VMs_as_services">Add a virtual machine as a clustered service</a>) states that:</div><div><br></div><div>1) "Both xen config files [e.g. xend-config-sxp] and VM disk images must be located on shared storage, with identical mount paths for each node"</div><div><br></div><div>and then on the next slide states:</div><div><br></div><div>2) "Xend must be running on each node, and MUST BE STARTED BEFORE THE CMAN CLUSTER DAEMON"</div><div><br></div><div>However, it seems to me that this creates a chicken and egg problem. In particular if my xend-config.sxp is on a shared storage device (In my case a gfs2 formatted iSCSI disk) then doesn't that imply that I must have cluster services running to mount/access the filesystem. If that is the case then it is impossible for me to start xend before cman as my xend-config.sxp will not exist until cman starts and I mount my gfs2 partition.</div><div><br></div><div>The only other documentation I found for this setup: <a href="http://magazine.redhat.com/2007/08/23/automated-failover-and-recovery-of-virtualized-guests-in-advanced-platform/">http://magazine.redhat.com/2007/08/23/automated-failover-and-recovery-of-virtualized-guests-in-advanced-platform/</a> says absolutely nothing about system service startup order and includes an example of a cluster node reboot.</div><div><br></div><div>So, my question is this; is the default ordering of system service startup (cman < xend) workable with virtual machines defined as cluster services?</div><div><br></div><div>Thanks -- Aaron</div><div><br></div></body></html>