From: Fabrice Bellard <fabrice@bellard.org>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] QEMU Dbus support - a proposal management API
Date: Tue, 11 Dec 2007 17:10:25 +0100 [thread overview]
Message-ID: <475EB671.7070803@bellard.org> (raw)
In-Reply-To: <20071211154441.GH17368@redhat.com>
Daniel P. Berrange wrote:
> On Tue, Dec 11, 2007 at 09:16:43AM +0200, Yuval Kashtan wrote:
>> - This is very useful when you want to manage and control QEMU, for instance
>> developing a GUI to attach and detach usb devices or controlling more than
>> one instance of QEMU from a single management point, receiving parameters
>> externally and more.
>
> This capability is already possible using the monitor API. I've implemented
> it in libvirt, and in virt-manager and can easily hotplug/remove USB devices.
> So DBus is not required to do this and does not really make it any easier
> to use. DBus is very verbose to use from languages like C, so switching from
> the monitor to DBus API would not really help simplify my existing code. On
> the other hand, having a library providing a simple client side C API to
> send & receive monitor commands, would be beneficial
For the short term I think it is better as you said to rely on libvirt
which already has some support for QEMU.
As it was suggested, improving the monitor seems the easiest, maybe with
an additionnal mode to provide a standardized way to get a return value
for each command. Providing an example client code to directly use the
monitor seems a good idea too.
Regarding the configuration, I can assure there will be soon a QEMU
configuration file. The question is whether it will be included before
the next release is out !
Regards,
Fabrice.
next prev parent reply other threads:[~2007-12-11 16:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 8:28 [Qemu-devel] [RFC] QEMU Dbus support - a proposal management API Yuval Kashtan
2007-12-10 20:51 ` Blue Swirl
2007-12-11 7:16 ` Yuval Kashtan
2007-12-11 9:10 ` Fabrice Bellard
2007-12-11 9:23 ` Laurent Vivier
2007-12-11 10:06 ` Brad Campbell
2007-12-11 10:07 ` Dor Laor
2007-12-11 14:51 ` Anthony Liguori
2007-12-11 15:00 ` Daniel P. Berrange
2007-12-11 15:21 ` Yuval Kashtan
2007-12-11 15:31 ` Daniel P. Berrange
2007-12-11 15:36 ` Anthony Liguori
2007-12-11 15:59 ` Avi Kivity
2007-12-11 16:18 ` Paul Brook
2007-12-11 16:40 ` Avi Kivity
2007-12-11 15:02 ` Daniel P. Berrange
2007-12-11 15:15 ` Anthony Liguori
2007-12-11 15:40 ` Richard W.M. Jones
2007-12-11 15:48 ` Anthony Liguori
2007-12-11 15:58 ` Daniel P. Berrange
2007-12-11 16:49 ` Anthony Liguori
2007-12-11 17:04 ` Daniel P. Berrange
2007-12-11 15:59 ` Dor Laor
2007-12-11 15:17 ` Jean-Christian de Rivaz
2007-12-11 15:24 ` Daniel P. Berrange
2007-12-11 10:20 ` Andreas Färber
2007-12-11 10:29 ` Laurent Vivier
2007-12-11 10:50 ` Andreas Färber
2007-12-11 10:21 ` Heikki Lindholm
2007-12-11 11:05 ` Avi Kivity
2007-12-11 14:43 ` Anthony Liguori
2007-12-11 14:56 ` Daniel P. Berrange
2007-12-11 15:57 ` Avi Kivity
2007-12-11 16:07 ` Richard W.M. Jones
2007-12-11 15:44 ` Daniel P. Berrange
2007-12-11 16:10 ` Fabrice Bellard [this message]
2007-12-11 14:53 ` Daniel P. Berrange
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=475EB671.7070803@bellard.org \
--to=fabrice@bellard.org \
--cc=berrange@redhat.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).