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


Re: [Xen-users] iscsi vs nfs for xen VMs

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-users] iscsi vs nfs for xen VMs
From: Bart Coninckx <bart.coninckx@xxxxxxxxxx>
Date: Sun, 30 Jan 2011 10:31:54 +0100
Cc: James Harper <james.harper@xxxxxxxxxxxxxxxx>, Christian Zoffoli <czoffoli@xxxxxxxxxxx>, Jia Rao <rickenrao@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 30 Jan 2011 01:33:03 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110129235010.GT2754@xxxxxxxxxxx>
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>
References: <20110129150142.GC2754@xxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01BB9317@trantor> <20110129234406.GS2754@xxxxxxxxxxx> <20110129235010.GT2754@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101125 SUSE/3.0.11 Thunderbird/3.0.11
On 01/30/11 00:50, Pasi Kärkkäinen wrote:
> On Sun, Jan 30, 2011 at 01:44:06AM +0200, Pasi Kärkkäinen wrote:
>> On Sun, Jan 30, 2011 at 10:41:23AM +1100, James Harper wrote:
>>>> On Wed, Jan 26, 2011 at 11:38:52AM +0100, Christian Zoffoli wrote:
>>>>> Hi,
>>>>> if you want to push on performance the best one is:
>>>>> CLVM over iSCSI
>>>> And if you need snapshots, just over normal LVM over shared iSCSI LUN.
>>>> (in this case your management toolstack needs to take care of locking LVM
>>>> control).
>>> How sure are you of this? Every write to the original or the snapshot 
>>> involves a potential metadata update. If the original is mounted on one 
>>> node and the snapshot on another, I'm pretty sure that it would all go to 
>>> crap really really quickly.
>>> Have you actually tried this???
>> It's widely used.
>> Citrix XenServer (and XCP) do it like that, and also the 
>> Xen based VirtualIron did it like that.
> Forgot to add this:
> In Citrix XenServer it's the XAPI toolstack that's 
> taking care of LVM locking, so only the "pool master" 
> is executing LVM commands.
> As long as you know you're executing LVM commands
> only from a single node, you're good. No need for CLVM.
> I guess you also need to refresh all the other nodes
> after executing LVM commands on the primary/master node.
> -- Pasi
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

I "fixed" this in a way I would like to have your idea on: what I did
was build the iSCSI LUNs on an IETD implementation. Each LUN points to a
LVM LV on this iSCSI server. To avoid worrying about which Hypervisor
will change the LUN, I save the DomU using the particular LUN over iSCSI
and then snapshot the LV on the iSCSI server. After I restore the guest
again and start dd-ing off the snapshot LV.



Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>