Re: [Qemu-devel] IO errors in guest caused by LTP dio test

[Kevin Wolf <kwolf@redhat.com>]

Am 28.06.2011 10:50, schrieb Kevin Wolf:
> 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.

No news is good news? Does it work with a different image format?

Kevin