From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42848) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VBLQL-00034i-Qk for qemu-devel@nongnu.org; Mon, 19 Aug 2013 05:06:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VBLQE-0003rc-Nv for qemu-devel@nongnu.org; Mon, 19 Aug 2013 05:06:53 -0400 Received: from mx1.redhat.com ([209.132.183.28]:60653) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VBLQE-0003rM-Fx for qemu-devel@nongnu.org; Mon, 19 Aug 2013 05:06:46 -0400 Date: Mon, 19 Aug 2013 10:06:40 +0100 From: "Daniel P. Berrange" Message-ID: <20130819090639.GB6578@redhat.com> References: <5204EB16.8020801@redhat.com> <20130809131759.GB2868@redhat.com> <5204EEA9.1010002@redhat.com> <87haeysvnk.fsf@codemonkey.ws> <20130809162957.GK2868@redhat.com> <5211D756.4070906@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <5211D756.4070906@redhat.com> Subject: Re: [Qemu-devel] [libvirt] [PATCH] qemu: Drop qemuDomainMemoryLimit Reply-To: "Daniel P. Berrange" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michal Privoznik Cc: libvir-list@redhat.com, QEMU Developers , Anthony Liguori On Mon, Aug 19, 2013 at 10:29:10AM +0200, Michal Privoznik wrote: > On 09.08.2013 18:29, Daniel P. Berrange wrote: > > On Fri, Aug 09, 2013 at 10:58:55AM -0500, Anthony Liguori wrote: > >> Michal Privoznik writes: > >> > >>> [CC'ing qemu-devel list] > >>> On 09.08.2013 15:17, Daniel P. Berrange wrote: > >>>> On Fri, Aug 09, 2013 at 07:13:58AM -0600, Eric Blake wrote: > >>>>> On 08/09/2013 06:56 AM, Michal Privoznik wrote: > > > So what's the conclusion? Should I push the patch until qemu gets > stabilized in mem consumption (which can take a while - no offense to > qemu devels, I can imagine it's nontrivial). Given the lack of any useful info to make memory limits work reliably, I guess we don't have any choice but to remove this default memory limit, and also recommend against people setting explicit memory limits too. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|