Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Nov 2009 10:08:30 -0800
From:      Julian Elischer <julian@elischer.org>
To:        Robert Watson <rwatson@FreeBSD.org>
Cc:        freebsd-emulation@FreeBSD.org, current@freebsd.org
Subject:   Re: JFYI: VirtualBox-3.0.51.r22902_2 bridge networking freeze issue (solved)
Message-ID:  <4B02E69E.40008@elischer.org>
In-Reply-To: <alpine.BSF.2.00.0911171118140.47035@fledge.watson.org>
References:  <FAFAA703-DBA4-4C5E-B926-FEAAC52EDEA7@ongs.co.jp> <alpine.BSF.2.00.0911171118140.47035@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote:
> 
> On Mon, 16 Nov 2009, Daichi GOTO wrote:
> 
>> At last, I have found an issue situation of system freeze led by 
>> bridge networking. With Vimage enable built kernel, bridge networking 
>> feature will lead system freeze.
> 
> This is more likely a VIMAGE bug than a VirtualBox bug, as VIMAGE is not 
> yet well-tested or ready for real-world use.  I'm not sure if the bridge 
> code is considered productionable with VIMAGE yet?

I believe not.
we use the netgraph bridging because it can act as a reverse bridge
(multiple top ends, a single physical interface)
So we have not really  done much with the standard if_bridge code yet.
Certainly it is not well tested if it works at all.

> 
> Robert
> 
>>
>>  checked environment:
>>    FreeBSD 9.0-CURRENT #44: Mon Nov 16 09:51:20 JST 2009  amd64
>>    virtualbox-3.0.51.r22902_2
>>    Core2 Quad Q9550
>>
>> I have replaced to Q9550 instead of Q8300 to get VT feature, but this 
>> was not
>> relevant (But from this change, I got an ability to use 64bit OS. My 
>> test environment
>> has been extended ;-). Second, I have got rid of some compile options
>> (e.x. CPUTYPE=core2) and ccache caches, but this was not relevant, too.
>> Third, I have changed my BIOS settings and update thats version, yes 
>> living
>> up to your expectations, this was not relevant, too.
>>
>> Finally, I have rolled back my kernel to GENERIC and bridge networking 
>> works
>> correctly. Step by step adding kernel options, at last, I have found 
>> that Vimage
>> feature is a cause of this problem.  Thanks
>>
>> PS
>> Vimage developer, do you have any ideas?  Or with this issue, 
>> VirtualBox side
>> should treat this problem?
>>
>> -- 
>> Daichi GOTO
>> CEO | ONGS Inc.
>> 81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp
>> LinkedIn: http://linkedin.com/in/daichigoto
>>
>> _______________________________________________
>> freebsd-current@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to 
>> "freebsd-current-unsubscribe@freebsd.org"
>>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B02E69E.40008>