[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Xen + SAN

  • To: Shaun Reitan <mailinglists@xxxxxxxxxxxxxxxx>
  • From: David Miller <david3d@xxxxxxxxx>
  • Date: Thu, 23 Jun 2011 17:43:07 -0400
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 23 Jun 2011 14:44:23 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=k9V/ezQ1ItpxncypDOk31W71lrLf/x75JMYAUwkkvI+4Jp575Uh/iKShQKxyzHXLbb k/qpnq2aTJFP6KxqzZDCJOVL/pXIIrdG1ZOxGDLRDHY1bBSbAoTk6s/8ssDZVGfRevuZ 8pcQa3phPrrxWmNEsu9poweeE2c4LzKW0uHb0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Thu, Jun 23, 2011 at 4:32 PM, Shaun Reitan
<mailinglists@xxxxxxxxxxxxxxxx> wrote:
> I'm curious what some of you guys out there are doing and or using.  Our
> virtual servers right now are PVM's with logical volumes attached.  I've
> been looking at ISCSI but the problem I'm seeing with ISCSI is that the
> disks that are exported to the initiator just pop up as /dev/sd devices and
> there seams to be no simple way to map that device to the guest easily using
> our automation system.

Have a look at the /dev/disk/by-path/.  It's been a few years since I
played with iSCSI on Linux but I think your device will be the iSCSI
target name.

This device path will not change between hosts and can be used to map
an iSCSI target to a DomU if you're doing one LUN per domain.  I
believe this will work for live migration if that's a concern.  If
you're just exposing large LUNs and want to use LVM to divide up that
space then you'll have to use cLVM if you want to mount that same VG
on multiple DomU's.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.