panic with jail bug_id 213673 was: VNET branch destiny

2017-04-12 Thread peter . blok
The problem happens when stopping a jail. It doesn’t seem to be related to vnet at all. When stopping a jail, pfr_cleanup calls uma_zdestroy(V_pfr_kentry_z). The dtor calls zone_release, which calls slab_free_item. The issue seems to be that the keg found in zone_release does not belong to the

Re: VNET branch destiny

2017-04-11 Thread peter . blok
Hi Kristof, I’m prety sure it is the same as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213673 . It is unrelated to epair or ng_eiface (my case). I’ll dig some more. Peter > On 11 Apr 2017, at 08:47, Kristof Provost wrote: >

Re: VNET branch destiny

2017-04-10 Thread Kristof Provost
On 10 Apr 2017, at 12:10, peter.b...@bsd4all.org wrote: There have been issues with pf if I recall correctly. I currently have issues with stable, pf and vnet. There is an issue with pf table entries when an interface is moved to a different vnet. Does anyone no if there is a specific fix for

Re: VNET branch destiny

2017-04-10 Thread Ari Suutari
Hi, There is also this one: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213673 It's about memory leak with pf tables + vnet, but the problem results in panic, which is quite easily reproduced. Ari S. On 10.4.2017 17:39, Ernie Luzar wrote: To the VNET (VIMAGE) update project team m

Re: VNET branch destiny

2017-04-10 Thread Bjoern A. Zeeb
On 10 Apr 2017, at 20:59, peter.b...@bsd4all.org wrote: No problem. Although pf is not used the vnet_destroy seems to be the issue. Some parts are not virtualized and the vnet_destroy->vnet_pf_uninit teardown happens on the host vnet so to speak. The base system VNET is not shutdown; it nev

Re: VNET branch destiny

2017-04-10 Thread peter . blok
No problem. Although pf is not used the vnet_destroy seems to be the issue. Some parts are not virtualized and the vnet_destroy->vnet_pf_uninit teardown happens on the host vnet so to speak. > On 10 Apr 2017, at 22:11, Ernie Luzar wrote: > > peter.b...@bsd4all.org wrote: >> Well, in my case i

Re: VNET branch destiny

2017-04-10 Thread Ernie Luzar
peter.b...@bsd4all.org wrote: Well, in my case it panic’ed on 11-stable. I’m only using pf on the host, not in the jail. I’m using Devin Teske’s jng to create a netgraph bridge. It is my intention to use the netgrpah bridge with bhyve as well. I also tested using Devin Teske’s jng to create

Re: VNET branch destiny

2017-04-10 Thread Ernie Luzar
peter.b...@bsd4all.org wrote: Well, in my case it panic’ed on 11-stable. I’m only using pf on the host, not in the jail. I’m using Devin Teske’s jng to create a netgraph bridge. It is my intention to use the netgrpah bridge with bhyve as well. The panic (one-time) happened in pfioctl when I re

Re: VNET branch destiny

2017-04-10 Thread Ernie Luzar
To the VNET (VIMAGE) update project team members Release 11.0 has some out standing VNET (VIMAGE) PR's that need addressing. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212013 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21203

Re: VNET branch destiny

2017-04-10 Thread peter . blok
Well, in my case it panic’ed on 11-stable. I’m only using pf on the host, not in the jail. I’m using Devin Teske’s jng to create a netgraph bridge. It is my intention to use the netgrpah bridge with bhyve as well. The panic (one-time) happened in pfioctl when I refreshed the rules. I suspect th

Re: VNET branch destiny

2017-04-10 Thread Ernie Luzar
peter.b...@bsd4all.org wrote: There have been issues with pf if I recall correctly. I currently have issues with stable, pf and vnet. There is an issue with pf table entries when an interface is moved to a different vnet. Does anyone no if there is a specific fix for this that hasn’t been port

Re: VNET branch destiny

2017-04-10 Thread peter . blok
There have been issues with pf if I recall correctly. I currently have issues with stable, pf and vnet. There is an issue with pf table entries when an interface is moved to a different vnet. Does anyone no if there is a specific fix for this that hasn’t been ported to stable? I haven’t had the

Re: VNET branch destiny

2017-04-09 Thread Pavel Timofeev
31 марта 2017 г. 17:40 пользователь "Bjoern A. Zeeb" < bzeeb-li...@lists.zabbadoz.net> написал: On 31 Mar 2017, at 13:57, Pavel Timofeev wrote: Hello, dear freebsd-current@! > > There was FreeBSD Foundation report back in 2016Q2 where it told us > about VNET (VIMAGE) update project sponsored by f

Re: VNET branch destiny

2017-04-01 Thread Pavel Timofeev
31 марта 2017 г. 17:40 пользователь "Bjoern A. Zeeb" < bzeeb-li...@lists.zabbadoz.net> написал: On 31 Mar 2017, at 13:57, Pavel Timofeev wrote: Hello, dear freebsd-current@! > > There was FreeBSD Foundation report back in 2016Q2 where it told us > about VNET (VIMAGE) update project sponsored by f

Re: VNET branch destiny

2017-03-31 Thread Bjoern A. Zeeb
On 31 Mar 2017, at 13:57, Pavel Timofeev wrote: Hello, dear freebsd-current@! There was FreeBSD Foundation report back in 2016Q2 where it told us about VNET (VIMAGE) update project sponsored by foundation. What is the current situation? Is it committed into base? If not what's the plan? Chang

VNET branch destiny

2017-03-31 Thread Pavel Timofeev
Hello, dear freebsd-current@! There was FreeBSD Foundation report back in 2016Q2 where it told us about VNET (VIMAGE) update project sponsored by foundation. What is the current situation? Is it committed into base? If not what's the plan? ___ freebsd-cu