From owner-freebsd-current@FreeBSD.ORG Wed Sep 19 21:57:31 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA510106564A; Wed, 19 Sep 2012 21:57:31 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 569AC8FC08; Wed, 19 Sep 2012 21:57:30 +0000 (UTC) Received: by obbun3 with SMTP id un3so1990987obb.13 for ; Wed, 19 Sep 2012 14:57:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=41YnPr0vNAWX9gZWcvVrfVG5mie2771m9dp46SgLwG8=; b=UvN409tQvjuSJLwp1wWQwmvdvKqdgj+KKLtUxTIqCGOOLdpT1iTtC+1EWdiX1H8F3M CErN8/Y/ruUcpI49PlkMgSQgm5zU5y87eZTEv59CINX6U2x7M4fMxvZP5t0VaInkI0ip wuBNn16VsaVWB6rQGMWexSFs4rFJehuEi2hJFUbeHXzm34Xh8JLlhBpjePgU+CIyhhNb QxHZq3nc3uqX4Lg2iRybZD/+6/rFLygVxfyH1Pf4nDvEe7LYbSOW40U/jGnMOwTFD7Lw I9mG0izW67urxlTzir3KG9ruZCs6PiFi8p3yAbeOryXypQXZ0ylMY2azVpStDu9A3EDI 2AQw== MIME-Version: 1.0 Received: by 10.60.13.232 with SMTP id k8mr3954980oec.81.1348091850473; Wed, 19 Sep 2012 14:57:30 -0700 (PDT) Received: by 10.76.142.201 with HTTP; Wed, 19 Sep 2012 14:57:30 -0700 (PDT) In-Reply-To: <1348087584.95562.55.camel@revolution.hippie.lan> References: <80840563.20120920002200@serebryakov.spb.ru> <1252171344.20120920003724@serebryakov.spb.ru> <1348087584.95562.55.camel@revolution.hippie.lan> Date: Wed, 19 Sep 2012 14:57:30 -0700 Message-ID: From: Garrett Cooper To: Ian Lepore Content-Type: text/plain; charset=ISO-8859-1 Cc: 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 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Sep 2012 21:57:31 -0000 On Wed, Sep 19, 2012 at 1:46 PM, Ian Lepore 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.. Thanks! -Garrett