qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Re: QEMU GUI-Frontend based on Libvert API
Date: Sun, 23 Jul 2006 11:34:34 -0500	[thread overview]
Message-ID: <pan.2006.07.23.16.34.34.826109@codemonkey.ws> (raw)
In-Reply-To: 20060723113929.GB4412@redhat.com

On Sun, 23 Jul 2006 12:39:29 +0100, Daniel P. Berrange wrote:
>> I have toyed around with the idea of writing an XML-RPC front-end to
>> QEMU (with the idea of bridging the gap for libvirt).  DV also had a
>> patch floating around to add a socket management interface to QEMU
>> (although now there is a TCP character device so I presume his patch is
>> unnecessary).
> 
> If there was a way to enumerate all running QEMU instances on a machine in
> a reasonably fast manner (ie, not reading every single /proc/PID entry),
> the existing QEMU monitor interface exposes enough functionality to
> support most of  libvirt API.

The approach I took was to have all qemu spawning be done through a single
daemon that could keep track of running instances.  In the general case, I
don't think there's a way to do it.

Plus, you want to make sure that each instance has the monitor on some
reconnectable interface.

Regards,

Anthony Liguori

> So the main questions are how to enumerate
> QEMU instances & how to connect to the monitor - UNIX, TCP, or XML-RPC are
> all possible options with plus/minuses. UNIX is nice because you can
> manage security with simple file permissions on the socket. TCP/XML-RPC is
> nice because you can manage VMs remotely - but you'd need to do some kind
> of sensible auth scheme in remote case - unlike Xen which allows anyone to
> connect :-(
> 
> Regards,
> Dan,

  parent reply	other threads:[~2006-07-23 16:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-21 18:37 [Qemu-devel] QEMU GUI-Frontend based on Libvert API Evan Paul
2006-07-21 19:21 ` [Qemu-devel] " Anthony Liguori
2006-07-21 19:58   ` Joe Lee
2006-07-21 20:57     ` [Qemu-devel] " Anthony Liguori
2006-07-21 21:15       ` Linas Žvirblis
2006-07-21 22:01         ` [Qemu-devel] " Anthony Liguori
2006-07-21 22:37           ` Linas Žvirblis
2006-07-23 11:39   ` [Qemu-devel] " Daniel P. Berrange
2006-07-23 15:24     ` Evan Paul
2006-07-24 10:38       ` Daniel P. Berrange
2006-07-23 16:34     ` Anthony Liguori [this message]
2006-07-24 17:01       ` [Qemu-devel] " James Olsen
2006-07-26 12:47   ` [Qemu-devel] " Daniel Veillard

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=pan.2006.07.23.16.34.34.826109@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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).