From: Anthony Liguori <anthony@codemonkey.ws>
To: Glauber Costa <glommer@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Mulyadi Santosa <mulyadi.santosa@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] new SDL keyboard shortcuts to start and stop VM
Date: Wed, 21 Oct 2009 13:08:44 -0500 [thread overview]
Message-ID: <4ADF4E2C.204@codemonkey.ws> (raw)
In-Reply-To: <5d6222a80910211004ldd75525m7dc1b957faf7041@mail.gmail.com>
Glauber Costa wrote:
> On Wed, Oct 21, 2009 at 2:55 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
>
>> Glauber Costa wrote:
>>
>>> Why don't we provide a mechanism to make a macro out of a sequence of
>>> monitor commands, and let the user assign whatever he wants out of that?
>>>
>>>
>> Really? This seems exceedingly complicated to me.
>>
>> Redirecting the kernel output to serial and logging is a considerably better
>> solution.
>>
> To his specific problem, yes.
>
> But this probably don't work so well on some OSes that are less serial friendly.
> Also, there are valid use cases in which one may want, for example, to pause
> fast if some graphical event happens, which is an extension of what he mentioned
> initially.
>
Then type "stop" in the monitor and hit enter when you need to. Or,
write a simple VNC client using gtk-vnc that can have any sort of crazy
key sequences you want.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-10-21 18:08 UTC|newest]
Thread overview: 43+ 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 ` [Qemu-devel] " Kevin Wolf
2009-10-23 11:23 ` 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 [this message]
2009-10-22 7:58 ` Kevin Wolf
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=4ADF4E2C.204@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=glommer@gmail.com \
--cc=kwolf@redhat.com \
--cc=mulyadi.santosa@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).