From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=37128 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Prul1-0006B6-2M for qemu-devel@nongnu.org; Tue, 22 Feb 2011 11:06:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Prukz-00080H-Tl for qemu-devel@nongnu.org; Tue, 22 Feb 2011 11:06:34 -0500 Received: from mx1.redhat.com ([209.132.183.28]:19781) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Prukz-000807-Hm for qemu-devel@nongnu.org; Tue, 22 Feb 2011 11:06:33 -0500 Date: Tue, 22 Feb 2011 18:06:22 +0200 From: "Michael S. Tsirkin" Message-ID: <20110222160622.GA7048@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Qemu-devel] KVM call minutes for Feb 22 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: kvm@vger.kernel.org Cc: qemu-devel@nongnu.org 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