From: Chris Wright <chrisw@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 08:42:10 -0800 [thread overview]
Message-ID: <20110222164210.GH20955@x200.localdomain> (raw)
0.14 recap
- keeping schedule on wiki was helpful
- changelog was helpful
- testing (could even more emphasis could be improved)
- -rc cycles
- -rc2 and final release just hours
0.15
- tentative date July 1st
- qapi
- qed features
- virtagent?
- depends on whether to terminate in qemu vs external
- terminating w/in qemu is close to feature complete
- using QMP (kinda, QObject -> JSON marshalling, still use HTTP)
- QMP is not bi-directional XMLRPC, one way with event posting
- XMLRPC + server logic add to the basic QEMU side attack surface
- splitting out to external process
- state associated with guest in external process complicates live migration
- e.g. handling in-process command in server
- guest client reconnects during migration
- can virtagent features be stateless
- Avi's favorite Lua based extension language coming RSN ;)
- let's use copy and paste as a concrete example
- usecase to help define the requirements and expose
architectural
- Jes will do this, make concrete counter proposal to hosting
virtagent server in qemu
- splitting QEMU into more modular components is a large architectural
step, but better step
Block format acceptance
- qcow3 wiki starting
GSoC projects
- only 3 so far, mentoring organization applications Feb 28th
- can update app
- please add your thoughts here so that we can have a successful
- Luiz will send out a note as more explicit reminder
gpxe vs ipxe
- gpxe still stagnate
- ipxe accepting patches (e.g. igbvf)
- perhaps switch in 0.15 (Alex take a look)
next reply other threads:[~2011-02-22 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 16:42 Chris Wright [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-22 16:06 [Qemu-devel] KVM call minutes for Feb 22 Michael S. Tsirkin
2011-02-22 17:32 ` Alon Levy
2011-02-22 18:14 ` Anthony Liguori
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=20110222164210.GH20955@x200.localdomain \
--to=chrisw@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).