Date: Thu, 25 Apr 2013 14:13:49 +0200 From: Nikos Vassiliadis <nvass@gmx.com> To: zulu <zulu@openvps.biz> Cc: Laurent Alebarde <l.alebarde@free.fr>, "freebsd-jail@freebsd.org" <freebsd-jail@freebsd.org> Subject: Re: state of the art ? Message-ID: <51791DFD.3040209@gmx.com> In-Reply-To: <1366868448.5178c1e04043f@gpo.cellcontainer.com> References: <5177B1A4.6060502@free.fr> <1366868448.5178c1e04043f@gpo.cellcontainer.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/25/2013 07:40 AM, zulu wrote: > VNET is supported and there is a "soft" jail restart option which > prevents the "kern/164763: Memory leak in VNET" issue from appearing. This is a really interesting workaround! Yes, ipfw is vnet-capable since a long time and it works as good as the non-virtualized version. Well... except for dummynet which isn't virtualized yet. My point is, VIMAGE is really stable except for: 1) tearing-down a vnet 2) running non-vnet-ready code (pf, dummynet, lagg, ipf etc) Number one is trigged by destroying a jail. Number two is usually triggered *immediately* after trying to use a non-vnet-ready driver. You can avoid these two and if you avoid them it is perfectly stable... Also, I have to say that i like vimage very much so i might be biased:) Just my 2 cents, Nikos
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51791DFD.3040209>