From: Chris Takemura <ctakemura@axcient.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] lsi53c895a lsi_do_dma assertion failure
Date: Mon, 16 Mar 2015 16:35:11 -0700 [thread overview]
Message-ID: <D12D80EC.2C01E%ctakemura@axcient.com> (raw)
In-Reply-To: <55071113.9010406@redhat.com>
On 3/17/15, 2:21 AM, "Paolo Bonzini" <pbonzini@redhat.com> wrote:
>
>On 16/03/2015 16:59, Chris Takemura wrote:
>> Hi everyone,
>>
>> We're using qemu as a device model for xen 4.4. Lately we've been
>> having qemu crashes with this output:
>>
>> lsi_scsi: error: Unhandled writeb 0xff = 0x0
>>
>> lsi_scsi: error: Unhandled writeb 0x100 = 0x0
>>
>> lsi_scsi: error: Unhandled writeb 0x101 = 0x0
>>
>> lsi_scsi: error: Unhandled writeb 0x102 = 0x0
>>
>> qemu-system-i386: /home/chris/qemu/hw/scsi/lsi53c895a.c:541: lsi_do_dma:
>> Assertion `s->current' failed.
>>
>>
>> This is with a clean qemu-2.1.0 tree, built for Xen.
>>
>> I confirmed that commit d1d74664ea99cdc571afee12e31c8625595765b0 is
>> present in our code. (As described in the thread that begins
>> with
>>http://qemu-devel.nongnu.narkive.com/LtGj28sZ/win2k8-32-bit-mix-of-ide-an
>>d-scsi-assertion ).
>
>What guest is this? The answer is basically "do not use this device
>model", it is old and buggy and newer guests do not even ship the driver
>anymore.
Windows 2008 R2.
I agree, but I don't know how to specify a different device emulation for
xen. If you have some tips on that, I'd be grateful.
next prev parent reply other threads:[~2015-03-16 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 15:59 [Qemu-devel] lsi53c895a lsi_do_dma assertion failure Chris Takemura
2015-03-16 17:21 ` Paolo Bonzini
2015-03-16 23:35 ` Chris Takemura [this message]
2015-03-17 7:22 ` Markus Armbruster
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=D12D80EC.2C01E%ctakemura@axcient.com \
--to=ctakemura@axcient.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).