From owner-freebsd-current@FreeBSD.ORG Wed Jul 20 15:15:00 2011 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 D770D10656AA; Wed, 20 Jul 2011 15:15:00 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id A8E438FC13; Wed, 20 Jul 2011 15:15:00 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 539F246B2D; Wed, 20 Jul 2011 11:15:00 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id DC5988A02C; Wed, 20 Jul 2011 11:14:59 -0400 (EDT) From: John Baldwin To: Bernhard Froehlich Date: Wed, 20 Jul 2011 09:04:45 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: <4E263EFE.3040200@FreeBSD.org> <201107200741.26362.jhb@freebsd.org> <565082b8e8b3e358266054e58e591e12@bluelife.at> In-Reply-To: <565082b8e8b3e358266054e58e591e12@bluelife.at> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201107200904.45647.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 20 Jul 2011 11:15:00 -0400 (EDT) Cc: Steve Wills , freebsd-current@freebsd.org Subject: Re: em problem in virtualbox since the weekend 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, 20 Jul 2011 15:15:01 -0000 On Wednesday, July 20, 2011 8:33:07 am Bernhard Froehlich wrote: > On Wed, 20 Jul 2011 07:41:26 -0400, John Baldwin wrote: > > On Tuesday, July 19, 2011 10:35:42 pm Steve Wills wrote: > >> Hi, > >> > >> While testing some other things, I found -CURRENT from yesterday doesn't > >> work with the em0 in my VirtualBox 4.0.8 (a little out of date > >> admittedly). It worked Friday or Saturday I think. Anyone else seen this > >> or should I open a PR? Has the code changed or am I perhaps > >> misremembering dates? The error reported is: > >> > >> em0: Unable to allocate bus resource: memory > >> em0: Allocation of PCI resources failed > > > > This is due to a bug in VirtualBox's BIOS implementation. Someone > > should file > > a bug report with VirtualBox to ask them to fix their BIOS. The problem is > > that they claim that the Host-PCI bridge in their system only decodes > > addresses 0xa0000-0xbffff (i.e. the VGA window) via the "Producer" resources > > in the _CRS method of the Host-PCI bridge device. This tells the OS > > that all > > the existing PCI devices are using invalid memory address ranges but that > > there is also no available address space to allocate for PCI devices such as > > em0. > > > > You can workaround this by setting "debug.acpi.disabled=hostres" until > > VirtualBox fixes their code. I'm happy to provide further > > clarification to an > > existing VirtaulBox bug report if needed. > > Thanks a lot for the analysis! I've talked to one of the virtualbox > developers about that but they are not aware of such problems with Linux > or Windows guests yet. So they are currently unsure if it's a VirtualBox > or FreeBSD fault and if it's their fault why it works fine with other > guests. I'm also unsure because I haven't heard of that problem before > and now multiple people complain. That looks more like a FreeBSD related > problem on current or stable. > > I think it would be good if someone could try to reproduce that with > emulators/virtualbox-ose-legacy which is 3.2.12 to get some vbox dev > look into the problem again. FreeBSD just started honoring this setting in the BIOS this week and ignored it previously. Can you get an acpidump from within VirtaulBox? I might be able to point to a bug in it directly if so. -- John Baldwin