From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Linux Container and Tapdev Date: Mon, 9 Jan 2012 11:09:19 -0500 Message-ID: <20120109160919.GA28700@phenom.dumpdata.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: MaoXiaoyun Cc: xen devel List-Id: xen-devel@lists.xenproject.org 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