From owner-freebsd-bugs@freebsd.org  Wed Aug 12 20:26:05 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE0DF9AB987
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 12 Aug 2015 20:26:05 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id DB0131AA9
 for <freebsd-bugs@FreeBSD.org>; Wed, 12 Aug 2015 20:26:05 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t7CKQ5Ua085381
 for <freebsd-bugs@FreeBSD.org>; Wed, 12 Aug 2015 20:26:05 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 202276] Changes to vt(4) in r286667 makes FreeBSD unbootable in
 VirtualBox
Date: Wed, 12 Aug 2015 20:26:05 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: ed@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
 attachments.created
Message-ID: <bug-202276-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Aug 2015 20:26:06 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202276

            Bug ID: 202276
           Summary: Changes to vt(4) in r286667 makes FreeBSD unbootable
                    in VirtualBox
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: ed@FreeBSD.org

Created attachment 159818
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=159818&action=edit
Screenshot of VirtualBox

Attached is a screenshot of a GENERIC FreeBSD kernel at r286667 booting in
VirtualBox 5.0.0. Almost immediately after starting the kernel, video gets
corrupted and the system locks up. r286666 works properly.

The same also happened with VirtualBox 4.3.28 and 4.3.30. I'm using the boot
loader from FreeBSD 10.1. As far as I know, that shouldn't be an issue, right?
We want FreeBSD 11.0 to be bootable from 10.

-- 
You are receiving this mail because:
You are the assignee for the bug.