From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NAkvf-00082F-Gh for qemu-devel@nongnu.org; Wed, 18 Nov 2009 08:50:39 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NAkvY-0007yj-Ld for qemu-devel@nongnu.org; Wed, 18 Nov 2009 08:50:37 -0500 Received: from [199.232.76.173] (port=43647 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NAkvY-0007yT-AP for qemu-devel@nongnu.org; Wed, 18 Nov 2009 08:50:32 -0500 Received: from mx1.redhat.com ([209.132.183.28]:46608) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NAkvX-0003zV-Mf for qemu-devel@nongnu.org; Wed, 18 Nov 2009 08:50:31 -0500 Message-ID: <4B03FB9C.8040407@redhat.com> Date: Wed, 18 Nov 2009 15:50:20 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Stack corruption problem with SeaBIOS/gPXE under QEMU References: <4AFBEF9A.5010802@redhat.com> <20091114194745.GA12007@morn.localdomain> <4B01555B.1030109@redhat.com> <4B015B6C.4090000@redhat.com> <20091117022620.GA25962@morn.localdomain> <20091118093949.GA18543@redhat.com> In-Reply-To: <20091118093949.GA18543@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: qemu-devel@nongnu.org, Glauber Costa , Kevin O'Connor , gpxe@etherboot.org, Naphtali Sprei On 11/18/2009 11:39 AM, Gleb Natapov wrote: > >> Hi Avi, >> >> Can you send the full qemu command line that you used? I can't seem >> to reproduce this on my setup. >> >> I do see an issue if SeaBIOS's reboot vector is called (eg, by using >> "sendkey ctrl-alt-delete" while still in the bios) because seabios >> allows gpxe to modify itself, and on a seabios only reboot the gpxe >> rom isn't recopied and gpxe therefore gets confused. However, on a >> linux invoked reboot, it looks like a full machine reset occurs and >> qemu recopies the gpxe rom, so that doesn't seem to be an issue. >> >> > Do we have the same problem with tpr patching rom (vapic,bin)? It modifies > itself too. > But a reset will reload it. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.