so all the guest os share the same kernel with host, that's the root
cause.
thank you!
在 2012年3月6日 上午11:45，Fajar A. Nugraha <l...@fajar.net>写道：
> 2012/3/6 陈竞 <cj.mag...@gmail.com>:
> > I see that we can start a ubuntu in a lxc. So when ubuntu do block io
> > operation, what does it really do, since it does not simulate hardware?
>
> All "OS" running in lxc containers shares the same kernel with the
> host. The kernel performs the necessary i/o operation.
>
> From the host perspective, the io operation is treated just like any
> normal io operation from a normal running process.
>
> > And what the real difference between kvm and lxc, since we can start a
> os in
> > lxc?
>
> I like to think of lxc as chroot with steroids. The host shares the
> same kernel and part of the filesystem with the guest (or rather, the
> host sees all guests' filesystem). It's different from normal chroot
> in:
> - guests can only see their own processes
> - guests has it's own ip address, can be on different logical subnet
> from the host
> - guests has some additional limits (e.g. memory, cpu share) imposed on
> them
>
> kvm is a full-blown virtualization setup, where each guest OS can have
> its own kernel, or even running non-linux OS (e.g. windows).
>
> --
> Fajar
>
--
陈竞，中科院计算技术研究所，高性能计算机中心
Jing Chen HPCC.ICT.AC China
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users
