[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <9c3849cf-86c6-4568-bff5-1050b445322d@default>
Date: Tue, 26 Mar 2019 09:47:50 -0700 (PDT)
From: Dongli Zhang <dongli.zhang@...cle.com>
To: <qemu-block@...gnu.org>, <linux-scsi@...r.kernel.org>,
<megaraidlinux.pdl@...adcom.com>
Cc: <linux-kernel@...r.kernel.org>, <qemu-devel@...gnu.org>
Subject: megasas: Unexpected response from lun 1 while scanning, scan aborted
I am reporting an error that the scsi lun cannot initialize successfully when I
am emulating megasas scsi controller with qemu.
I am not sure if this is issue in qemu or linux kernel.
When 'lun=1' is specified, there is "Unexpected response from lun 1 while
scanning, scan aborted".
Everything works well if 'lun=0' is specified.
Below is the qemu cmdline involved:
-device megasas,id=scsi0 \
-device scsi-hd,drive=drive0,bus=scsi0.0,lun=1 \
-drive file=/home/zhang/img/test.img,if=none,id=drive0,format=raw
Below is the syslog related to 'scsi|SCSI'
# dmesg | grep SCSI
[ 0.392494] SCSI subsystem initialized
[ 0.460666] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[ 0.706788] sd 1:0:0:0: [sda] Attached SCSI disk
# dmesg | grep scsi
[ 0.511643] scsi host0: Avago SAS based MegaRAID driver
[ 0.523302] scsi 0:2:0:0: Unexpected response from lun 1 while scanning, scan aborted
[ 0.540364] scsi host1: ata_piix
[ 0.540780] scsi host2: ata_piix
[ 0.702396] scsi 1:0:0:0: Direct-Access ATA QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
When 'lun=1' is changed to 'lun=0', there is no issue.
Thank you very much!
Dongli Zhang
Powered by blists - more mailing lists