From: Eric Blake <eblake@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Adding Save States menu items
Date: Thu, 6 Oct 2016 15:26:15 -0500 [thread overview]
Message-ID: <72e25dca-06f2-b115-bc75-6ba0ea21eb97@redhat.com> (raw)
In-Reply-To: <E1B0C1E4-2094-4994-A5C2-DB9766DD68FF@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1805 bytes --]
On 10/06/2016 03:10 PM, Programmingkid wrote:
>
> On Oct 6, 2016, at 3:59 PM, Eric Blake wrote:
>
>> On 10/06/2016 09:22 AM, Programmingkid wrote:
>>> Would you accept a patch that added "Save State" and "Restore State" menu items to the cocoa interface? They would allow the user to save the running state of the emulator.
>>
>> Doesn't virt-manager already do this? What do we gain by duplicating
>> GUI functionality at this level that is already implemented at higher
>> levels? Not that I'm opposed to the idea, but having a solid reason why
>> it is useful is important.
>
> Virt-manager is a Linux exclusive. This program doesn't run on Windows or
> Mac OS.
Not true. I've seen it ported to Windows, and I'm sure Cole would
welcome a port to Mac.
> The savevm feature is anything but perfect, but that doesn't mean we
> shouldn't provide easy access to it. This feature is already there in
> QEMU, so why not help the user be able to use it?
If you want to HELP the user, then tell them to use a management app
that has already dealt with the problems of consistent snapshots, rather
than making the user reinvent it themselves by clicking a gui button
that does incomplete work.
Yes, qemu has a gui. But I maintain that it is mostly a mistake, and
that time spent improving the gui in this project, rather than porting
and improving better upper-layer guis, is probably wasted. The Unix
philosophy is "do one thing and do it well" - we don't always live up to
it, but on THIS mailing list, the thing we do well is emulation, not
guis. You are going to be hard-pressed to find reviewers, even if you
spend time solving the technical issues.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-10-06 20:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 14:22 [Qemu-devel] Adding Save States menu items Programmingkid
2016-10-06 14:28 ` Peter Maydell
2016-10-06 14:42 ` Programmingkid
2016-10-06 15:35 ` Paolo Bonzini
2016-10-06 15:48 ` Programmingkid
2016-10-06 15:49 ` Paolo Bonzini
2016-10-06 16:04 ` Programmingkid
2016-10-06 16:17 ` Paolo Bonzini
2016-10-06 17:43 ` Programmingkid
2016-10-06 17:49 ` Peter Maydell
2016-10-06 17:51 ` Programmingkid
2016-10-06 20:03 ` Eric Blake
2016-10-06 19:59 ` Eric Blake
2016-10-06 20:10 ` Programmingkid
2016-10-06 20:26 ` Eric Blake [this message]
2016-10-07 7:21 ` Paolo Bonzini
2016-10-07 9:14 ` Daniel P. Berrange
2016-10-07 14:39 ` Programmingkid
2016-10-06 20:47 ` Peter Maydell
2016-10-06 21:07 ` Programmingkid
2016-10-07 8:46 ` Kevin Wolf
2016-10-07 9:09 ` Daniel P. Berrange
2016-10-07 14:55 ` Programmingkid
2016-10-07 14:57 ` Daniel P. Berrange
2016-10-07 14:59 ` Peter Maydell
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=72e25dca-06f2-b115-bc75-6ba0ea21eb97@redhat.com \
--to=eblake@redhat.com \
--cc=peter.maydell@linaro.org \
--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).