From: Avi Kivity <avi@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: stefanha@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 2/3] qcow2: Use QcowCache
Date: Wed, 09 Feb 2011 13:23:39 +0200 [thread overview]
Message-ID: <4D52793B.6010104@redhat.com> (raw)
In-Reply-To: <4D527847.9070400@redhat.com>
On 02/09/2011 01:19 PM, Avi Kivity wrote:
> On 01/20/2011 07:10 PM, Kevin Wolf wrote:
>> Use the new functions of qcow2-cache.c for everything that works on
>> refcount
>> block and L2 tables.
>>
>
> While autotesting qemu-kvm's stable-0.14 branch, this commit causes
> failures. The scenario is:
>
> - install OS
> - reboot
> - hang at GRUB prompt
> - qemu-img reports hundreds of leaked clusters
>
> The actual commit I am testing is in qemu-kvm.git
> qcow2-qcowcache-failure (tag). The test runs with -drive ,cache=unsafe.
Got it - it's specific to qemu-kvm; the call to bdrv_close_all() wasn't
replicated in qemu-kvm's main loop.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-02-09 11:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 17:10 [Qemu-devel] [PATCH v4 0/3] qcow2 metadata cache Kevin Wolf
2011-01-20 17:10 ` [Qemu-devel] [PATCH v4 1/3] qcow2: Add QcowCache Kevin Wolf
2011-01-24 14:00 ` Stefan Hajnoczi
2011-01-20 17:10 ` [Qemu-devel] [PATCH v4 2/3] qcow2: Use QcowCache Kevin Wolf
[not found] ` <AANLkTimeRQVVeNnRbaiRNQ-SbExyJDZiuteBP7wfv9He@mail.gmail.com>
2011-01-24 14:54 ` Kevin Wolf
2011-01-24 15:26 ` Stefan Hajnoczi
2011-01-24 15:36 ` Kevin Wolf
2011-01-24 15:39 ` Stefan Hajnoczi
2011-02-09 11:19 ` Avi Kivity
2011-02-09 11:23 ` Avi Kivity [this message]
2011-01-20 17:10 ` [Qemu-devel] [PATCH v4 3/3] qcow2: Batch flushes for COW Kevin Wolf
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=4D52793B.6010104@redhat.com \
--to=avi@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).