qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "John R. Hogerhuis" <jhoger@pobox.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU feature idea: simple macros/scripting
Date: Thu, 30 Sep 2004 20:40:09 -0700	[thread overview]
Message-ID: <1096602009.10585.62.camel@aragorn> (raw)
In-Reply-To: <Pine.LNX.4.58.0410010216020.5953@wgmdd8.biozentrum.uni-wuerzburg.de>

On Thu, 2004-09-30 at 17:19, Johannes Schindelin wrote:

> I started to write a vnc frontend for QEmu. On the other end, I started to
> write a scriptable vnc viewer. The use of this? Macros/Scripting for QEmu,
> but also Macros/Scripting for everything which can be controlled by a
> vncviewer. For now, I use an adaption of vncrec, which just records inputs
> and timestamps, and play those inputs back later.

Sounds like your solution would work for me as well. I hadn't thought of
using vnc and related tools.

I'm not sure what kind of integration makes sense, if any.

A record/playback feature could be

1) In QEMU proper wedged between the QEMU and the guest, hooked into the
data traffic
2) In a front end to QEMU which just communicates through a
to-be-implemented API; basically still #1 just architecturally different
3) In a completely separate utility that knows nothing about QEMU and
just deals with X. Such utilities exist for X
4) In a VNC viewer
5) In the guest only; such utilities exist for Windows and probably some
other OSes.

Not sure what the pros/cons are exactly. (5) can be ruled out since you
wouldn't be able to script at the QEMU level (saving/loading system
state images and such, and not all OSes necessarily have good utilities
for recording and playing back such events.

-- John.

  reply	other threads:[~2004-10-01  3:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 23:55 [Qemu-devel] QEMU feature idea: simple macros/scripting John R. Hogerhuis
2004-10-01  0:19 ` Johannes Schindelin
2004-10-01  3:40   ` John R. Hogerhuis [this message]
2004-10-01  9:54     ` Johannes Schindelin
2004-10-02  4:58       ` John R. Hogerhuis
2004-10-01  7:09   ` Lionel Ulmer
2004-10-01 10:08     ` Johannes Schindelin

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=1096602009.10585.62.camel@aragorn \
    --to=jhoger@pobox.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).