xen-users

[Top] [All Lists]

[Xen-users] lock domU file backed vbd's?

from [Wayde Nie]

[Permanent Link][Original]

To:	Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-users] lock domU file backed vbd's?
From:	Wayde Nie <xen@xxxxxx>
Date:	Fri, 08 Aug 2008 18:00:15 -0400
Delivery-date:	Fri, 08 Aug 2008 14:53:49 -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

Hi Everyone,

Does anyone have suggestions on the best way to implement some sort of
interlock so that a VM with a file-backed vbd can only be started on one
node at any given time? I haven't had much luck with Google or the
archive searches so far...

Some background:

I've got a 2 node setup based on Debian Etch and the stock Debian Xen
3.0.3. Each node has local storage connected together in an
active-active drbd8 cluster with osfs2 and I'm using file backed vdb's
on the shared storage for my domU's.

I can start a domU on either node and live migration is working great.
Unfortunately, there doesn't appear to be any locking done on the file
backed vbd's which makes it a bit to easy to start a VM on both nodes at
the same time (trashing the disk file in the process...)

Any pointers would be appreciated!

Thanks,
Wayde.



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-users] lock domU file backed vbd's?, Wayde Nie <= RE: [Xen-users] lock domU file backed vbd's?, Dustin Henning Re: [Xen-users] lock domU file backed vbd's?, Todd Deshane

Previous by Date:	Re: [Xen-devel] Re: [Xen-users] svm.c:83:d917 Bad instruction length 0, Keir Fraser
Next by Date:	[Xen-users] Cannot assign device in Xen-unstable [VT-d], Bryan York
Previous by Thread:	[Xen-users] Adding a block device to a new Linux Guest, Omer Khalid
Next by Thread:	RE: [Xen-users] lock domU file backed vbd's?, Dustin Henning
Indexes:	[Date] [Thread] [Top] [All Lists]