From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LY1PH-0004ap-0G for qemu-devel@nongnu.org; Fri, 13 Feb 2009 12:00:51 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LY1PF-0004YJ-1G for qemu-devel@nongnu.org; Fri, 13 Feb 2009 12:00:50 -0500 Received: from [199.232.76.173] (port=40800 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LY1PE-0004Y9-N9 for qemu-devel@nongnu.org; Fri, 13 Feb 2009 12:00:48 -0500 Received: from qw-out-1920.google.com ([74.125.92.147]:51731) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LY1PE-000631-Az for qemu-devel@nongnu.org; Fri, 13 Feb 2009 12:00:48 -0500 Received: by qw-out-1920.google.com with SMTP id 4so315489qwk.4 for ; Fri, 13 Feb 2009 09:00:47 -0800 (PST) Message-ID: <4995A723.9010208@codemonkey.ws> Date: Fri, 13 Feb 2009 11:00:19 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Cutting a new QEMU release References: <4988AD96.6090308@codemonkey.ws> <20090213084023.GA1020@kos.to> <20090213163043.GJ18471@shareable.org> In-Reply-To: <20090213163043.GJ18471@shareable.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Jamie Lokier wrote: > Riku Voipio wrote: > >> On Tue, Feb 03, 2009 at 02:48:22PM -0600, Anthony Liguori wrote: >> >>> We could decide to cut one by the end of the month. >>> >> This would indeed be really cool. >> >> >>> .. to decide if there's anything we need to fix before a release. >>> >> At least the OS X (cocoa) host is broken, which is IMHO pretty >> bad regression. Apart from that I'm not aware of any major regression >> (wearing arm-linux-user, some arm-softmmu and debian hats). >> > > I'd say the two qcow2 data corruption bugs are a major regression. > (Both reported in in another thread). > > qemu 0.9.1 has the qcow2 code from kvm-72, which doesn't exhibit > either of those corruption bugs. A new release based on current kvm > userspace would introduce those bugs. One of the bugs (reported by > Marc) corrupts a qcow2 image so you can't use it even if you revert to > an older qemu/kvm. It's not clear if the other bug causes permanent > corruption itself, but anything which causes a guest to see the wrong > data can lead to the guest writing corrupt data elsewhere later on. > > Simply reverting the qcow2 code appears to fix those problems, so it > needn't hold up cutting a release. That's what I recommend. > Send some patches. Regards, Anthony Liguori > -- Jamie > > >