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

RE: [Xen-users] Xen 4.0 feature request

  • To: "Nathan Eisenberg" <nathan@xxxxxxxxxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Jeff Sturm <jeff.sturm@xxxxxxxxxx>
  • Date: Tue, 7 Jul 2009 14:38:45 -0400
  • Cc:
  • Delivery-date: Tue, 07 Jul 2009 11:41:35 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: Acn/CYOA5P9D9Ik3Ql6dlWiw3Q7UggAHqcmAAAHQp0A=
  • Thread-topic: [Xen-users] Xen 4.0 feature request

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Nathan Eisenberg
> Sent: Tuesday, July 07, 2009 1:31 PM
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] Xen 4.0 feature request
> More than thinking that it is possible, I do it every single day.  It
works, and it works
> well.  :)
> There's no reason not to have dedicated Logical Volumes for every
domU.  It makes
> dealing with the data backend a lot easier, as the volume management
> incredibly logical and well labeled.

Definitely.  In fact one of our volume groups has 55 LV's:

# vgs
  VG     #PV #LV #SN Attr   VSize VFree
  t0core   1  55   0 wz--nc 4.08T 3.63T

This is a clustered LVM too, shared among 4 dom0 hosts.

You could accomplish the same creating as many LUNs on your SAN, but it
tends to be more work and the volume labels are not as clear.  The only
advantage I see is that you won't have to work around the limitations of
a CLVM (e.g. single-host snapshots).

(It'd be nice too if the Xen tools handled automatic LV
activation/deactivation when bringing up a domU or migrating.)


Xen-users mailing list



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