current mainline ide doesn't like qemu/kvm (or vice versa)

current mainline ide doesn't like qemu/kvm (or vice versa)

[Christoph Hellwig]

When trying to put some stress on qemu by running the xfs testsuite
I get the following:

debian:~/xfs-cmds/xfstests# sh check 
[  438.166822] SGI XFS with ACLs, security attributes, realtime, large block numbers, no debug enabled
[  438.185557] SGI XFS Quota Management subsystem
[  438.193150] hdb: task_no_data_intr: status=0x41 { DriveReady Error }
[  438.194018] hdb: task_no_data_intr: error=0x04 { DriveStatusError }
[  438.194195] ide: failed opcode was: 0x9d

and after that the kernel seems to hang.  Qemu is emulating a piix3
device, and using the piix driver.  This is on a pretty old kvm (version
28) because newer ones don't even compile.

Re: current mainline ide doesn't like qemu/kvm (or vice versa)

[Alan Cox]

On Fri, 8 Feb 2008 16:25:08 +0100
Christoph Hellwig <hch@lst.de> wrote:

> When trying to put some stress on qemu by running the xfs testsuite
> I get the following:
> 
> debian:~/xfs-cmds/xfstests# sh check 
> [  438.166822] SGI XFS with ACLs, security attributes, realtime, large block numbers, no debug enabled
> [  438.185557] SGI XFS Quota Management subsystem
> [  438.193150] hdb: task_no_data_intr: status=0x41 { DriveReady Error }
> [  438.194018] hdb: task_no_data_intr: error=0x04 { DriveStatusError }
> [  438.194195] ide: failed opcode was: 0x9d

Drive aborted the command. Thats all correct.
> 
> and after that the kernel seems to hang.  Qemu is emulating a piix3
> device, and using the piix driver.  This is on a pretty old kvm (version
> 28) because newer ones don't even compile.

Old Qemu is not really a credible IDE emulation. The chances are that as
with all the libata bugs I close for qemu the problem is qemu. Please
file a bug with the qemu people.

Re: current mainline ide doesn't like qemu/kvm (or vice versa)

[Anthony Liguori]

Alan Cox wrote:
> On Fri, 8 Feb 2008 16:25:08 +0100
> Christoph Hellwig <hch@lst.de> wrote:
> 
>> When trying to put some stress on qemu by running the xfs testsuite
>> I get the following:
>>
>> debian:~/xfs-cmds/xfstests# sh check 
>> [  438.166822] SGI XFS with ACLs, security attributes, realtime, large block numbers, no debug enabled
>> [  438.185557] SGI XFS Quota Management subsystem
>> [  438.193150] hdb: task_no_data_intr: status=0x41 { DriveReady Error }
>> [  438.194018] hdb: task_no_data_intr: error=0x04 { DriveStatusError }
>> [  438.194195] ide: failed opcode was: 0x9d
> 
> Drive aborted the command. Thats all correct.
>> and after that the kernel seems to hang.  Qemu is emulating a piix3
>> device, and using the piix driver.  This is on a pretty old kvm (version
>> 28) because newer ones don't even compile.

kvm-28 is ancient and there have been IDE emulation fixes since.  I am 
not aware of issues building KVM either.  The problems you reported a 
month ago on kvm-devel have been fixed.

> Old Qemu is not really a credible IDE emulation. The chances are that as
> with all the libata bugs I close for qemu the problem is qemu. Please
> file a bug with the qemu people.

Agreed, this is very likely to be a QEMU issue (that may have already 
been fixed).

Regards,

Anthony Liguori

> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>