qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Linas Žvirblis" <0x0007@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: wxWidgets and C: was Re: [Qemu-devel] QEMU GUI
Date: Tue, 11 Jul 2006 18:29:17 +0300	[thread overview]
Message-ID: <44B3C3CD.8090307@gmail.com> (raw)
In-Reply-To: <44B3BB46.8030004@gmx.de>

Oliver Gerlich wrote:

> Personally, I'd be interested to have a GUI for controlling a running
> Qemu instance: change CD-ROM, add/remove USB devices, save/restore VM
> snapshots (though this would also require to save/restore disk
> snapshots), and eg. provide buttons to switch between guest Virtual
> Terminals. 

Already exists at <http://qemuctl.sourceforge.net/>. I am not sure if it
is developed anymore, but I am going to integrate it into my own
project, in the nearest future.

> Furthermore, I'd like to get information like guest CPU usage
> and guest hard disk access; this would probably require that the GUI is
> integrated into Qemu.

Not if this data is available via monitor. And I certainly want it to
be, as this is one of the coolest features.

> Configuration could still be done with the current command line flags,
> but if one of the many config GUIs could be integrated into Qemu, that
> might be useful as well.

None of them (at least the ones I know) are written in C, so integrating
them _into_ QEMU is not really possible. And I absolutely fail to see
the reason for doing so.

If there is a need for an official GUI, choose one, write yet another,
but, please, do not enforce things on users. The current situation works
quite well for projects like cdrtools so why should it not work for QEMU?

  reply	other threads:[~2006-07-11 15:29 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 18:11 [Qemu-devel] QEMU GUI Fabrice Bellard
2006-06-21 19:42 ` Mike Kronenberg
2006-06-22 19:32   ` gbeauchesne
2006-06-22 19:32   ` gbeauchesne
2006-06-28 23:03     ` Joe Lee
2006-06-29 13:19       ` Daniel P. Berrange
2006-06-29 21:05         ` Joe Lee
2006-06-29 21:47           ` Daniel P. Berrange
2006-06-22 15:06 ` Luca Barbato
2006-07-01 22:47   ` Chris Wilson
2006-07-05 20:51     ` Luca Barbato
2006-07-08  2:14       ` Chris Wilson
2006-07-08  2:46         ` Johannes Schindelin
2006-07-08  6:34           ` M. Warner Losh
2006-07-08 14:34             ` wxWidgets and C: was " Jim C. Brown
2006-07-08 15:02               ` Joe Lee
2006-07-08 15:13                 ` Jim C. Brown
2006-07-08 16:34                   ` Kevin F. Quinn
2006-07-08 21:26               ` Oliver Gerlich
2006-07-10  0:03                 ` John R.
2006-07-10  0:10                   ` Jim C. Brown
2006-07-11  7:44                   ` David Fraser
2006-07-11 12:40                     ` Jason Gress
2006-07-11 13:17                       ` Linas Žvirblis
2006-07-11 14:52                         ` Oliver Gerlich
2006-07-11 15:29                           ` Linas Žvirblis [this message]
2006-07-12  8:17         ` Luca Barbato
2006-07-12 13:15           ` [Qemu-devel] Insert module into kernel Tieu Ma Dau
2006-07-12 13:36             ` Paul Brook
2006-07-13  8:11               ` Tieu Ma Dau
2006-06-22 15:18 ` [Qemu-devel] QEMU GUI Christian MICHON
2006-06-30 10:28   ` Dan Sandberg
2006-06-22 21:50 ` Anthony Liguori
2006-06-23  0:18   ` Kevin F. Quinn
2006-06-23  1:53     ` Anthony Liguori
2006-06-23  7:17       ` Kevin F. Quinn

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=44B3C3CD.8090307@gmail.com \
    --to=0x0007@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).