https://bugzilla.novell.com/show_bug.cgi?id=343603 Summary: XEN config files not kept in sync with virtmanager files, affects heartbeat cluster, autostart and XM command line tools Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: SLES 10 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: darrent@akurit.com.au QAContact: qa@suse.de Found By: Third Party Developer/Partner Is it possible that you could circulate this around your team to see if anyone has a decent work-around/solution to this very annoying XEN/Virt-manager issue? In summary: I have noted that the VM configuration files created/updated by virt-manager are stored in /var/lib/xend/domains in uniquely identified folders (it's the UID of the VM) and in different format the the default XEN VM config file format. I also not that all of the command line XM tools, autostart , and heartbeat are all dependant on the text based config files stored in /etc/xen/vm. They are not kept in sync so any changes to the VM config using Virt-manager risks compromising the VM if used in heartbeat, autoload etc. It's a potential issue as the only way the "end customer" can configure new VM' is by virt-manager, yet I have to discourage them from ever using the tool again once the VM is created.... (seems very poor design to have such disconnected tools managing the same resource). Have you found a good way to keep these separate and disjointed configuration repositories in sync with each other???? I've become a bit of an expert at reading the Virt-manager files and hand crafting matching XEN config files, but it's a real pain to have to keep doing so.. Is there a new version of XEN/Virtmanager that does a better job of keeping these in sync or a tools available that can process one or the other of the config files to keep them in sync? -- 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.