This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Keeping domU configs sync'ed across nodes in a cluster

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Keeping domU configs sync'ed across nodes in a cluster
From: Digimer <linux@xxxxxxxxxxx>
Date: Tue, 19 Oct 2010 23:30:01 -0400
Delivery-date: Tue, 19 Oct 2010 20:31:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100922 Thunderbird/3.1.4
Hi all,

  I've got a Fedora 13 cluster (just two nodes) with Xen 4.0.1 and the
dom0's are 2.6.32 kernel. I can live migrate the domU VMs back and forth
just fine.

  The trick is that, until a VM has been migrated to the second node (or
I run 'virsh dumpxml domain > domain.xml; <copy to other node>; virsh
define domain.xml), the second node doesn't know that the domU exists.
So if the original node dies, I can't (easily) recover the domU on the
backup. Also, if I make changes to the virtual hardware on one node, the
other node's config goes stale.

  Is there a way to keep the domU configuration in sync across nodes? I
think I saw something to this effect a little earlier, but so far my
google-fu has not turned up anything.



Xen-users mailing list