On Wednesday 17 November 2010 06:57:53 Bjoern A. Zeeb wrote:
On Wed, 17 Nov 2010, Thierry Herbelot wrote:
Hi,
first of all freebsd-virtualization@ is the better list for this; Cc:ed.
We are using FreeBSD + VIMAGE at work, and we have seen an annoying
problem : there seems to be a memory
On Wed, 17 Nov 2010, Marko Zec wrote:
Actually, we never seriously discussed or revisited the issue with separate
UMA pools for each vnet instance.
My original motivation when O introduced separate UMA pools was primarily in
making it easier to spot resource leaks, and to prove the correctness
Hi,
Are there any plans to add CPU (at least) accounting
on a per jail basis, so that I can distinguish all
the CPU cycles used by jail X. While sar could be useful,
it only notes user id and that's not unique across jails.
I know that some kind of resource limiting is planned and
that would
Mark Blackman wrote:
Hi,
I know that some kind of resource limiting is planned and
that would naturally require the accounting suggested.
/me bothers to google and finds...
http://lists.freebsd.org/pipermail/freebsd-announce/2010-July/001335.html
never mind. :)
Cheers,
Mark
On Wed, Nov 17, 2010 at 7:17 AM, Bjoern A. Zeeb
bzeeb-li...@lists.zabbadoz.net wrote:
On Wed, 17 Nov 2010, Marko Zec wrote:
Actually, we never seriously discussed or revisited the issue with
separate
UMA pools for each vnet instance.
My original motivation when O introduced separate UMA
Synopsis: [vimage] [panic] TUN\TAP under jail with vimage crashes system
State-Changed-From-To: open-analyzed
State-Changed-By: bz
State-Changed-When: Thu Nov 18 06:13:54 UTC 2010
State-Changed-Why:
Problem is well known.
Responsible-Changed-From-To: freebsd-bugs-freebsd-virtualization
