From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:56248) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rvzqr-0006AU-LP for qemu-devel@nongnu.org; Fri, 10 Feb 2012 18:26:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rvzqq-0002w5-I3 for qemu-devel@nongnu.org; Fri, 10 Feb 2012 18:26:01 -0500 Received: from relay1.mentorg.com ([192.94.38.131]:49897) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rvzqq-0002w1-CS for qemu-devel@nongnu.org; Fri, 10 Feb 2012 18:26:00 -0500 From: Paul Brook Date: Fri, 10 Feb 2012 23:25:53 +0000 References: <4F354883.602@suse.de> In-Reply-To: <4F354883.602@suse.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201202102325.54423.paul@codesourcery.com> Subject: Re: [Qemu-devel] Memory: how to determine the max memory size of one VM? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Zhi Yong Wu , Stefan Hajnoczi , Alexander Graf , Andreas =?iso-8859-1?q?F=E4rber?= , Stefan Weil > There's two slightly different scenarios to consider here: > > i) User specifies command line options that cannot possibly work. > => Ideally, yeah, we should just provide an understandable error message > and exit with error code. > > ii) Some tracing of mine indicates QEMU has a highly dynamic memory > usage during runtime, be it due to network layer, block layer or > whatever exactly. We do? Significant compared to the size of guest ram? That sounds like a bug. I know I've nacked patches before (particularly SCSI ones) because they allocarted memory proportional to the size of the guest block device request. Paul