Re: kvmnet.sys BSOD w/ WinXP...
Hi Dor, On Wed, Sep 17, 2008 at 5:04 PM, Dor Laor [EMAIL PROTECTED] wrote: Daniel J Blueman wrote: When using Windows XP 32 installed with TCP/IP and microsoft client networking, I can reproduce an intermittent BSOD [1] with kvmnet.sys 1.0.0 and 1.2.0, by aborting a large data transfer in an application. Since this reproduces with 1.0.0 kvmnet.sys, it looks unrelated to the locking changes that went into 1.2.0, but something relating to when sockets are closed, flushed or data discarded. Perhaps the offset into the driver at 0xF761A5A9 - 0xF7618000 may tell us what is needed to reproduce and hint at what area the fix is needed in? Many thanks, Daniel --- [1] DRIVER_IRQL_NOT_LESS_OR_EQUAL *** STOP: 0x00D1 (0x001C,0x0002,0x,0xF761A5A9) *** kvmnet.sys - Address F761A5A9 base at F7618000, DateStamp 47dd531c Can you try http://people.qumranet.com/dor/Drivers-0-3107.iso this? With the updated WinXP 32bit drivers here, I'm finding that the application is experiences a socket disconnect/loss when upload starts. Also please provide the specific way of producing load. I'm using a software package from lecroy.com [http://www.lecroy.com/tm/Library/Software/PSG/petracersummit.asp?menuid=8], which connects to a device over the network and receives data at ~30Mbits/s with two concurrent streams. Along with it, please note kernel version, kvm version, qemu cmd line. Host is Ubuntu 8.0.4.1 LTS w/ 2.6.24-19-generic kernel, x86-64. Problem confirmed with KVM 74 1:74+dfsg-0ubuntu2~ppa3h; qemu version 0.9.1-1ubuntu1. Params are: kvm -hda winxp-next.qcow2 -m 768 -soundhw '' -parallel none -serial none -net nic,model=virtio -net user Let me know if you need any more information. Thanks, Daniel -- Daniel J Blueman -- 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
Re: kvmnet.sys BSOD w/ WinXP...
Daniel J Blueman wrote: When using Windows XP 32 installed with TCP/IP and microsoft client networking, I can reproduce an intermittent BSOD [1] with kvmnet.sys 1.0.0 and 1.2.0, by aborting a large data transfer in an application. Since this reproduces with 1.0.0 kvmnet.sys, it looks unrelated to the locking changes that went into 1.2.0, but something relating to when sockets are closed, flushed or data discarded. Perhaps the offset into the driver at 0xF761A5A9 - 0xF7618000 may tell us what is needed to reproduce and hint at what area the fix is needed in? Many thanks, Daniel --- [1] DRIVER_IRQL_NOT_LESS_OR_EQUAL *** STOP: 0x00D1 (0x001C,0x0002,0x,0xF761A5A9) *** kvmnet.sys - Address F761A5A9 base at F7618000, DateStamp 47dd531c Can you try http://people.qumranet.com/dor/Drivers-0-3107.iso this? Also please provide the specific way of producing load. Along with it, please note kernel version, kvm version, qemu cmd line. Regards, Dor -- 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
kvmnet.sys BSOD w/ WinXP...
When using Windows XP 32 installed with TCP/IP and microsoft client networking, I can reproduce an intermittent BSOD [1] with kvmnet.sys 1.0.0 and 1.2.0, by aborting a large data transfer in an application. Since this reproduces with 1.0.0 kvmnet.sys, it looks unrelated to the locking changes that went into 1.2.0, but something relating to when sockets are closed, flushed or data discarded. Perhaps the offset into the driver at 0xF761A5A9 - 0xF7618000 may tell us what is needed to reproduce and hint at what area the fix is needed in? Many thanks, Daniel --- [1] DRIVER_IRQL_NOT_LESS_OR_EQUAL *** STOP: 0x00D1 (0x001C,0x0002,0x,0xF761A5A9) *** kvmnet.sys - Address F761A5A9 base at F7618000, DateStamp 47dd531c -- Daniel J Blueman -- 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