qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Cutting a new QEMU release
Date: Fri, 13 Feb 2009 11:00:19 -0600	[thread overview]
Message-ID: <4995A723.9010208@codemonkey.ws> (raw)
In-Reply-To: <20090213163043.GJ18471@shareable.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
>
>
>   
 

  reply	other threads:[~2009-02-13 17:00 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 20:48 [Qemu-devel] Cutting a new QEMU release Anthony Liguori
2009-02-03 20:58 ` Glauber Costa
2009-02-03 21:35   ` Laurent Desnogues
2009-02-03 21:50     ` Anthony Liguori
2009-02-03 22:05       ` Laurent Desnogues
2009-02-03 22:47         ` Anthony Liguori
2009-02-03 23:48           ` Glauber Costa
2009-02-04 13:09       ` Ulrich Hecht
2009-02-04  0:31     ` David Turner
     [not found]     ` <74222928-D24B-4780-BDB0-D537A83C4F68@hotmail.com>
2009-02-04  5:08       ` C.W. Betts
2009-02-03 21:48 ` Rick Vernam
2009-02-03 22:07 ` Daniel P. Berrange
2009-02-04 14:50 ` Aurelien Jarno
2009-02-04 15:23   ` Tristan Gingold
2009-02-04 15:43     ` Lennart Sorensen
2009-02-04 16:01       ` Tristan Gingold
2009-02-04 18:17         ` [Qemu-devel] " Consul
2009-02-04 17:39   ` [Qemu-devel] " Blue Swirl
2009-02-04 17:50     ` Jonathan Kalbfeld
2009-02-04 20:07   ` Blue Swirl
2009-02-07 14:15   ` Stuart Brady
2009-02-04 15:58 ` Glauber Costa
2009-02-07 15:29 ` Shin-ichiro KAWASAKI
2009-02-11 21:49   ` Rob Landley
2009-02-12 14:44     ` Shin-ichiro KAWASAKI
2009-02-12 21:08       ` Rob Landley
2009-02-12 21:44       ` Rob Landley
2009-02-09 12:43 ` Mark McLoughlin
2009-02-09 21:36   ` Anthony Liguori
2009-02-10  0:47   ` Rob Landley
2009-02-10  7:22     ` M. Warner Losh
2009-02-13  8:40 ` Riku Voipio
2009-02-13  9:59   ` Stefano Stabellini
2009-02-13 16:30   ` Jamie Lokier
2009-02-13 17:00     ` Anthony Liguori [this message]
2009-02-13 19:04       ` [Qemu-devel] [PATCH] Revert block-qcow2.c to kvm-72 version due to corruption reports Jamie Lokier
2009-02-14 22:23         ` Dor Laor
2009-02-15  2:20           ` Jamie Lokier
2009-02-14 23:13         ` Anthony Liguori
2009-02-15  2:01           ` Jamie Lokier
2009-02-15  4:09             ` Anthony Liguori
2009-02-15 15:42               ` Jamie Lokier
2009-02-15 18:19                 ` Anthony Liguori
2009-02-15 18:34                   ` Johannes Schindelin
2009-02-16  1:01                     ` Anthony Liguori
2009-02-17  0:52                       ` Jamie Lokier
2009-02-17  2:55                         ` Anthony Liguori
2009-02-16  1:19                     ` Anthony Liguori
2009-02-17  1:01                   ` Jamie Lokier

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=4995A723.9010208@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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).