From: Chris Wright <chrisw@redhat.com>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] KVM call minutes for May 18
Date: Tue, 18 May 2010 07:29:25 -0700 [thread overview]
Message-ID: <20100518142925.GA21120@x200.localdomain> (raw)
0.13 release
- push out to July 1st
- esp. important to solidy/crispen QMP
- 1 rc to shake out brown paper bag bugs, then final release
block i/o performance (high CPU consumption)
- memset can be removed (patch posted, queued by kwolf)
- cpu_physical_memory_rw known, should gather data
block 1TB limit
- sounds like integer issue
- bug report needs to be updated (verify it's still happening in 0.12.4?
- should be able to easily reproduce (can use lvm to create sparse volume)
sourceforge bug tracker...
- sucks
- unclear if there's active triage
- anthony prefers the launchpad instance
- alex likes the sf email to list, wuld be good to keep that feature
- had to migrate existing bugs (be nice if we could stop sf from growing)
- need more people involved w/ bug work
- possible bug-day before next release
- suggested June 1st
0.12.4 bugs
- migration regression...follow-up on email, open a bug ;-)
next reply other threads:[~2010-05-18 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 14:29 Chris Wright [this message]
2010-05-18 21:34 ` [Qemu-devel] Re: KVM call minutes for May 18 Brian Jackson
2010-05-18 22:08 ` Anthony Liguori
2010-05-19 17:02 ` Avi Kivity
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=20100518142925.GA21120@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).