https://bugzilla.novell.com/show_bug.cgi?id=343603#c4 --- Comment #4 from Darren Thompson <darrent@akurit.com.au> 2007-11-27 12:14:51 MST --- Created an attachment (id=184941) --> (https://bugzilla.novell.com/attachment.cgi?id=184941) More info - Part II Quote:" On the edit step, change '(on_xend_start ignore)' to '(on_xend_start start)'" => I'll give that a try, thanks (Is it bad form to edit the config file in the XEND store directly?) Quote: "'xm start config' is really just launching the vm based on the config in /var/lib/xend/domains/<uuid>/config.sxp. The syntax for start is 'xm start <dom_name>'. Is the config file name same as vm name? If so, what you are really doing is starting vm <dom_name> using the config in /var/lib/xend/domains/<uuid>/config.sxp. You should be able to nuke your config file in /etc/xen/vm and the 'xm start config' command you are using will continue to work." => Oh... The config file is ALWAYS the same as the VM name so I had "assumed"... Thanks for that info - I now have a better understanding how this holds together. RE: Heartbeat, the available documentation does indicate a reliance on the "legacy" config files... http://www.novell.com/documentation/sles10/heartbeat/index.html?page=/docume... Similarly, the "normal" way to make XEN VM's available in a cluster environment was to create OCFS2 files mounts of /etc/xen/vm and /var/lib/xen/images which were then mounted via the HB2 cluster. If the /etc/xen/vm files are no longer to be used it does make clustering XEN VM' nerly impossible (There is no way that I know of to ensure both host servers are using exacly the same VM configurations). This is a well documented configuration: http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=... http://wiki.novell.com/images/3/37/Exploring_HASF.pdf http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=... This alone is a "show stopper" for the XEN and HB2 clustering. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.