From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36482) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YyQ1s-0001Le-Tf for qemu-devel@nongnu.org; Fri, 29 May 2015 15:33:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YyQ1p-0002ZN-NB for qemu-devel@nongnu.org; Fri, 29 May 2015 15:33:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45958) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YyQ1p-0002ZJ-Ip for qemu-devel@nongnu.org; Fri, 29 May 2015 15:33:13 -0400 Message-ID: <5568BEF5.8020501@redhat.com> Date: Fri, 29 May 2015 21:33:09 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <2816EEF2-0256-4B49-8811-74EFB3016CD4@livius.net> <556848A3.6010905@redhat.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC] extensions to the -m memory option List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Liviu Ionescu Cc: qemu-devel@nongnu.org On 29/05/2015 21:27, Liviu Ionescu wrote: >> If the flash is persistent, it should be tied to either "-pflash" >> (NOR) or "-mtd" (NAND). Just using a different image then >> results in resizing the flash. > > I did not try the resizing mechanism, but I don't think it is > appropriate, one of my use cases is to start QEMU as GDB server, > without any image specified on the command line, and in this case the > flash size needs to be known in advance, I doubt the it can resize > when the image is loaded by the GDB client. You can use -drive if=mtd,snapshot=on,file=null-co://,file.size=128K to start QEMU with a zero 128K NOR flash. Paolo