WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Sharing filesystems between VMs.

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Sharing filesystems between VMs.
From: Andy Davidson <andy@xxxxxxxxxxxx>
Date: Wed, 03 Aug 2005 17:09:01 +0100
Delivery-date: Wed, 03 Aug 2005 16:07:28 +0000
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Debian Thunderbird 1.0.6 (X11/20050728)

Hi, folks --

I'm using xen 2.0.6 on a Debian Sarge host, and Linux 2.6.11.10-xen0.

I use Xen to host a number of QA environments.

I'm mounting filesystems for guest vms from files on disk. Ideally, I would like to share a single 'file' between all VMs for /usr/local and another ext3 partition, and maintain individual root and swap partitions on a per-machine basis.

This doesn't seem to work presently. When I bring up the 'second' machine in the cluster, I get :

qa-host:/etc/xen/auto# xm create xm-manager
Using config file "xm-manager".
Error: Error creating domain: vbd: Segment not found: uname=file:/export/vm/vm-usrlocal


If I then shutdown the machine 'holding' this partition I can bring up the VM as normal.

qa-host:/etc/xen/auto# xm create xm-manager
Using config file "xm-manager".
Started domain VM8, console on port 9614


Is this a limitation that I can not work around ? A limitation that an upgrade or alternative method of storing the filesystem will fix ?

Ideally I'd like to avoid the situation where I physically export the partitions I want to use on guest OSes over NFS .. but I am aware that it's an option which will probably work...

Thanks for any ideas you guys may have ..

-a

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