From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NDYek-0000KW-6c for qemu-devel@nongnu.org; Thu, 26 Nov 2009 02:20:46 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NDYef-0000Hz-2y for qemu-devel@nongnu.org; Thu, 26 Nov 2009 02:20:45 -0500 Received: from [199.232.76.173] (port=35506 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NDYed-0000Ho-TN for qemu-devel@nongnu.org; Thu, 26 Nov 2009 02:20:40 -0500 Received: from mx1.redhat.com ([209.132.183.28]:57111) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NDYed-0000Qz-Ev for qemu-devel@nongnu.org; Thu, 26 Nov 2009 02:20:39 -0500 Date: Thu, 26 Nov 2009 09:20:34 +0200 From: Gleb Natapov Subject: Re: [Qemu-devel] Re: POST failure (loop) with isapc and seabios Message-ID: <20091126072034.GA1990@redhat.com> References: <2D659FA33BF64C419243FD76049AFD33@FSCPC> <20091124062810.GZ2999@redhat.com> <20091124143812.GA27783@shareable.org> <20091124144044.GJ2999@redhat.com> <20091125060951.GA17203@shareable.org> <20091125122039.GM2999@redhat.com> <20091125225349.GA18812@morn.localdomain> <20091126064925.GS2999@redhat.com> <20091126071527.GA29003@morn.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091126071527.GA29003@morn.localdomain> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin O'Connor Cc: qemu-devel@nongnu.org, Sebastian Herbszt On Thu, Nov 26, 2009 at 02:15:27AM -0500, Kevin O'Connor wrote: > On Thu, Nov 26, 2009 at 08:49:25AM +0200, Gleb Natapov wrote: > > On Wed, Nov 25, 2009 at 05:53:49PM -0500, Kevin O'Connor wrote: > > > * If qemu does reload the bios (a hard-reset) then there is a good > > > chance that old DOS programs will break when they invoke a reset in > > > an attempt to switch from protected mode to real mode. > > > > > > Is that correct? > > > > > Reloading of a BIOS will not prevent old DOS program from working. > > It will slow switch to real mode, but otherwise I see no harm. What may > > prevent them from working is the fact that too much devices are reset on > > triple fault, but this has nothing to do with reloading of a BIOS. > > On a switch to real mode, seabios will detect the code in cmos and > jump directly to the resume vector. Seabios will not reinitialize > itself in this case. > > Now, if the bios is reloaded, the jump to the resume vector will skip > ide, bios table, and other internal state setup. So, later calls to > the bios will likely fail. > Seabios stores .bss and .data section in BIOS segments? If this is the case that you are right. Can we move them somewhere else and add it to e820 map? Although event then switching to real mode using triple fault after migration to newer BIOS will not work properly. -- Gleb.