From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Megasas HBA emulation and SCSI update v.2
Date: Wed, 24 Nov 2010 01:41:04 -0800 [thread overview]
Message-ID: <1290591664.30138.216.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <4CEA473F.5030806@suse.de>
On Mon, 2010-11-22 at 11:34 +0100, Hannes Reinecke wrote:
> On 11/22/2010 11:15 AM, Hannes Reinecke wrote:
> >
> > The is the second version of the megasas patchset; changes are:
> > v1 -> v2:
> > - Include suggestions (and acked-by) from Christoph Hellwig
> > - Updated patch description as requested by Gerd Hoffman
> > - Use generic iov_size() implementation
> > - Drop old patches
> > - Make SCSI HBA configurable
> >
> > This patchset can be found at
> >
> > git://repo.or.cz/qemu/megasas.git
> > branch megasas.v2
> >
> Hey, sorry, just found out I've omitted the series numbers
> in the patchset. But reposting the entire patchset just
> to get the numbers back is a bit of a waste.
> So please check with the above git tree or
> use this as a series file:
> >
> > Hannes Reinecke (15):
> > scsi: Increase the number of possible devices
> > scsi: Return SAM status codes
> > scsi: INQUIRY VPD fixes
> > scsi: Move sense handling into the driver
> > scsi-disk: Remove duplicate cdb parsing
> > scsi: Update sense code handling
> > lsi53c895a: Rename 'sense' to 'status'
> > scsi-disk: Allocate iovec dynamically
> > scsi: Use 'SCSIRequest' directly
> > scsi-disk: add data direction checking
> > Remove 'bus' argument from SCSI command completion callbacks
> > scsi: Implement 'get_sense' callback
> > scsi: Implement alloc_req_iov callback
> > megasas: LSI Megaraid SAS emulation
> > Make SCSI HBA configurable
> >
>
Hey Hannes,
Just a heads up, I noticed that the latest v2 megasas w/ scsi-generic ->
TCM_loop appears to be broken on a Windows7 (Build 7600) guest, which
hangs during boot -> LUN scan with the following:
truelife:/usr/src/qemu-kvm.git# ./x86_64-softmmu/qemu-system-x86_64 -m 512 -boot c ~/windows7.img \
-drive if=none,id=mydisk1,file=/dev/sg4 -device megasas,id=raid
-device scsi-generic,bus=raid.0,scsi-id=1,drive=mydisk1
megasas: Using 80 sges, 1000 cmds, raid mode
megasas: Reset
megasas: Mapping MMIO region 0 at f2040000
megasas: Mapping IO region 2 at 0000c200
megasas: Mapping QUEUE region 3 at f2080000
megasas: Mapping MMIO region 0 at f2040000
megasas: Mapping IO region 2 at 0000c200
megasas: Mapping QUEUE region 3 at f2080000
megasas: Mapping MMIO region 0 at f2040000
megasas: Mapping IO region 2 at 0000c200
megasas: Mapping QUEUE region 3 at f2080000
megasas: readl mmio 0xb0
megasas: writel mmio 20: 7
megasas: Reset
megasas: readl mmio 0x20
megasas: writel mmio 40: 1ff9c041
megasas: Received frame addr 1ff9c000 count 32
megasas: MFI cmd 0 context 0 count 32
megasas: Return new frame 0 cmd 0x7f7711654330
megasas: Enqueue frame 0 count 32 context 0 tail 0 busy 1
megasas: MFI init firmware: xfer len 0 pa 0
megasas: MFI init firmware: queue at f000ff53f000e2c3 len -268370093 head f000ff53f000ff53 tail f000ff53f000ff53
megasas: Complete frame context 0
Oddly enough, after trying a number of older megasas versions with this
particular Windows 7 guest w/ scsi-generic -> TCM_Loop, the last version
that I can find which is still working is this branch from May, on what
is effectively v1.0 megasas code.
http://git.kernel.org/?p=virt/kvm/nab/qemu-kvm.git;a=shortlog;h=refs/heads/windows7-megasas-working
Anyways, I have not had a chance to track this down myself and wanted
to see if you had any ideas..
--nab
next prev parent reply other threads:[~2010-11-24 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 10:15 [Qemu-devel] [PATCH] Megasas HBA emulation and SCSI update v.2 Hannes Reinecke
2010-11-22 10:34 ` Hannes Reinecke
2010-11-24 9:41 ` Nicholas A. Bellinger [this message]
2010-12-01 14:18 ` Hannes Reinecke
2010-12-01 15:46 ` Hannes Reinecke
2010-12-02 0:14 ` Nicholas A. Bellinger
2010-12-02 7:51 ` Hannes Reinecke
2010-12-02 9:16 ` Nicholas A. Bellinger
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=1290591664.30138.216.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=hare@suse.de \
--cc=kraxel@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).