From: "Daniel P. Berrange" <berrange@redhat.com>
To: Michal Privoznik <mprivozn@redhat.com>
Cc: libvir-list@redhat.com, QEMU Developers <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [libvirt] [PATCH] qemu: Drop qemuDomainMemoryLimit
Date: Mon, 19 Aug 2013 10:06:40 +0100 [thread overview]
Message-ID: <20130819090639.GB6578@redhat.com> (raw)
In-Reply-To: <5211D756.4070906@redhat.com>
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 <mprivozn@redhat.com> 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 :|
next prev parent reply other threads:[~2013-08-19 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ad6173415eb6c51c95645e42b4bafa67cac39986.1376052970.git.mprivozn@redhat.com>
[not found] ` <5204EB16.8020801@redhat.com>
[not found] ` <20130809131759.GB2868@redhat.com>
2013-08-09 13:29 ` [Qemu-devel] [libvirt] [PATCH] qemu: Drop qemuDomainMemoryLimit Michal Privoznik
2013-08-09 15:58 ` Anthony Liguori
2013-08-09 16:29 ` Daniel P. Berrange
2013-08-19 8:29 ` Michal Privoznik
2013-08-19 9:06 ` Daniel P. Berrange [this message]
2013-08-19 10:06 ` Michal Privoznik
2013-08-09 16:32 ` Andreas Färber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130819090639.GB6578@redhat.com \
--to=berrange@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=libvir-list@redhat.com \
--cc=mprivozn@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).