qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Juan Quintela <quintela@trasno.org>
Cc: Glauber Costa <glommer@gmail.com>,
	Mulyadi Santosa <mulyadi.santosa@gmail.com>,
	qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: [Qemu-devel] Re: [PATCH] new SDL keyboard shortcuts to start and stop VM
Date: Fri, 23 Oct 2009 09:40:45 +0200	[thread overview]
Message-ID: <4AE15DFD.6050203@redhat.com> (raw)
In-Reply-To: <m33a5bj851.fsf@neno.mitica>

Am 23.10.2009 01:55, schrieb Juan Quintela:
> Anthony Liguori <anthony@codemonkey.ws> wrote:
>> Luiz Capitulino wrote:
>>> On Thu, 22 Oct 2009 10:40:54 -0500
>>> Anthony Liguori <anthony@codemonkey.ws> wrote:
>>>
>>>   
>>>> Luiz Capitulino wrote:
>>>>     
>>>>>  Yeah, I agree.
>>>>>
>>>>>  When testing migration, for example, I have to type 'migrate -d tcp:0:4444'
>>>>> several times... Maybe there's a smarter way to do this, but the monitor
>>>>> macros idea seems interesting to me.
>>>>>         
>>>> When we have QMP, we can create a QMP socket at a well known
>>>> location based on the -name parameter.  We could also introduce a
>>>> qm command that allowed one to execute monitor commands from the
>>>> shell.  That allows people to write whatever crazy shell scripts
>>>> they want.
>>>>     
>>>
>>>  Yes.
>>>
>>>  What about the macros idea? Are you against it?
>>>   
>>
>> I'm concerned that it's a snowball of complexity waiting to happen for
>> very little benefit.
>>
>> I think we're trying to solve a non-existent problem.
> 
> I fully agree.  If we have a had to issue commands to the monitor, we
> can use whatever shell/interpreter/... that we like.

But I can't bind a keyboard shortcut to such a script which is exactly
what this thread is about... What I want to have in the end is my "VM
stop" shortcut, dynamically binding keys to monitor commands is just a
way to achieve this.

I really hate this "You don't need this, I know it better" attitude. If
it were only for the technical arguments, okay - I can understand that
you don't want to add another magic key, and yes, doing it dynamically
comes with some complexity. But all this talking about "non-existent
problems" makes me think that you don't... really care about what users
want if they are the wrong users (yes, I admit, this one is useful more
likely for developers and plain qemu users than for those running their
servers in KVM - but they are still users, right?)

Kevin

  parent reply	other threads:[~2009-10-23  7:42 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18 16:24 [Qemu-devel] [PATCH] new SDL keyboard shortcuts to start and stop VM Mulyadi Santosa
2009-10-19 22:20 ` Anthony Liguori
2009-10-20  3:16   ` Mulyadi Santosa
2009-10-20  7:58     ` Gerd Hoffmann
2009-10-20  8:12     ` Daniel P. Berrange
2009-10-20 10:40   ` Kevin Wolf
2009-10-20 16:59     ` Anthony Liguori
2009-10-20 17:08     ` Daniel P. Berrange
2009-10-20 22:14       ` Mulyadi Santosa
2009-10-21  7:27       ` Kevin Wolf
2009-10-21 13:52         ` Glauber Costa
2009-10-21 16:04           ` Mulyadi Santosa
2009-10-21 16:24             ` Glauber Costa
2009-10-21 16:44               ` Mulyadi Santosa
2009-10-21 16:48                 ` Glauber Costa
2009-10-21 18:35                 ` Jamie Lokier
2009-10-22 14:40                   ` Luiz Capitulino
2009-10-22 15:02                     ` Kevin Wolf
2009-10-22 16:32                       ` Luiz Capitulino
2009-10-22 15:40                     ` Anthony Liguori
2009-10-22 16:38                       ` Luiz Capitulino
2009-10-22 18:32                         ` Anthony Liguori
     [not found]                           ` <m33a5bj851.fsf@neno.mitica>
2009-10-23  7:40                             ` Kevin Wolf [this message]
2009-10-23 11:23                               ` [Qemu-devel] " Mulyadi Santosa
2009-10-23 11:45                                 ` Kevin Wolf
2009-10-23 13:59                                   ` Anthony Liguori
2009-10-23 14:36                                     ` Kevin Wolf
2009-10-25 15:28                                     ` Avi Kivity
2009-10-25 15:44                                       ` Luiz Capitulino
2009-10-26 13:45                                       ` Anthony Liguori
2009-10-26 14:13                                         ` Avi Kivity
2009-10-26 15:04                                           ` Anthony Liguori
2009-10-26 15:07                                             ` Avi Kivity
2009-10-26 15:49                                               ` Anthony Liguori
2009-10-26 16:08                                                 ` Avi Kivity
2009-10-26 16:17                                                   ` Anthony Liguori
2009-10-27  9:11                                                   ` Gerd Hoffmann
2009-10-27  9:28                                                     ` Avi Kivity
2009-10-21 16:55           ` [Qemu-devel] " Anthony Liguori
2009-10-21 17:01             ` Mulyadi Santosa
2009-10-21 17:04             ` Glauber Costa
2009-10-21 18:08               ` Anthony Liguori
2009-10-22  7:58                 ` Kevin Wolf
     [not found] <E1N2mhd-0003dq-N6@pih-inmx13.plus.net>
2009-10-28  3:11 ` [Qemu-devel] " Gervase Lam

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=4AE15DFD.6050203@redhat.com \
    --to=kwolf@redhat.com \
    --cc=glommer@gmail.com \
    --cc=lcapitulino@redhat.com \
    --cc=mulyadi.santosa@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@trasno.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).