From: Amit Shah <amit.shah@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: aliguori@linux.vnet.ibm.com, ryanh@us.ibm.com,
agl@linux.vnet.ibm.com, qemu-devel@nongnu.org,
abeekhof@redhat.com
Subject: [Qemu-devel] Re: [RFC][PATCH v3 00/11] virtagent: host/guest RPC communication agent
Date: Thu, 25 Nov 2010 15:09:34 +0530 [thread overview]
Message-ID: <20101125093934.GD6889@amit-x200.redhat.com> (raw)
In-Reply-To: <1289439450-23556-1-git-send-email-mdroth@linux.vnet.ibm.com>
Hi,
On (Wed) Nov 10 2010 [19:37:19], Michael Roth wrote:
> EXAMPLE USAGE:
>
> The commandline options are a little convoluted right now; this will addressed in later revisions.
>
> - Configure guest agent to talk to host via virtio-serial
> # start guest with virtio-serial/virtproxy/virtagent. for example (RHEL6rc1):
> qemu \
> -chardev virtproxy,id=test0,virtagent=on \
> -device virtio-serial \
> -device virtserialport,chardev=test0,name=virtagent0 \
> -monitor stdio
> ...
> # in the guest:
> ./qemu-vp -c virtserial-open:/dev/virtio-ports/virtagent0:- -g
> ...
> # monitor commands
> (qemu) agent_viewdmesg
> [139311.710326] wlan0: deauthenticating from 00:30:bd:f7:12:d5 by local choice (reason=3)
> [139323.469857] wlan0: deauthenticating from 00:21:29:cd:41:ee by local choice (reason=3)
> ...
> [257683.375646] wlan0: authenticated
> [257683.375684] wlan0: associate with AP 00:30:bd:f7:12:d5 (try 1)
> [257683.377932] wlan0: RX AssocResp from 00:30:bd:f7:12:d5 (capab=0x411 status=0 aid=4)
> [257683.377940] wlan0: associated
>
> (qemu) agent_viewfile /proc/meminfo
It would be better to have a command and sub-commands rather than
different commands for viewing different kinds of files:
(qemu) agent view dmesg
(qemu) agent view /proc/meminfo
Amit
prev parent reply other threads:[~2010-11-25 9:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 1:37 [Qemu-devel] [RFC][PATCH v3 00/11] virtagent: host/guest RPC communication agent Michael Roth
2010-11-11 1:37 ` [Qemu-devel] [RFC][PATCH v3 01/11] virtagent: add common rpc transport defs Michael Roth
2010-11-11 1:37 ` [Qemu-devel] [RFC][PATCH v3 02/11] virtagent: base definitions for host/guest RPC server Michael Roth
2010-11-11 1:37 ` [Qemu-devel] [RFC][PATCH v3 03/11] virtagent: qemu-vp, integrate virtagent server Michael Roth
2010-11-11 1:37 ` [Qemu-devel] [RFC][PATCH v3 04/11] virtagent: base RPC client definitions Michael Roth
2010-11-11 1:37 ` [Qemu-devel] [RFC][PATCH v3 05/11] virtagent: add getfile RPC Michael Roth
2010-11-11 1:37 ` [Qemu-devel] [RFC][PATCH v3 06/11] virtagent: add agent_viewfile command Michael Roth
2010-11-11 1:37 ` [Qemu-devel] [RFC][PATCH v3 07/11] virtagent: add getdmesg RPC Michael Roth
2010-11-11 1:37 ` [Qemu-devel] [RFC][PATCH v3 08/11] virtagent: add agent_viewdmesg command Michael Roth
2010-11-11 1:37 ` [Qemu-devel] [RFC][PATCH v3 09/11] virtagent: qemu-vp integration, use virtagent init functions Michael Roth
2010-11-11 1:37 ` [Qemu-devel] [RFC][PATCH v3 10/11] virtagent: qemu integration, add va invocation via virtproxy chardev Michael Roth
2010-11-11 1:37 ` [Qemu-devel] [RFC][PATCH v3 11/11] virtagent: Makefile/configure changes to build virtagent bits Michael Roth
2010-11-25 9:39 ` Amit Shah [this message]
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=20101125093934.GD6889@amit-x200.redhat.com \
--to=amit.shah@redhat.com \
--cc=abeekhof@redhat.com \
--cc=agl@linux.vnet.ibm.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=ryanh@us.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).