All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Schmitt" <scdbackup@gmx.net>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@gmail.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] Do you have a use for a tester of virtio-scsi with CD drives ?
Date: Sun, 06 Nov 2011 11:35:50 +0100	[thread overview]
Message-ID: <9743422021570@192.168.2.69> (raw)
In-Reply-To: <4EB64286.5060208@redhat.com>

Hi,

Paolo Bonzini wrote:
> It would be more interesting if you tried again the failure cases with a
> virtio drive (if=virtio).  It would appear as /dev/vda but you can issue
> SG_IO to it.  This would isolate the failure to the kernels vs. the SCSI
> subsystem.

Will do. I am currently fighting with eSATA and may have to give up
the planned Blu-ray tests, after USB already failed so dramatically.

The external drive does not work properly with 3.0 Gbps.
This is a known shortcomming of my test machine's eSATA cabling or of
the eSATA box (i only have one of either kind, so i cannot cross-check).

--------------------------------------------------------------------

Interesting insight:

The failure at 3.0 Gbps throws on the host the same sense code as
FORMAT UNIT does on the guest with the internal SATA drive, which
runs at 1.5 Gbps by miracle.
  Sense Key B "Command aborted", ASC 00 ASCQ 00

So the sense code with FORMAT UNIT might stem from the host kernel
and not from qemu.

--------------------------------------------------------------------

Other than Debian 5 the newer Debian 6 kernel 2.6.32-5-amd64 does not
reset to 1.5 Gps after the first transport failure.
  Nov  6 10:59:55 debian2 kernel: [ 2025.849176] ata5: hard resetting link
  Nov  6 10:59:56 debian2 kernel: [ 2026.780105] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
I dimly remember that i'd need to patch initrd to get the kernel
module option into effect at an early boot stage.
I haven't done this since two years and this could possibly change the
whole test setup.

Better would be to know, why the internal SATA drive is started with
1.5 Gbps at boot time
  Nov  6 10:26:15 debian2 kernel: [    1.241546] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  Nov  6 10:26:15 debian2 kernel: [    1.242406] ata3.00: ATAPI: TSSTcorp CDDVDW SH-S223B, SB02, max UDMA/100

In contrast to the eSATA attached drive
  Nov  6 10:26:15 debian2 kernel: [    1.688050] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
  Nov  6 10:26:15 debian2 kernel: [    1.693623] ata5.00: ATAPI: Optiarc BD RW BD-5300S, 1.04, max UDMA/100

On Debian 5, the internal drive was run with 3.0 Gbps and worked fine.

Miracles of system administration ...

--------------------------------------------------------------------


Have a nice day :)

Thomas

  reply	other threads:[~2011-11-06 10:36 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 17:27 [Qemu-devel] Do you have a use for a tester of virtio-scsi with CD drives ? Thomas Schmitt
2011-11-01 21:03 ` Thomas Schmitt
2011-11-02 11:25   ` Stefan Hajnoczi
2011-11-02 12:08     ` Paolo Bonzini
2011-11-02 16:26       ` Thomas Schmitt
2011-11-02 16:34         ` Paolo Bonzini
2011-11-02 18:05           ` Thomas Schmitt
2011-11-02 19:50             ` Paolo Bonzini
2011-11-02 21:22               ` Thomas Schmitt
2011-11-02 22:08                 ` Thomas Schmitt
2011-11-02 22:16                   ` [Qemu-devel] Compile error Frans de Boer
2011-11-02 22:19                     ` Anthony Liguori
2011-11-02 22:31                       ` Frans de Boer
2011-11-03  7:49                 ` [Qemu-devel] Do you have a use for a tester of virtio-scsi with CD drives ? Paolo Bonzini
2011-11-03  9:15                   ` Thomas Schmitt
2011-11-03  9:36                     ` Paolo Bonzini
2011-11-03 13:10                   ` Thomas Schmitt
2011-11-03 22:30                     ` Thomas Schmitt
2011-11-04  9:18                       ` Thomas Schmitt
2011-11-04  9:38                         ` Paolo Bonzini
2011-11-04 11:09                           ` Thomas Schmitt
2011-11-04 11:31                             ` Paolo Bonzini
2011-11-04 13:03                               ` Thomas Schmitt
2011-11-04 20:28                                 ` Thomas Schmitt
2011-11-05  8:33                                   ` Paolo Bonzini
2011-11-05 13:00                                     ` Thomas Schmitt
2011-11-05 14:37                                   ` Thomas Schmitt
2011-11-05 15:53                                     ` Paolo Bonzini
2011-11-05 16:38                                       ` Thomas Schmitt
2011-11-05 20:47                                     ` Thomas Schmitt
2011-11-06  8:17                                       ` Paolo Bonzini
2011-11-06 10:35                                         ` Thomas Schmitt [this message]
2011-11-06 20:14                                         ` Thomas Schmitt
2011-11-07  8:02                                           ` Paolo Bonzini
2011-11-07 10:04                                             ` Thomas Schmitt
2011-11-07 11:13                                               ` Paolo Bonzini
2011-11-07 11:24                                                 ` Zhi Yong Wu
2011-11-07 11:29                                                   ` Paolo Bonzini
2011-11-07 11:40                                                     ` Zhi Yong Wu
2011-11-06  9:31                                       ` Thomas Schmitt
2011-11-04 13:26                       ` Andreas Färber
2011-11-04 14:46                         ` Thomas Schmitt
2011-11-07  8:48             ` Zhi Yong Wu
2011-11-02 15:15     ` Thomas Schmitt
2011-11-02 16:22       ` Paolo Bonzini

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=9743422021570@192.168.2.69 \
    --to=scdbackup@gmx.net \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.