Date: Tue, 6 Mar 2012 22:55:41 +0100 From: Marko Zec <zec@fer.hr> To: Adrian Chadd <adrian.chadd@gmail.com> Cc: freebsd-virtualization@freebsd.org Subject: Re: VIMAGE + kldload wlan + kldload wtap panic Message-ID: <201203062255.41480.zec@fer.hr> In-Reply-To: <CAJ-VmonjsTDKT_NyHfDjby9TSf6zrfV0PK4RShK2fBNoDtF%2B4Q@mail.gmail.com> References: <CA%2BsBSo%2Bt=p0HLbyOH87DOJWWYn%2Be%2Bok7cwRiL1c1=gCw5=KTqg@mail.gmail.com> <201203062251.39786.zec@fer.hr> <CAJ-VmonjsTDKT_NyHfDjby9TSf6zrfV0PK4RShK2fBNoDtF%2B4Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 06 March 2012 22:52:43 Adrian Chadd wrote: > On 6 March 2012 13:51, Marko Zec <zec@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201203062255.41480.zec>