From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60619) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YXeXj-0005Tc-P5 for qemu-devel@nongnu.org; Mon, 16 Mar 2015 19:35:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YXeXg-0005jz-K4 for qemu-devel@nongnu.org; Mon, 16 Mar 2015 19:35:31 -0400 Received: from p01c12o144.mxlogic.net ([208.65.145.67]:44496) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YXeXg-0005jr-EB for qemu-devel@nongnu.org; Mon, 16 Mar 2015 19:35:28 -0400 From: Chris Takemura Date: Mon, 16 Mar 2015 16:35:11 -0700 Message-ID: References: <55071113.9010406@redhat.com> In-Reply-To: <55071113.9010406@redhat.com> Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [Qemu-devel] lsi53c895a lsi_do_dma assertion failure List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , qemu-devel On 3/17/15, 2:21 AM, "Paolo Bonzini" wrote: > >On 16/03/2015 16:59, Chris Takemura wrote: >> Hi everyone, >>=20 >> We're using qemu as a device model for xen 4.4. Lately we've been >> having qemu crashes with this output: >>=20 >> lsi_scsi: error: Unhandled writeb 0xff =3D 0x0 >>=20 >> lsi_scsi: error: Unhandled writeb 0x100 =3D 0x0 >>=20 >> lsi_scsi: error: Unhandled writeb 0x101 =3D 0x0 >>=20 >> lsi_scsi: error: Unhandled writeb 0x102 =3D 0x0 >>=20 >> qemu-system-i386: /home/chris/qemu/hw/scsi/lsi53c895a.c:541: lsi_do_dma: >> Assertion `s->current' failed. >>=20 >>=20 >> This is with a clean qemu-2.1.0 tree, built for Xen. >>=20 >> I confirmed that commit d1d74664ea99cdc571afee12e31c8625595765b0 is >> present in our code. (As described in the thread that begins >> with=20 >>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.