From: Perry Myers <pmyers@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: Chris Wright <chrisw@redhat.com>,
Juan Quintela <quintela@redhat.com>,
"libvir-list@redhat.com" <libvir-list@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Russell Bryant <rbryant@redhat.com>,
"arch@ovirt.org" <arch@ovirt.org>
Subject: Re: [Qemu-devel] Guest Agent Summaries
Date: Mon, 05 Dec 2011 23:21:54 -0500 [thread overview]
Message-ID: <4EDD9862.4000509@redhat.com> (raw)
In-Reply-To: <4EDD397B.8090709@linux.vnet.ibm.com>
On 12/05/2011 04:36 PM, Michael Roth wrote:
> On 12/05/2011 01:21 PM, Chris Wright wrote:
>> * Chris Wright (chrisw@redhat.com) wrote:
>>> * Anthony Liguori (aliguori@us.ibm.com) wrote:
>>>> 1. A short introduction to each of the guest agents, what guests they
>>>> support, and what verbs they support.
>>>
>>> I think we did this once before w/ Matahari. Can we please capture
>>> these things in email before the call, so people actually have time
>>> to ponder the details.
>>>
>>>> 2. A short description of key requirements from each party (oVirt,
>>>> libvirt,
>>>> QEMU) for a guest agent
>>>
>>> Same here...call this the abstract/intro of the above detailed list of
>>> verbs and guest support, and send it by Friday this week.
>>>
>>> I know there's plenty of details buried in the current thread and old
>>> discussions of Matahari. But that's just it...buried...
>>
>> It's past Friday. Barak's links are all we have so far...
>
> Sorry this slipped by me. However, Barak's link to the guest agent
> proposals:
>
> http://www.ovirt.org/wiki/Guest_agent_proposals
>
> is a summary of the recent discussion on guest agents for oVirt from the
> following thread:
>
> http://thread.gmane.org/gmane.comp.emulators.ovirt.vdsm.devel/93/focus=93
>
> Requirements were posted there for oVirt (ovirt-guest-agent), QEMU
> (qemu-ga), and Spice (vdagent) and pulled into wiki, so as far as
> requirements go that is probably the best summary available at the
> moment. There is also summary of the current proposals for how to go
> about leveraging ovirt-guest-agent or qemu-ga for oVirt/QEMU requirements.
>
> Matahari was mentioned only in brief since it didn't come up much in
> that particular discussion, but feel free to add as a response to this
> email and I can add it to the wiki so we can start getting all this
> stuff in one place.
Matahari really isn't a candidate for a lightweight guest agent for
virtualization because of the heavy dependency chain. So it's not
really in contention with ovirt guest agent or qemu guest agent.
Matahari will continue to be developed for general systems management
functionality, but it doesn't need to be further considered for this
specific usage.
next prev parent reply other threads:[~2011-12-06 4:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 14:36 [Qemu-devel] KVM Call Agenda for 12/6 (Tuesday) @ 10am US/Eastern Anthony Liguori
2011-11-30 14:56 ` Barak Azulay
2011-11-30 16:29 ` Chris Wright
2011-11-30 16:36 ` Anthony Liguori
2011-12-05 19:21 ` Chris Wright
2011-12-05 21:36 ` [Qemu-devel] Guest Agent Summaries Michael Roth
2011-12-06 4:21 ` Perry Myers [this message]
2011-12-07 9:15 ` [Qemu-devel] [libvirt] " Alon Levy
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=4EDD9862.4000509@redhat.com \
--to=pmyers@redhat.com \
--cc=arch@ovirt.org \
--cc=chrisw@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rbryant@redhat.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).