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] Guarding against starting same vm on multiple nodes?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Guarding against starting same vm on multiple nodes?
From: Wayde Nie <xen@xxxxxx>
Date: Thu, 05 Feb 2009 00:44:02 -0500
Cc: xen@xxxxxx
Delivery-date: Wed, 04 Feb 2009 21:45:33 -0800
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>
Reply-to: xen@xxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi Everyone,

How do people running multinode xen dom0 clusters, with shared storage
for the domU images ensure that vm's aren't started on more than one
node at a time?

I can't seem to find much info about it through web searches. I asked
the question on this list a few months back and the following thread was
brought to my attention:


The thread fizzled out pretty early but there was a suggestion that vdb
locks belong in higher level management tools, rather than xend... Would
that include tools like xm? Are there other tools that can take care of
management of vms across multiple nodes and protect against disk
corruption caused by starting the same vm multiple times? 


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Guarding against starting same vm on multiple nodes?, Wayde Nie <=