On 3/17/15, 2:21 AM, "Paolo Bonzini" <pbonz...@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.
