From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41079) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1vzY-0003D1-2G for qemu-devel@nongnu.org; Wed, 24 Jul 2013 06:08:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V1vzW-000576-8n for qemu-devel@nongnu.org; Wed, 24 Jul 2013 06:08:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:65105) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1vzV-00056s-Vh for qemu-devel@nongnu.org; Wed, 24 Jul 2013 06:08:18 -0400 Date: Wed, 24 Jul 2013 12:08:09 +0200 From: Igor Mammedov Message-ID: <20130724120809.71415f59@nial.usersys.redhat.com> In-Reply-To: <20130724095116.GB26778@redhat.com> References: <20130724060104.GA18072@redhat.com> <51EF7BDF.2070503@redhat.com> <20130724095116.GB26778@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] pc: limit 64 bit hole to 2G by default List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Anthony Liguori , Eduardo Habkost , qemu-devel@nongnu.org, Isaku Yamahata , Alex Williamson , Gerd Hoffmann , Paolo Bonzini , Laszlo Ersek , Andreas =?ISO-8859-1?B?RuRyYmVy?= , David Gibson On Wed, 24 Jul 2013 12:51:16 +0300 "Michael S. Tsirkin" wrote: > On Wed, Jul 24, 2013 at 09:01:51AM +0200, Gerd Hoffmann wrote: > > On 07/24/13 08:01, Michael S. Tsirkin wrote: > > > It turns out that some 32 bit windows guests crash > > > if 64 bit PCI hole size is >2G. > > > > Ah, *that* is the reason for winxp crashing with a 64bit hole. > > > > Current seabios uses a slightly different approach: the 64bit hole is > > present only in case it is actually used to map bars there, and seabios > > tries to fit everything into the 32bit hole first. > > Yes. But this doesn't work with device hotplug. > > > > Limit it to 2G for piix and q35 by default, > > > add properties to let management override the hole size. > > > > > > Examples: > > > -global i440FX-pcihost.pci_hole64_size=137438953472 > > > > Do we really want specify this in bytes? Using megabytes or gigabytes > > instead looks more sane to me. > > > > cheers, > > Gerd > > I think that arbitrarily saying size is in gigabytes is > confusing to users (in particular because there's no > documentation for properties except their type). > I intend to send a patch to properties that allows writing > "size=1G" instead. for size property you could take patches: [PATCH 04/16] qapi: make visit_type_size fallback to type_int [PATCH 05/16] qdev: Add SIZE type to qdev properties from [PATCH 00/16 RFC v6] ACPI memory hotplug