From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NCeTO-0003Te-6v for qemu-devel@nongnu.org; Mon, 23 Nov 2009 14:21:18 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NCeTG-0003OY-I3 for qemu-devel@nongnu.org; Mon, 23 Nov 2009 14:21:14 -0500 Received: from [199.232.76.173] (port=59341 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCeTG-0003OU-BK for qemu-devel@nongnu.org; Mon, 23 Nov 2009 14:21:10 -0500 Received: from mail.gmx.net ([213.165.64.20]:37949) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1NCeTE-00027y-IB for qemu-devel@nongnu.org; Mon, 23 Nov 2009 14:21:09 -0500 Message-ID: <11090DAABE9449F7B5D1415C45F8F411@FSCPC> From: "Sebastian Herbszt" References: <20091120225113.GD24539@morn.localdomain> <20091122123503.GH3193@redhat.com> <20091122151052.GK3193@redhat.com> <217FD12D88EA4AC2B2A32D77E010B16C@FSCPC> <20091122153809.GL3193@redhat.com> <8A56C1F849F34911ABF51DE049CA3D24@FSCPC> <20091123111137.GF2999@redhat.com> In-Reply-To: <20091123111137.GF2999@redhat.com> Subject: Re: [Qemu-devel] Re: POST failure (loop) with isapc and seabios Date: Mon, 23 Nov 2009 20:19:54 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: Kevin O'Connor , qemu-devel@nongnu.org Gleb Natapov wrote: > On Sun, Nov 22, 2009 at 09:01:45PM +0100, Sebastian Herbszt wrote: >> Gleb Natapov wrote: >> >On Sun, Nov 22, 2009 at 04:31:24PM +0100, Sebastian Herbszt wrote: >> >> >> >>Bad things could happen if someone modifies the BIOS because it's unprotected >> >>(e.g. VM crash). >> >> >> >BIOS is reloaded during VM reset. >> >> The BIOS is not reloaded - tested with "reboot" on Linux and system_reset in monitor. >> > Looks like a bug. Tested with latest QEMU version I assume? Tested with v0.11.0-rc0-1677-gf165b53. Where do you suspect a bug? In the behaviour on "reboot" or system_reset? I think it depends wheter it's a software or hardware reset. - Sebastian