Bug 182343

Summary: Boot FreeBSD-10-Alpha2 in VituralBox Crash
Product: Base System Reporter: ben
Component: amd64Assignee: freebsd-amd64 (Nobody) <amd64>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description ben 2013-09-24 10:40:00 UTC
Kernel panic on default boot from iso.
- panic: running without device atpic requires a local APIC

How-To-Repeat: 
1) I create an new VM for installing FreeBSD on. VM stats 512 MB Memory and 8 GB HD.  No changes to default settings, but have also tried with changing net work to bridged device with same result.

2) After vm create is done.  Turn on and select FreeBSD-10-Alpha2.iso to boot from.

3) Select Normal (default option) boot from FreeBSD boot menu.

4) panic response starts at:
     - panic: running without device atpic requires a local APIC
Comment 1 ben 2013-09-25 00:24:12 UTC
Screenshot when booting from CD: http://imgur.com/AXCk1fD=0A=0A-----Origina=
l Message-----=0AFrom: FreeBSD-gnats-submit@FreeBSD.org=0ASent: Tuesday, Se=
ptember 24, 2013 5:40am=0ATo: "Ben Adams" <ben@acustat.org>=0ASubject: Re: =
amd64/182343: Boot FreeBSD-10-Alpha2 in VituralBox Crash=0A=0AThank you ver=
y much for your problem report.=0AIt has the internal identification `amd64=
/182343'.=0AThe individual assigned to look at your=0Areport is: freebsd-am=
d64. =0A=0AYou can access the state of your problem report at any time=0Avi=
a this link:=0A=0Ahttp://www.freebsd.org/cgi/query-pr.cgi?pr=3D182343=0A=0A=
>Category:       amd64=0A>Responsible:    freebsd-amd64=0A>Synopsis:       =
Boot FreeBSD-10-Alpha2 in VituralBox Crash=0A>Arrival-Date:   Tue Sep 24 09=
:40:00 UTC 2013=0A
Comment 2 ben 2013-09-25 00:32:40 UTC
This Can Be closed APIC issue in VBOX not FreeBSD=0A=0A-----Original Messag=
e-----=0AFrom: FreeBSD-gnats-submit@FreeBSD.org=0ASent: Tuesday, September =
24, 2013 5:40am=0ATo: "Ben Adams" <ben@acustat.org>=0ASubject: Re: amd64/18=
2343: Boot FreeBSD-10-Alpha2 in VituralBox Crash=0A=0AThank you very much f=
or your problem report.=0AIt has the internal identification `amd64/182343'=
.=0AThe individual assigned to look at your=0Areport is: freebsd-amd64. =0A=
=0AYou can access the state of your problem report at any time=0Avia this l=
ink:=0A=0Ahttp://www.freebsd.org/cgi/query-pr.cgi?pr=3D182343=0A=0A>Categor=
y:       amd64=0A>Responsible:    freebsd-amd64=0A>Synopsis:       Boot Fre=
eBSD-10-Alpha2 in VituralBox Crash=0A>Arrival-Date:   Tue Sep 24 09:40:00 U=
TC 2013=0A
Comment 3 Mark Johnston freebsd_committer freebsd_triage 2013-09-25 02:24:37 UTC
State Changed
From-To: open->closed

Closed by submitter request.