On Tue, 25 Jan 2011 18:13:43 -0800, Julian Elischer wrote:
> On 1/25/11 1:06 PM, Mikolaj Golub wrote:
>> On Sun, 23 Jan 2011 23:44:41 -0800 Julian Elischer wrote:
>>   JE>  On 1/23/11 6:33 AM, Mikolaj Golub wrote:
>>   >>  As a quick fix I added in VBoxNetFlt-freebsd.c in all "problem" 
>> functions
>>   >>  CURVNET_SET_QUIET(vnet0) macro, which sets td->td_vnet to default vnet 
>> (see the
>>   >>  attached patch). This has fixed the issue for me and now I am happily 
>> running
>>   >>  both VNET jails and VirtualBox machines on my desktop.
>>   >>
>>   >>  But the way I fixed the issue looks hackish for me. Could someone 
>> suggest a
>>   >>  better solution?
>>   JE>  this is probably at east partially the correct solution.
>>   JE>  Usually you should also set the value back to its previous value when
>>   JE>  you leave that code as well.
>> Thank you for the comments. Actually the patch contained CURVNET_RESTORE()
>> too. I just did not mentioned it :-). So if it looks like right solution here
>> is an "improved" version of the patch: vnet to switch is taken from thread's
>> ucred (on interface initialization) or from ifp->if_vnet.
> yes I like it.. Now you just need a port person to patch the port :-)

Sounds like it's my turn now. Which FreeBSD version is required to be
able to use it?
Is VIMAGE enabled per default and what happens if VIMAGE is disabled -
does it at least build fine with that patch?

For Mikolaj Golub to get this patch upstream we need that you either
agree that his patch is under the MIT License or sign a Sun Contributors
Agreement. Then we can submit that patch upstream or you can do it
yourself if you prefer. Read here:

Bernhard Froehlich
freebsd-virtualization@freebsd.org mailing list
To unsubscribe, send any mail to 

Reply via email to