From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37965) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1vhq-0006Q2-88 for qemu-devel@nongnu.org; Wed, 24 Jul 2013 05:50:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V1vhn-0006x5-GO for qemu-devel@nongnu.org; Wed, 24 Jul 2013 05:50:02 -0400 Received: from mx1.redhat.com ([209.132.183.28]:8273) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1vhn-0006vc-9U for qemu-devel@nongnu.org; Wed, 24 Jul 2013 05:49:59 -0400 Date: Wed, 24 Jul 2013 12:51:16 +0300 From: "Michael S. Tsirkin" Message-ID: <20130724095116.GB26778@redhat.com> References: <20130724060104.GA18072@redhat.com> <51EF7BDF.2070503@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51EF7BDF.2070503@redhat.com> 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: Gerd Hoffmann Cc: Anthony Liguori , Eduardo Habkost , qemu-devel@nongnu.org, Isaku Yamahata , Alex Williamson , Paolo Bonzini , Laszlo Ersek , Andreas =?iso-8859-1?Q?F=E4rber?= , David Gibson 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. Will this address your comment?