Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Oct 2007 10:20:58 +0300
From:      Nikolay Pavlov <qpadla@gmail.com>
To:        freebsd-arch@freebsd.org
Cc:        Marko Zec <zec@freebsd.org>, arch@freebsd.org, James Gritton <jamie@gritton.org>, Julian Elischer <julian@elischer.org>
Subject:   Re: kernel level virtualisation requirements.
Message-ID:  <200710131021.03861.qpadla@gmail.com>
In-Reply-To: <470FD0DC.5080503@gritton.org>
References:  <470E5BFB.4050903@elischer.org> <470FD0DC.5080503@gritton.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1379809.SUtEzzziul
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 12 October 2007 22:54:04 James Gritton wrote:
> Julian Elischer wrote:
>  > What I'd like to see is a bit of a 'a-la-carte' virtualisation
>  > ability.
>
> ...
>
>  > My question to you, the reader, is:
>  > what aspects of virtualisation (the appearance of multiple instances
>  > of some resource) would you like to see in the system?
>
> Of course everything jail has now, and all the network bits that vimage
> offers.
>
> CPU scheduling, in particular schedule the CPU first by jail, and then
> by processes within jail.

This is absolutely "MUST HAVE" feature i think.

>
> Filesystem quotas, without the need for each jail to have its own mount
> point.

Strange, but IMHO it would be better slightly revert this statement:
=46ilesystem quotas _with_ the need for each jail to have it's own mount=20
point, but with out the need to maintain them in fstab (Like it is in=20
ZFS). Because you gain the ability to maintain jails in a filesystem=20
level(snapshots, cloning, dump, restore and so on).

>
> A lot of things that fall under the IPC category: UNIX domain sockets
> (part of
> jail chroot I suppose), PTYs, tunnel devices, SYSV IPC, file locks.
>
> Swap space and resident memory limits.
>
>
> The sysctl mechanism seems a good way to declare jails as having one
> capability
> or the other.  This would alleviate the need to keep updating the jail
> structure when someone has a new idea, especially handy since the single
> structure makes it very hard to work on more than one new idea at a
> time.


=2D-=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20
=2D Best regards, Nikolay Pavlov. <<<-----------------------------------   =
=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20


--nextPart1379809.SUtEzzziul
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBHEHHf/2R6KvEYGaIRAh2SAJ44rcUr2J5eB3f3FvkqHA7XIOlFqQCbBeyt
Rvi0dYRzYZbOo20RUXEPdvw=
=dH9k
-----END PGP SIGNATURE-----

--nextPart1379809.SUtEzzziul--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200710131021.03861.qpadla>