From: Kevin Wolf <kwolf@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] IO errors in guest caused by LTP dio test
Date: Tue, 28 Jun 2011 10:50:54 +0200 [thread overview]
Message-ID: <4E0995EE.1020305@redhat.com> (raw)
In-Reply-To: <20110627160806.GB13616@one.firstfloor.org>
Am 27.06.2011 18:08, schrieb Andi Kleen:
> On Mon, Jun 27, 2011 at 05:59:41PM +0200, Kevin Wolf wrote:
>> Am 23.06.2011 01:36, schrieb Andi Kleen:
>>>
>>> Running LTP testcases/kernel/io/direct_io/test_dma_thread_diotest7
>>> causes IO errors in the guest. There are no IO errors on the host.
>>>
>>> Kernel Linux 3.0.0-rc*
>>> Using a standard emulated IDE -hda image.
>>
>> Couldn't reproduce this in a quick test with a random guest I had
>> available. What is your complete qemu command line? Is the problem new
>
> -m 1500M -smp 2 \
> -hda ~/qemu/suse-11.1-64.img \
> -kernel arch/x86/boot/bzImage -append "root=/dev/sda1 debug $EXTRA" "$@"
>
> Could it be related to the image?
>
> suse11.3-64.img: Qemu Image, Format: Qcow , Version: 1 , Disk Size could be: 83886080 * 256 bytes
Oh, this is a qcow1 image? Interesting, I didn't expect that people are
still using this format. :-)
Definitely worth trying a raw image or at least qcow2. The old qcow1
format driver hasn't been actively maintained for quite a while now.
>> with the 3.0 RCs or does it also happen with kernels that my existing
>> guests are likely to have in use - say, the F15 kernel?
>
> It happened on older kernels too.
>>
>> I guess with virtio-blk you don't see the problems?
>
> Will try later.
Ok, thanks. It looked like an IDE problem at first, but now that you
mention it's a qcow1 image, I think it could just as well be an image
format driver bug.
Kevin
next prev parent reply other threads:[~2011-06-28 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 23:36 [Qemu-devel] IO errors in guest caused by LTP dio test Andi Kleen
2011-06-27 15:59 ` Kevin Wolf
2011-06-27 16:08 ` Andi Kleen
2011-06-28 8:50 ` Kevin Wolf [this message]
2011-07-11 8:49 ` 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=4E0995EE.1020305@redhat.com \
--to=kwolf@redhat.com \
--cc=andi@firstfloor.org \
--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).