Date: Wed, 19 Sep 2012 15:10:38 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Garrett Cooper <yanegomi@gmail.com> Cc: Ian Lepore <freebsd@damnhippie.dyndns.org>, lev@freebsd.org, freebsd-current@freebsd.org Subject: Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection Message-ID: <CAJ-Vmo=oHti=F8a=kaX=HZFyUjKwg-NaoRE=Ke_ezbVd7iauPQ@mail.gmail.com> In-Reply-To: <CAGH67wS0pKmEjbHMH3dFPqkzTbEx6tFgBOKzWxGXHfDtap=iGw@mail.gmail.com> References: <80840563.20120920002200@serebryakov.spb.ru> <1252171344.20120920003724@serebryakov.spb.ru> <1348087584.95562.55.camel@revolution.hippie.lan> <CAGH67wS0pKmEjbHMH3dFPqkzTbEx6tFgBOKzWxGXHfDtap=iGw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19 September 2012 14:57, Garrett Cooper <yanegomi@gmail.com> wrote: > On Wed, Sep 19, 2012 at 1:46 PM, Ian Lepore > <freebsd@damnhippie.dyndns.org> wrote: > > ... > >> Yes, exactly. I updated the PR to request that my patch not get >> committed because it locks up virtualbox. I hope to find time soon to >> learn enough about installing/configuring virtualbox to figure out what >> the problem is (offhand,I suspect it hangs in the loop that probes for >> the need to re-index, because vbox doesn't quite emulate the hardware >> behavior fully). > > Why not just detect VBox and disable that functionality? VMware at > least has a sane way of determining whether or not you're running it > based on the SMBios ident.. Sure, but that doens't answer the underlying reason(s) of "why is it failing?". :-) Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=oHti=F8a=kaX=HZFyUjKwg-NaoRE=Ke_ezbVd7iauPQ>