Re: [Xen-users] Shared storage between open Xen, VMware ESX, XenServer, KVM and a normal Linux...

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Wed, Dec 09, 2009 at 02:05:39PM -0200, Thiago Camargo Martins Cordeiro wrote:
>    Guys!
> 
>     I have one fiber channel IBM storage (10T) and 8 HP Proliant servers with
>    32G of RAM on each and 1 HP with 4G of RAM.
> 
>     My question is:
> 
>    * How to use the same storage (block device) with all my different
>    virtualization servers simultaneously?
> 
>     I have 2 open source Xen with CentOS 5.4, 2 VMWare ESX, 2 Citrix
>    XenServer, 2 KVM powered by Ubuntu and 1 Debian exporting the IBM storage
>    to a SAN via NFS/iSCSI/CIFS... And, I have more open source Xen servers
>    using the same storage, but via NFS instead via fiber channel (HBA).
> 
>     So, how to store the virtual harddisks on a repository visible by all
>    flavours of virtualization technologies?
> 
>     Is there some kind of cluster file system compatible with CentOS, ESX,
>    XenServer, Ubuntu and Debian out there?
> 
>     Or... do I need to divide the storage, for example, creating LUNs for
>    each kind of hypervisors?
> 
>     I'll try to ilustrate:
> 
>    |FC IBM STORAGE|
>                       \_ (HBA) XenServer 1
>                       \_ (HBA) XenServer 2
>                       \_ (HBA) ESX 1
>                       \_ (HBA) ESX 2
>                       \_ (HBA) CentOS with Xen 1...2
>                       \_ (HBA) Ubuntu with KVM 1...2
>                       \_ (HBA) Debian 1
>                                            \_ (NFS) XenServer 3
>                                            \_ (NFS) XenServer 4
>                                            \_ (NFS) Ubuntu KVM 3
> 
>     My Debian 1 is exporting the FC Storage via NFS, this is necessary
>    because not all my hosts have the HBA interface but, I really want to be
>    able to do a live motion from XenServer 3 to XenServer 1, for example! Or
>    from KVM 3 to KVM 2...
> 
>     I appreciate ANY help!
> 

I think NFS is the only supported method that works with all of the
listed virtualization solutions.

The other options is to have multiple LUNs, one for each technique, or
whatever your requirements are.

CLVM is option for Xen/KVM, VMware prefers to use VMFS, XenServer has
it's own SR/LVM stuff etc.

-- Pasi


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