On 08/05/2010 10:58 PM, Peter Lieven wrote:
Hi,
we today saw a Win2k8 VM with first device IDE and second device SCSI crash reprocably during boot.
Win2k8 32-bit Server was installed with IDE only. The second SCSI device was added later.
Here is the output and commandline:
Aug 5 20:42:55 172.21.59.142 exec: /usr/bin/qemu-kvm-0.12.4 -net tap,vlan=726,script=no,downscript=no,ifname=tap0 -net nic,vlan=726,model=rtl8139,macaddr=52:54:00:fe:00:bf -drive format=host_device,file=/dev/mapper/iqn.2001-05.com.equallogic:0-8a0906-e4ce1ab04-3ce7a1250354c545-p01-w2k8,if=ide,boot=on,cache=none,aio=native -drive format=host_device,file=/dev/mapper/iqn.2001-05.com.equallogic:0-8a0906-319e1ab04-39a7a1250204c503-test2,if=scsi,boot=off,cache=none,aio=native -m 4096 -smp 4 -monitor tcp:0:4001,server,nowait -vnc :1 -name 'W2K8-01' -boot order=dc,menu=off -k de -pidfile /var/run/qemu/vm-200.pid -mem-path /hugepages -mem-prealloc -cpu qemu64,model_id='Intel(R) Xeon(R) CPU L5640 @ 2.27GHz',-nx -rtc base=localtime,clock=vm -vga cirrus -usb -usbdevice tablet
Aug 5 20:43:06 172.21.59.142 kvm: lsi_scsi: error: Unhandled writeb 0xff = 0x0
Aug 5 20:43:06 172.21.59.142 kvm: lsi_scsi: error: Unhandled writeb 0x100 = 0x0
Aug 5 20:43:06 172.21.59.142 kvm: lsi_scsi: error: Unhandled writeb 0x101 = 0x0
Aug 5 20:43:06 172.21.59.142 kvm: lsi_scsi: error: Unhandled writeb 0x102 = 0x0
Aug 5 20:43:06 172.21.59.142 kvm: qemu-kvm-0.12.4: /usr/src/qemu-kvm-0.12.4/hw/lsi53c895a.c:512: lsi_do_dma: Assertion `s->current' failed.
Aug 5 20:43:06 172.21.59.142 kvm: Aborted
Aug 5 20:43:06 172.21.59.142 kvm errno=134
Any ideas?
Best Regards,
Peter
Peter, you say you're using Win2K8 32-bit (x86) version (i.e. you don't
use Win2K8R2 - it doesn't have LSI drivers for lsi53c895a AFAIK) ? I
don't know but isn't Win2K8 x64 only? Does 32-bit version for this
system exists? Nevertheless the registers on the log you wrote about
were somehow problematic on x64 LSI drivers because of bad phase jump
implementation.
Paolo, I remember we've been studying the LSI SCSI controller code and
those unhandled writes on registers 0xff, 0x100, 0x101 and 0x102 were
there for the Windows x64 guests and this was caused by invalid phase
jump registers not meeting the specs. Nevertheless when I tried to seach
some information on errno=134 (based on assumption it's a standard OS
error) I used perror but it returned some kind of MySQL error code:
$ perror 134
MySQL error code 134: Record was already deleted (or record file crashed)
$
I don't know whether installation MySQL can override some codes from
perror however even googling for the OS Error 134 proved to be
ineffective. Are you having any ideas ? Is your patch for LSI SCSI
controller applied in the upstream ?
Thanks,
Michal
--
Michal Novotny<minovotn@xxxxxxxxxx>, RHCE
Virtualization Team (xen userspace), Red Hat
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
