https://bugzilla.novell.com/show_bug.cgi?id=343603#c5 --- Comment #5 from James Fehlig <jfehlig@novell.com> 2007-11-28 11:04:56 MST --- (In reply to comment #4 from Darren Thompson)
=> I'll give that a try, thanks (Is it bad form to edit the config file in the XEND store directly?)
Yes. When xend starts it reads all the config under /var/lib/xend/domains and keeps it in memory. When config is changed (via various interfaces into xend), the memory is updated as well as changes flushed to corresponding config file. Fi changes are made to the config file directly, they won't be reflected in memory - unless xend is restarted.
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=feature-18124html&sliceId=&dialogID=51787062&stateId=0%200%2051785718 http://wiki.novell.com/images/3/37/Exploring_HASF.pdf http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=feature-19676html&sliceId=&dialogID=51787062&stateId=0%200%2051785718
This alone is a "show stopper" for the XEN and HB2 clustering.
Right, which is why I have not closed this bug. Of all the items discussed in this report, the HB problem is certainly an issue. Investigation of possible solutions added to my todo list. -- 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.