From owner-freebsd-emulation@FreeBSD.ORG  Wed Nov 11 06:42:35 2009
Return-Path: <owner-freebsd-emulation@FreeBSD.ORG>
Delivered-To: freebsd-emulation@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1022F1065672
	for <freebsd-emulation@freebsd.org>;
	Wed, 11 Nov 2009 06:42:35 +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 D35DE8FC0A
	for <freebsd-emulation@freebsd.org>;
	Wed, 11 Nov 2009 06:42:34 +0000 (UTC)
Received: from parancell.ongs.co.jp (dullmdaler.ongs.co.jp [202.216.246.94])
	by natial.ongs.co.jp (Postfix) with ESMTPSA id 6D44A12543B
	for <freebsd-emulation@freebsd.org>;
	Wed, 11 Nov 2009 15:42:33 +0900 (JST)
Date: Wed, 11 Nov 2009 15:42:33 +0900
From: Daichi GOTO <daichi@ongs.co.jp>
To: freebsd-emulation@freebsd.org
Message-Id: <20091111154233.5c9d08ed.daichi@ongs.co.jp>
Organization: ONGS Inc.
X-Mailer: Sylpheed 2.7.1 (GTK+ 2.16.6; amd64-portbld-freebsd9.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: VirtualBox 3.0.51.r22902 on CURRENT/amd64 leads system freeze
 within bridge networking
X-BeenThere: freebsd-emulation@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Development of Emulators of other operating systems
	<freebsd-emulation.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-emulation>, 
	<mailto:freebsd-emulation-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-emulation>
List-Post: <mailto:freebsd-emulation@freebsd.org>
List-Help: <mailto:freebsd-emulation-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-emulation>, 
	<mailto:freebsd-emulation-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2009 06:42:35 -0000

I have tried to use VirtualBox 3.0.51.r22902 within bridge
networking. In any ways, VirtualBox gets system freeze.

  Environment:
    VirtualBox 3.0.51.r22902
    FreeBSD 9.0-CURRENT (Fri Nov  6 10:09:25 JST 2009) amd64
    Core2Quad Q8300 (xVT not supported version)

  Method #1
    kldload vboxdrv
    kldload vboxnetflt
    kldload vboxnetadp
    VirtualBox -> Bridge Networking -> choose of re0
        (re0 is used on host)
    GuestOS starts boot and host gets freeze immediately 

  Method #2
    kldload vboxdrv
    kldload vboxnetflt
    kldload vboxnetadp
    VirtualBox -> Bridge Networking -> choose of fxp0
        (re0 is not used on host, just plugged)
    GuestOS starts boot and host gets freeze immediately 

  Method #3
    kldload vboxdrv
    kldload if_bridge
    setup tap interface
    setup bridge intarace
    VirtualBox -> Bridge Networking -> choose of tap0
    GuestOS starts boot and host gets freeze immediately 

  Method #4
    kldload vboxdrv
    kldload vboxnetflt
    kldload vboxnetadp
    kldload if_bridge
    setup tap interface
    setup bridge intarace
    VirtualBox -> Bridge Networking -> choose of tap0
    GuestOS starts boot and host gets freeze immediately 

It looks like VirtualBox on amd64 cannot use bridge feature.
Could anyone use bridge networking on amd64?  The lack of 
xVT technology leads this issue?

If anyone has any ideas, please teach me.
Thanks

-- 
Daichi GOTO
CEO | ONGS Inc.
81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp
LinkedIn: http://linkedin.com/in/daichigoto