From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: MaoXiaoyun <tinnycloud@hotmail.com>
Cc: xen devel <xen-devel@lists.xensource.com>
Subject: Re: Linux Container and Tapdev
Date: Mon, 9 Jan 2012 11:09:19 -0500 [thread overview]
Message-ID: <20120109160919.GA28700@phenom.dumpdata.com> (raw)
In-Reply-To: <BLU157-W65C4641D5245A308C327C2DA9A0@phx.gbl>
On Sat, Jan 07, 2012 at 12:17:23PM +0800, MaoXiaoyun wrote:
>
> Hi:
>
> Recently I have some study on linux container(lxc), which is a light weight OS level
> virtualization.
>
> With the previous knowledge of tapdisk, I have an assumption that, I may could
> use the vhd for each container to seperate the storage of all containers, or even in
> later days, vhd is stored in distributed storage, container could be migrated.
>
> Build filesystem on tapdev and mount it under some directory, put the rootfs of
How would you "mount" a tapdev filesystem?
But more interestingly, how would you migrate your tap disk? Is it on NFS or OCFS2
or iSCSI? If so, why not just expand the filesystem on an iSCSI disk and mount it
on other machines and "migrate it".
> container into that dir, and start the lxc, I haven't try this, will try later.
I am not really sure how one would freeze and migrate the processes? Does the
cgroups have that functionality?
>
> I post my idea here, hope someone has one forsee comments.
>
> Thanks.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2012-01-09 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.6093.1325902643.12970.xen-devel@lists.xensource.com>
2012-01-07 4:17 ` Linux Container and Tapdev MaoXiaoyun
2012-01-09 16:09 ` Konrad Rzeszutek Wilk [this message]
2012-01-09 23:12 ` hotmaim
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=20120109160919.GA28700@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=tinnycloud@hotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).