From: Yura Pismerov <y.pismerov@armorware.net>
To: xen-devel@lists.xensource.com
Subject: Re: [Xen-users] How to share data between guest domains
Date: Mon, 20 Mar 2006 08:49:44 -0500 [thread overview]
Message-ID: <441EB2F8.3080403@armorware.net> (raw)
In-Reply-To: <62b0912f0603200445q6667d3c9q53bd8e9ce48fcedf@mail.gmail.com>
I found that using NFS for things like this makes much more sense.
You can run the domU with NFS root (read-only) and map certain areas you
need read/write
to tmpfs by mounting them with "mount --bind" in Linux). For example, if
I use NFS root and want my /etc
be writable I can always write its content to a tmpfs mounted area and
run "mount --bind /tmpfs/etc /etc".
This also will solve problems with centralized package updates when not
only /usr is being updated, but some other areas (eg. /etc, /var/lib).
You want those areas be shared between domU's as well.
Molle Bestefich wrote:
>Todd D. Esposito wrote:
>
>
>>However, on that note, I wonder if you could mount the same file system,
>>say something like /usr, into multiple domU's READ ONLY.
>>
>>
>
>That works for me.
>
>What doesn't work is mounting that file/device READ/WRITE in one domU
>to update the filesystem. For that, I have to take down *all* domUs.
>Not good...
>
>(When I try I get a vbd: error saying "already in use".)
>
>(I know about caching and that I need eg. a cluster-aware filesystem
>to do this.)
>
>I've spent a couple of hours hunting through various Xen source files.
> There's a lot of Python functions that are only 3-5 lines long and
>which does little else than calling the next function, which makes it
>very hard to figure out what's going on :-/.
>
>Could one of you devel guys please let me know where I need to go to
>remove this silly limitation? :-)
>
>_______________________________________________
>Xen-users mailing list
>Xen-users@lists.xensource.com
>http://lists.xensource.com/xen-users
>
>
--
Yuri Pismerov, System Administrator
Armor Technologies (Canada) Inc.
P: 905 305 1946 (x.3519)
http://www.armorware.net
Privacy Protection Guaranteed!
next prev parent reply other threads:[~2006-03-20 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1142710436.15319.1.camel@localhost>
[not found] ` <441C7352.7030401@hcsd.de>
[not found] ` <441CB16E.6090901@freemail.hu>
[not found] ` <200603182119.31607.javier@guerrag.com>
[not found] ` <2967.67.184.68.1.1142737228.squirrel@67.184.68.1>
2006-03-20 12:45 ` How to share data between guest domains Molle Bestefich
2006-03-20 13:49 ` Yura Pismerov [this message]
2006-03-20 17:24 ` Re: [Xen-users] " Xin Zhao
2006-03-21 13:06 ` Yura Pismerov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=441EB2F8.3080403@armorware.net \
--to=y.pismerov@armorware.net \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.