Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for tag 'vimage'

This is an experimental report containing PRs for tag 'vimage' as of 5-26-2012. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.

This report is generated statically.

Please give feedback on this report to linimon@FreeBSD.org. Thanks.


PRs for tag 'vimage':
SSubmittedTrackerResp.Description
o2012/05/03kern/167551virtualization[vimage] Fatal trap 12 jails, vimage, ifconfig destroy epair*a
o2012/02/17kern/165252virtualization[vimage] [pf] [panic] kernel panics with VIMAGE and PF on FreeBSD 9.0 rel
o2011/09/28kern/161094virtualization[vimage] [pf] [panic] kernel panic with pf + VIMAGE when stopping a jail
o2011/09/07kern/160541virtualization[vimage][pf][patch] panic: userret: Returning on td 0xxxxxxxxx (pid xxxx, pftop) with vnet 0xxxxxxxxx set in pfioctl
o2011/09/06kern/160496virtualization[vimage] [pf] [patch] kernel panic with pf + VIMAGE
o2011/07/06kern/158686virtualization[vimage] [tap] [patch] Add VIMAGE support to if_tap
a2010/11/08kern/152047virtualization[vimage] [panic] TUN\TAP under jail with vimage crashes system
o2010/06/26kern/148155virtualization[vimage] [pf] Kernel panic with PF/IPFilter + VIMAGE kernel option
a2010/06/17kern/147950virtualization[vimage] [carp] VIMAGE + CARP = kernel crash
a2009/12/17kern/141696virtualization[rum] [vimage] [panic] rum(4)+ vimage = kernel panic
10 problems total.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.