VIMAGE + kldload wlan + kldload wtap panic

[Marko Zec]

On Tuesday 06 March 2012 22:52:43 Adrian Chadd wrote:
> On 6 March 2012 13:51, Marko Zec <zec at fer.hr> wrote:
> > On Tuesday 06 March 2012 22:49:56 Adrian Chadd wrote:
> >> Wait a sec. Is it possible that the macro is a no-op when we're
> >> building modules w/ VNET?
> >
> > Yes that's it, the VNET stuff resolves (mostly) to whitespace when
> > options VIMAGE is not on!
>
> So the question is - how the heck are the modules supposed to pull in
> the VNET config?
>
> is there a missing opt_<x>.h somewhere?
>

No, you don't need any extra explicit #includes, but you should see this in 
opt_global.h if you've really configured the kernel with options VIMAGE:

#define VIMAGE 1

Marko