From owner-freebsd-questions@freebsd.org Tue Jun 30 10:24:52 2015 Return-Path: Delivered-To: freebsd-questions@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 A2D2498E294 for ; Tue, 30 Jun 2015 10:24:52 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.179]) (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 7C26911FC for ; Tue, 30 Jun 2015 10:24:52 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [10.2.2.1] (pool-173-48-121-235.bstnma.fios.verizon.net [173.48.121.235]) by douhisi.pair.com (Postfix) with ESMTPSA id 1BBD13F801 for ; Tue, 30 Jun 2015 06:24:51 -0400 (EDT) Message-ID: <55926E72.5080706@sneakertech.com> Date: Tue, 30 Jun 2015 06:24:50 -0400 From: Quartz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: FreeBSD questions Subject: Re: Can't install freebsd inside virtualbox, glacially slow References: <55925B9B.2090503@sneakertech.com> In-Reply-To: <55925B9B.2090503@sneakertech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2015 10:24:52 -0000 > I can't seem to get the 10.1 installer to work under virtualbox, > everything is so slow it's completely unusable. The dvd image takes > upwards of a minute to even draw the opening ascii menu, and attempting > to boot the kernel just sits there forever. If I convert the memstick > img into a vdi and boot from that, I just get the "spinning slash" > forever (it doesn't even get to the menu). I've tried the 'set > vfs.unmapped_buf_allowed=0' trick, tried changing vb's chipset from > PIIX3 to ICH9, tried changing the number of CPUs and ram and everything, > but no dice. Anyone have any ideas? Nevermind, it's fixed. The virtualbox I was using claimed it was still the most recent version, but manually checking virtualbox.org revealed that this was a lie. Updating mostly fixed the slowness issue (It's still not as fast as my other guest OSs, but it's at least it's usable now).