qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: wdongxu@cn.ibm.com
Subject: [Qemu-devel] [RFC] QEMU Guest and Host channel
Date: Sun, 12 May 2013 23:12:20 +0800	[thread overview]
Message-ID: <518FB154.9080500@linux.vnet.ibm.com> (raw)

Hi,

Now QEMU has a guest agent tool:
http://wiki.qemu.org/Features/QAPI/GuestAgent

Guest agent is used to send "guest agent commands" to agent, and agent 
will do some work and return the results via QMP protocol. Now 
qemu-guest-agent is mainly for single direction: Host->Guest, that is 
users will send command from host to guest.

I think it is useful to extend single direction to two-way protocol. 
Because sometimes, guest OS might have interest in Host's information, 
such as QEMU versions, with/without hardware assist virtualization 
features, host OS versions, host RAM/CPU usage.

Guest and host channel will add a individual command interface called
"qemu-channel", (in the future, it is possible to merge it with qemu-ga).

Usage can be like this:
1) install qemu-channel to guest OS. In windows, it also can be 
installed as a service, like qemu-ga.exe.
2) qemu-channel open a listen socket, waiting for user input.
3) interact with qemu-channel, using socat/nc to send command to 
qemu-channel, such as:
{"execute":"get-host-ramsize"}
4) qemu-channel communicates with QEMU, via a certain transport method. 
QEMU returns the results to qemu-channel.
5) qemu-channel writes result to client.

Since qemu guest agent already has channel/service/commands code, I 
think I can re-use some of them.

Do you have any suggestions or requests about my RFC? Please let me know 
your ideas, thanks in advance. :)

                 reply	other threads:[~2013-05-12 15:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=518FB154.9080500@linux.vnet.ibm.com \
    --to=wdongxu@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wdongxu@cn.ibm.com \
    /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).