From owner-freebsd-current@FreeBSD.ORG Mon Nov 16 01:43:34 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 49AA0106566C for ; Mon, 16 Nov 2009 01:43:34 +0000 (UTC) (envelope-from daichi@ongs.co.jp) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.246.90]) by mx1.freebsd.org (Postfix) with ESMTP id 16C3B8FC12 for ; Mon, 16 Nov 2009 01:43:33 +0000 (UTC) Received: from [192.168.1.241] (dullmdaler.ongs.co.jp [202.216.246.94]) by natial.ongs.co.jp (Postfix) with ESMTPSA id 123D812543B; Mon, 16 Nov 2009 10:25:44 +0900 (JST) From: Daichi GOTO Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Mon, 16 Nov 2009 10:25:43 +0900 Message-Id: To: freebsd-emulation@FreeBSD.org Mime-Version: 1.0 (Apple Message framework v1077) X-Mailer: Apple Mail (2.1077) Cc: current@freebsd.org Subject: 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: Mon, 16 Nov 2009 01:43:34 -0000 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.=20 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=20 (e.x. CPUTYPE=3Dcore2) and ccache caches, but this was not relevant, = too.=20 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=20 should treat this problem? --=20 Daichi GOTO CEO | ONGS Inc. 81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp LinkedIn: http://linkedin.com/in/daichigoto