From: Gerd Hoffmann <kraxel@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Programmingkid <programmingkidx@gmail.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Speed menu for GTK interfaace
Date: Wed, 04 Jan 2017 21:55:13 +0100 [thread overview]
Message-ID: <1483563313.8627.6.camel@redhat.com> (raw)
In-Reply-To: <20170104155116.GG10541@redhat.com>
Hi,
> > We already have "pause" in gtk, adding a "throttle" item next to it
> > looks reasonable to me. I don't think it is that useful to have 10%
> > steps in there, you probably never throttle 10% in practice. It's
> > probably more useful to have something like "throttle -> off / 50% /
> > 90% / 95% / 99%".
>
> This feels like going down the slippery slope to turn the GTK frontend
> into a full mgmt UI, which is something we've said we don't want todo
> inside QEMU UI frontends. IMHO this kind of feature is best left to
> external mgmt layers, like virt-manager/GNOME Boxes/etc. It is already
> possible to timebox VMs CPU execution using cgroups quotas via libvirt.
Well, except that libvirt doesn't support gtk. And gtk is what you get
by default when using qemu ad-hoc, without libvirt. Adding features to
gtk which make sense in that context still looks useful to me.
Alternatively we could add qmp+hmp commands for cpu throttling, that way
libvirt can support the feature and with gtk it can be used too, via
monitor tab, even in case we don't create new menu items for it.
cheers,
Gerd
prev parent reply other threads:[~2017-01-04 20:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 18:15 [Qemu-devel] Speed menu for GTK interfaace Programmingkid
2017-01-03 8:59 ` Gerd Hoffmann
2017-01-03 16:37 ` Programmingkid
2017-01-04 8:37 ` Gerd Hoffmann
2017-01-04 15:43 ` Programmingkid
2017-01-04 15:51 ` Daniel P. Berrange
2017-01-04 16:01 ` Programmingkid
2017-01-04 16:19 ` Daniel P. Berrange
2017-01-04 16:22 ` Programmingkid
2017-01-04 20:55 ` Gerd Hoffmann [this message]
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=1483563313.8627.6.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=berrange@redhat.com \
--cc=programmingkidx@gmail.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).