From owner-freebsd-current@FreeBSD.ORG Tue Nov 17 11:19:33 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1179B1065672; Tue, 17 Nov 2009 11:19:33 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id E06818FC13; Tue, 17 Nov 2009 11:19:32 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 8D73746BA3; Tue, 17 Nov 2009 06:19:32 -0500 (EST) Date: Tue, 17 Nov 2009 11:19:32 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Daichi GOTO In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-emulation@FreeBSD.org, current@freebsd.org Subject: Re: JFYI: VirtualBox-3.0.51.r22902_2 bridge networking freeze issue (solved) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2009 11:19:33 -0000 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? 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" >