Hi, Just to recap my problems with Win2K3 and SCSI...
Host: 2.6.28 x86_64 Intel Core2Duo E8500 (3.16GHz), 6gb ram Guest: Win2003 server, 32-bit, SP2 KVM: 82 (both userspace and kernel modules) qemu-system-x86_64 -name $name -smp 1 -m 1024 -vnc :$id -k fi -serial mon:telnet::1000$id,server,nowait -localtime -vga std -usb -usbdevice tablet -net nic,macaddr=00:16:3e:00:00:$id,model=e1000 -net tap,ifname=tap-$name -pidfile /var/run/kvm/$name.pid -boot c -drive index=0,media=disk,if=scsi,boot=on,file=/dev/mapper/vg0-$name - Copying file from network drive (100mbps network) to local drive seems to cause 'lsi_scsi: error: Bad Status move' 100% in one system, usually somewhere after 300mb transferred. - Also sometimes installing Oracle DB, Bea Weblogic and/or MS SQL Server seems to cause it. - Under normal loads it happens about once a week. - When running without kvm modules no errors occur. - Writing null to local drive works just fine. Unbuffered and write-trough write is about 50mb/s (whereas host can do about 95mb/s). - Once after such write I got 'Bad status move' error but only after guest had been idling for about 30s. Resulted in Windows KERNEL_INPAGE_ERROR (ntfs.sys) BSOD. Hasn't occured since. - Not all 'Bad status moves' cause BSOD but if they do it is KERNEL_INPAGE_ERROR... Feels like memory corruption to me. - Windows event log contains few dozen of "The driver detected a controller error on \Device\Scsi\sym_hu1." These come mostly in boot. - Another event log error 'The device did not respond within the timeout period.' occurs at somewhat same time as 'Bad Status move' error. - Bad Status move looks like it comes when scsi (write) command is completed after adapter is reset. Executed SCRIPTS doesn't know adapter has been reset and does bad things. Ryan, have you been able to duplicate this? I can provide you access to my test system where you could try to debug this. -- Anssi Kolehmainen [email protected] 040-5085390 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
