From owner-freebsd-emulation@FreeBSD.ORG  Thu Jun 24 07:46:11 2010
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 6DA701065675;
	Thu, 24 Jun 2010 07:46:11 +0000 (UTC)
	(envelope-from beat@FreeBSD.org)
Received: from azh-com0.aspectra.com (azh-com0.aspectra.com [212.47.170.6])
	by mx1.freebsd.org (Postfix) with ESMTP id 2F5B48FC14;
	Thu, 24 Jun 2010 07:46:10 +0000 (UTC)
Message-ID: <4C230D38.9020402@FreeBSD.org>
Date: Thu, 24 Jun 2010 09:46:00 +0200
From: Beat Gaetzi <beat@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.9.2.4) Gecko/20100623 Thunderbird/3.1
MIME-Version: 1.0
To: Andriy Gapon <avg@icyb.net.ua>
References: <4C230BC2.4040908@icyb.net.ua>
In-Reply-To: <4C230BC2.4040908@icyb.net.ua>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jun 2010 07:46:08.0957 (UTC)
	FILETIME=[4F1AA6D0:01CB1371]
Cc: freebsd-emulation@FreeBSD.org, vbox@FreeBSD.org
Subject: Re: why vbox is marked broken for head?
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: Thu, 24 Jun 2010 07:46:11 -0000

On 06/24/10 09:39, Andriy Gapon wrote:
>
> Why vbox is marked broken for head?
> I keep using it with TRYBROKEN and see zero problems.
> Where are the bug reports?  Perhaps there are specific problems that can be
> investigated, fixed or worked around (via configuration)?

There are several known panics with CURRENT older than revision 209048. 
The port also do not build on current newer than revision 208751. This 
is fixed in our development repository and we will remove the BROKEN 
with the update to 3.2.6.

Beat