From: Avi Kivity <avi@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: the >1Tb block issue
Date: Tue, 18 May 2010 20:29:20 +0300 [thread overview]
Message-ID: <4BF2CE70.1060402@redhat.com> (raw)
In-Reply-To: <4BF2B7CD.7090204@msgid.tls.msk.ru>
On 05/18/2010 06:52 PM, Michael Tokarev wrote:
> I just re-verified it on current stable
> qemu-kvm-0.12.4. The issue is still here,
> trivial to trigger.
>
Can you try the patch I just posted?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-05-18 17:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 15:52 the >1Tb block issue Michael Tokarev
2010-05-18 15:59 ` Daniel P. Berrange
2010-05-18 16:51 ` Michael Tokarev
2010-05-18 16:58 ` Gleb Natapov
2010-05-18 17:29 ` Avi Kivity [this message]
2010-05-18 17:34 ` Michael Tokarev
2010-05-18 17:38 ` Avi Kivity
2010-05-18 18:03 ` Michael Tokarev
2010-05-18 18:09 ` Avi Kivity
2010-05-18 18:38 ` Michael Tokarev
2010-05-18 18:43 ` Michael Tokarev
2010-05-19 8:57 ` Christoph Hellwig
2010-05-19 9:03 ` 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=4BF2CE70.1060402@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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