From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:54645) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SWWnh-0007oM-3I for qemu-devel@nongnu.org; Mon, 21 May 2012 13:53:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SWWnf-0004ea-BD for qemu-devel@nongnu.org; Mon, 21 May 2012 13:53:44 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47975) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SWWnf-0004eL-2n for qemu-devel@nongnu.org; Mon, 21 May 2012 13:53:43 -0400 Date: Mon, 21 May 2012 13:53:36 -0400 From: Jason Baron Message-ID: <20120521175335.GD3353@redhat.com> References: <201205042123.q44LNp9x029061@int-mx01.intmail.prod.int.phx2.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201205042123.q44LNp9x029061@int-mx01.intmail.prod.int.phx2.redhat.com> Subject: Re: [Qemu-devel] [PATCH] memory: add -dont-dump-guest option to reduce core dump size List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: avi@redhat.com Cc: qemu-devel@nongnu.org On Fri, May 04, 2012 at 05:23:51PM -0400, Jason Baron wrote: > Add a command line parameter to not dump guest memory in the core dump, the > command line is: -dont-dump-guest. This brought the core dump down from > 383MB to 13 MB on a 1GB guest. > > Signed-off-by: Jason Baron > --- > exec.c | 13 +++++++++++++ > osdep.h | 7 +++++++ > qemu-options.hx | 5 +++++ > sysemu.h | 1 + > vl.c | 4 ++++ > 5 files changed, 30 insertions(+), 0 deletions(-) > Any thoughts on this? Is the guest memory often helpful in debugging when the qemu process segfaults? This feature also seems useful if somebody is running a sensitive workload, such that the non-sensitive qemu state can be dumped independently of the guest state. In that case, perhaps there should also be an option that allows the guest to be dumped on a segfault, now separately? Thanks, -Jason