qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] KVM call minutes for Feb 22
Date: Tue, 22 Feb 2011 18:06:22 +0200	[thread overview]
Message-ID: <20110222160622.GA7048@redhat.com> (raw)

Looks like Chris will send minutes too,
so I didn't do much to polish this,
I didn't realise he's doing it until I had this, so
here's the braindump: hope it helps.

1. 0.14 postmortem
- what went well
	wiki for planning
	testing
- what can be improved
	rc - cycle could be longer

2. 0.15 should be end of June
   July 1?
   - features:
     QED
     other?
     virtagent? might be blocked by the rpc issue (discussion followed)

3. virtagent rpc
     what should virtagent use to talk to the world outside of QEMU?
     Generalize QMP?
     Use an external rpc library?
     Do we want to/can we have virtagent out of process?
     Hard to make well with live migration.
     Would be the most beneficial if we can make it stateless.
     Might be good for security but hard to integrate.

4. qcow3
     there will be a wiki with features we want there

5. google summer of code
	we only have 3 projects
	need more projects/mentors, we have another week

6. switch from gpxe to ipxe
	needed to get patches applied
	we'll likely switch
	need some testing
	might be possible by 0.15

-- 
MST

             reply	other threads:[~2011-02-22 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22 16:06 Michael S. Tsirkin [this message]
2011-02-22 17:32 ` [Qemu-devel] KVM call minutes for Feb 22 Alon Levy
2011-02-22 18:14   ` Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2011-02-22 16:42 Chris Wright

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=20110222160622.GA7048@redhat.com \
    --to=mst@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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).