Machine shut off after tons of lsi_scsi: error: MSG IN data too long
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
Expired
|
Undecided
|
Unassigned |
Bug Description
The problem mostly happens during our backup, syslog does not have any problematic messages.
Host is Ubuntu 10.10 x86 64 bits
Guest is Windows 2003 Server 32 bits
Using Virtio and Red Hat driver I get a STOP screen 0x100000d1 and machine either reboot, stay frozen or shut off.
Using SCSI the machine shuts off and I get tons of message on stdout;
LC_ALL=C PATH=/usr/
char device redirected to /dev/pts/0
pci_add_option_rom: failed to find romfile "pxe-virtio.bin"
husb: open device 2.5
husb: config #1 need -1
husb: 1 interfaces claimed for configuration 1
husb: grabbed usb device 2.5
husb: config #1 need 1
husb: 1 interfaces claimed for configuration 1
lsi_scsi: error: Unimplemented message 0x00
(x8)
lsi_scsi: error: MSG IN data too long
lsi_scsi: error: Unimplemented message 0x00
(x760)
lsi_scsi: error: MSG IN data too long
lsi_scsi: error: MSG IN data too long
kvm: /build/
I can include minidump file if needed.
I am currently using IDE and it seems OK.
Changed in qemu: | |
status: | Expired → New |
On Wed, Jan 5, 2011 at 5:05 AM, TiCPU <email address hidden> wrote:
> Using Virtio and Red Hat driver I get a STOP screen 0x100000d1 and machine either reboot, stay frozen or shut off.
Here the minidump would be useful and we should get in touch with the
person that maintains the virtio-blk Windows driver.
> Using SCSI the machine shuts off and I get tons of message on stdout; buildd/ qemu-kvm- 0.12.5+ noroms/ hw/lsi53c895a. c:512: lsi_do_dma: Assertion `s->current' failed.
[...]
> lsi_scsi: error: Unimplemented message 0x00
> (x8)
>
> lsi_scsi: error: MSG IN data too long
> lsi_scsi: error: Unimplemented message 0x00
> (x760)
>
> lsi_scsi: error: MSG IN data too long
> lsi_scsi: error: MSG IN data too long
> kvm: /build/
Looks like the LSI SCSI device emulation is getting out of sync with
the guest's device driver.
Can you give more details or a test case that reproduces these
problems? Which backup software are you using and is it known to do
special purpose SCSI commands?
Stefan