From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:36296) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UdkBJ-0002Y8-KA for qemu-devel@nongnu.org; Sat, 18 May 2013 12:40:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UdkBC-0004Ih-Ql for qemu-devel@nongnu.org; Sat, 18 May 2013 12:40:29 -0400 Received: from isrv.corpit.ru ([86.62.121.231]:50983) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UdkBC-0004IH-IS for qemu-devel@nongnu.org; Sat, 18 May 2013 12:40:22 -0400 Message-ID: <5197AEF1.8070302@msgid.tls.msk.ru> Date: Sat, 18 May 2013 20:40:17 +0400 From: Michael Tokarev MIME-Version: 1.0 References: <5197825B.6050008@msgid.tls.msk.ru> <51978484.1050006@redhat.com> <5197869A.7060004@msgid.tls.msk.ru> <51979295.8000503@msgid.tls.msk.ru> <5197A407.1010303@redhat.com> In-Reply-To: <5197A407.1010303@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] IDE TRIM bug on at least PPC target List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel 18.05.2013 19:53, Paolo Bonzini wrote: > Il 18/05/2013 16:39, Michael Tokarev ha scritto: >> And I don't really know how to add scsi device to qemu ppc. >> >> qemu-system-ppc -drive file=foo,if=scsi > For example: > > qemu-system-ppc -drive file=foo,if=none,id=hd -device \ > megasas -device scsi-disk,drive=hd This creates megasas device in the guest, but it does not work still, at least with the debian wheezy (current) kernel. It tries to load megaraid_sas module, and is getting this: scsi3 : LSI SAS based MegaRAID driver irq 22: nobody cared (try booting with the "irqpool" option) ... --- Exception: 501 at __do_softirq+0x6c/0x1dc LR = call_do_softirq+0x14/0x24 ... --- Exception: 501 at megasas_fire_cmd_ppc+0x28/0x2c [megaraid_sas] LR = megasas_issue_dcmd+0x28/0x38 [megaraid_sas] ... Disabling IRQ #22 scsi 3:0:0:0: megasas: RESET cmd=12 retries=0 megasas: [ 0]waiting for 1 commands to complete megasas: [10]waiting for 1 commands to complete INFO: task modprobe:4017 blocked for more than 120 seconds. ... and so on. So I'm afraid megasas isn't exactly useful in this situation. Thanks, /mjt