Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>,
	Developers qemu-devel <qemu-devel@nongnu.org>,
	Libvirt <libvir-list@redhat.com>, arch <arch@ovirt.org>
Cc: Chris Wright <chrisw@redhat.com>
Subject: KVM call agenda for 12/6 (Tuesday) @ 10am US/Eastern
Date: Mon, 05 Dec 2011 15:13:10 +0100	[thread overview]
Message-ID: <87pqg35cp5.fsf@neno.neno> (raw)


Hi

Please send in any agenda items you are interested in covering.

Proposal (from Anthony):

> 1. A short introduction to each of the guest agents, what guests they
> support, and what verbs they support.

> 2. A short description of key requirements from each party (oVirt,
> libvirt, QEMU) for a guest agent

> 3. An open discussion about possible ways to collaborate/converge.

Notice that guest integration will take more than one week (Anthony
estimation also).

For libvirt and ovirt folks, please contact me or Chris for details of
the call.


Thanks, Juan.


                 reply	other threads:[~2011-12-05 14:15 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=87pqg35cp5.fsf@neno.neno \
    --to=quintela@redhat.com \
    --cc=arch@ovirt.org \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=libvir-list@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