From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55117) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VBMLv-0002TM-FZ for qemu-devel@nongnu.org; Mon, 19 Aug 2013 06:06:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VBMLp-0000OY-DB for qemu-devel@nongnu.org; Mon, 19 Aug 2013 06:06:23 -0400 Received: from mx1.redhat.com ([209.132.183.28]:4375) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VBMLp-0000OP-5C for qemu-devel@nongnu.org; Mon, 19 Aug 2013 06:06:17 -0400 Message-ID: <5211EE15.3060207@redhat.com> Date: Mon, 19 Aug 2013 12:06:13 +0200 From: Michal Privoznik MIME-Version: 1.0 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> <20130819090639.GB6578@redhat.com> In-Reply-To: <20130819090639.GB6578@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [libvirt] [PATCH] qemu: Drop qemuDomainMemoryLimit List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: libvir-list@redhat.com, QEMU Developers , Anthony Liguori On 19.08.2013 11:06, Daniel P. Berrange wrote: > 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 > Okay, I've pushed the patch. And I've just proposed patch to discourage users setting this limit: https://www.redhat.com/archives/libvir-list/2013-August/msg00820.html Michal