Quoting Greg KH ([email protected]):
> On Mon, Nov 14, 2005 at 11:15:01PM -0600, Serge E. Hallyn wrote:
> > Quoting Paul Jackson ([email protected]):
> > > Serge wrote:
> > > > the vserver model
> > >
> > > What's that?
> >
> > :) Well a vserver pretends to be a full system of its own, though you
> > can have lots of vservers on one machine. Processes in each virtual
> > server see only other processes in the same vserver. However in
> > vserver the pids they see are the real kernel pids - except for one
> > process per vserver which can be the fakeinit. Other processes in the
> > same vserver see it as pid 1, but to the kernel it is still known by
> > its real pid.
>
> Why not just use Xen? It can handle process migration from one virtual
> machine to another just fine.
It handles vm migration, but not process migration. The most compelling
thing (imo) which the latter allows you to do is live OS upgrade under
an application. Xen won't let you do that. Of course load-balancing is
also more fine-grained and powerful with process set migration, and
the overhead of a full OS per migrateable job is quite heavy.
That's not to say we don't also want to use Xen :) - it has it's own
advantages and I'm not intending to denigrate those. We just hope to
get both!
-serge
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
