From: Luiz Capitulino <lcapitulino@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] qcow2/coroutine fixes
Date: Thu, 1 Sep 2011 13:19:54 -0300 [thread overview]
Message-ID: <20110901131954.25e81235@doriath> (raw)
In-Reply-To: <1314887471-18052-1-git-send-email-kwolf@redhat.com>
On Thu, 1 Sep 2011 16:31:08 +0200
Kevin Wolf <kwolf@redhat.com> wrote:
> This fixes a couple of issues with the coroutine-based block layer regarding
> error handling.
>
> Luiz, can you please try if this fixes your bug?
It fixes the reported bug, but it seems that there's another issue.
I'll copy & paste the test case here for our convenience:
1. Create a 100MB logical volume and create a 200MB qcow2 image on it
2. Run qemu with the following command-line:
# qemu -drive file=disks/test.img,if=virtio,cache=writeback,aio=native \
-drive file=/dev/vg_doriath/kvmtest,if=virtio -enable-kvm -m 1G \
-monitor stdio -netdev type=tap,id=guest0,script=qemu-ifup-switch \
-device virtio-net-pci,netdev=guest0 -cpu host
3. Log into the guest and run dd to write 150MB on /dev/vdb
4. The VM will stop
5. Assign extra space to the logical volume, say 200MB
6. Type 'cont' in the monitor
If I assign chunks of 50MB each time the VM stop in steps 4 and 5,
I have to do it several times (totalizing a logical volume size of 400MB),
so that dd is able to finish.
Testing with commit b96e92470 works as expected, I extend the lv twice
with 50MB (totalizing 200MB) and dd finishes normally.
Small note: I'm writing 157MB in step 3.
prev parent reply other threads:[~2011-09-01 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 14:31 [Qemu-devel] [PATCH 0/3] qcow2/coroutine fixes Kevin Wolf
2011-09-01 14:31 ` [Qemu-devel] [PATCH 1/3] qcow2: Properly initialise QcowL2Meta Kevin Wolf
2011-09-01 14:31 ` [Qemu-devel] [PATCH 2/3] qcow2: Fix error cases to run depedent requests Kevin Wolf
2011-09-01 14:31 ` [Qemu-devel] [PATCH 3/3] async: Allow nested qemu_bh_poll calls Kevin Wolf
2011-09-02 8:33 ` Stefan Hajnoczi
2011-09-01 16:19 ` Luiz Capitulino [this message]
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=20110901131954.25e81235@doriath \
--to=lcapitulino@redhat.com \
--cc=kwolf@redhat.com \
--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).