* [Qemu-devel] [Bug 639651] [NEW] DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping @ 2010-09-15 15:12 Michal Suchanek 2010-09-16 13:27 ` [Qemu-devel] [Bug 639651] " Michal Suchanek ` (12 more replies) 0 siblings, 13 replies; 19+ messages in thread From: Michal Suchanek @ 2010-09-15 15:12 UTC (permalink / raw) To: qemu-devel Public bug reported: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. I can post the screenshot if somebody thinks it is interesting enough. The same image works on hardware (which has controllers different from the qemu PIIX3) and in VirtualBox (with the default PIIX4 as well as PIIX3) so long as IO apic is enabled). I am not sure if this is an error with the MS drivers or how they are used in sysprep in this particular case or if his is some strange error in qemu emulation in the PIIX3 controller or elsewhere. The image is originally created on hardware with MP acpi (not virtualization). ** Affects: qemu Importance: Undecided Status: New ** Affects: debian Importance: Undecided Status: New ** Tags: windows ** Also affects: debian Importance: Undecided Status: New -- DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping https://bugs.launchpad.net/bugs/639651 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in QEMU: New Status in Debian GNU/Linux: New Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. I can post the screenshot if somebody thinks it is interesting enough. The same image works on hardware (which has controllers different from the qemu PIIX3) and in VirtualBox (with the default PIIX4 as well as PIIX3) so long as IO apic is enabled). I am not sure if this is an error with the MS drivers or how they are used in sysprep in this particular case or if his is some strange error in qemu emulation in the PIIX3 controller or elsewhere. The image is originally created on hardware with MP acpi (not virtualization). ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping 2010-09-15 15:12 [Qemu-devel] [Bug 639651] [NEW] DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping Michal Suchanek @ 2010-09-16 13:27 ` Michal Suchanek 2010-09-16 14:34 ` Michal Suchanek ` (11 subsequent siblings) 12 siblings, 0 replies; 19+ messages in thread From: Michal Suchanek @ 2010-09-16 13:27 UTC (permalink / raw) To: qemu-devel ** Attachment added: "screenshot of the blue screen" https://bugs.launchpad.net/qemu/+bug/639651/+attachment/1593631/+files/gkrellShoot_2010-09-16_152436.png ** Description changed: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. I can post the screenshot if somebody thinks it is interesting enough. The same image works on hardware (which has controllers different from the qemu PIIX3) and in VirtualBox (with the default PIIX4 as well as PIIX3) so long as IO apic is enabled). I am not sure if this is an error with the MS drivers or how they are used in sysprep in this particular case or if his is some strange error in qemu emulation in the PIIX3 controller or elsewhere. The image is originally created on hardware with MP acpi (not virtualization). + + qemu-kvm 0.12.5+dfsg-2 -- DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping https://bugs.launchpad.net/bugs/639651 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in QEMU: New Status in Debian GNU/Linux: New Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. I can post the screenshot if somebody thinks it is interesting enough. The same image works on hardware (which has controllers different from the qemu PIIX3) and in VirtualBox (with the default PIIX4 as well as PIIX3) so long as IO apic is enabled). I am not sure if this is an error with the MS drivers or how they are used in sysprep in this particular case or if his is some strange error in qemu emulation in the PIIX3 controller or elsewhere. The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping 2010-09-15 15:12 [Qemu-devel] [Bug 639651] [NEW] DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping Michal Suchanek 2010-09-16 13:27 ` [Qemu-devel] [Bug 639651] " Michal Suchanek @ 2010-09-16 14:34 ` Michal Suchanek 2010-09-17 11:29 ` Michal Suchanek ` (10 subsequent siblings) 12 siblings, 0 replies; 19+ messages in thread From: Michal Suchanek @ 2010-09-16 14:34 UTC (permalink / raw) To: qemu-devel Note that most of the section is generated by sysprep (the drivers referencing C:\windows), only small part at the end is generated by my script for additional drivers (references C:\drivers). The previous images that did not have this section worked only on controllers compatible with the MS generic PCI IDE driver (and also on KVM). ** Attachment added: "sysprep mass storage section used in the image" https://bugs.launchpad.net/qemu/+bug/639651/+attachment/1593932/+files/paste_89914 -- DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping https://bugs.launchpad.net/bugs/639651 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in QEMU: New Status in Debian GNU/Linux: New Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. I can post the screenshot if somebody thinks it is interesting enough. The same image works on hardware (which has controllers different from the qemu PIIX3) and in VirtualBox (with the default PIIX4 as well as PIIX3) so long as IO apic is enabled). I am not sure if this is an error with the MS drivers or how they are used in sysprep in this particular case or if his is some strange error in qemu emulation in the PIIX3 controller or elsewhere. The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping 2010-09-15 15:12 [Qemu-devel] [Bug 639651] [NEW] DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping Michal Suchanek 2010-09-16 13:27 ` [Qemu-devel] [Bug 639651] " Michal Suchanek 2010-09-16 14:34 ` Michal Suchanek @ 2010-09-17 11:29 ` Michal Suchanek 2010-09-20 12:55 ` [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed Michal Suchanek ` (9 subsequent siblings) 12 siblings, 0 replies; 19+ messages in thread From: Michal Suchanek @ 2010-09-17 11:29 UTC (permalink / raw) To: qemu-devel ** Description changed: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message - DRIVER_IRQL_NOT_LESS_OR_EQUAL. I can post the screenshot if somebody - thinks it is interesting enough. + DRIVER_IRQL_NOT_LESS_OR_EQUAL. - The same image works on hardware (which has controllers different from - the qemu PIIX3) and in VirtualBox (with the default PIIX4 as well as - PIIX3) so long as IO apic is enabled). - - I am not sure if this is an error with the MS drivers or how they are - used in sysprep in this particular case or if his is some strange - error in qemu emulation in the PIIX3 controller or elsewhere. + It turns out that the error is unrelated to storage drivers. It is + triggered by Synaptics driver installing for the PS2 mouse in kvm (which + does not happen in VirtualBox or on real hardware). The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 -- DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping https://bugs.launchpad.net/bugs/639651 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in QEMU: New Status in Debian GNU/Linux: New Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. It turns out that the error is unrelated to storage drivers. It is triggered by Synaptics driver installing for the PS2 mouse in kvm (which does not happen in VirtualBox or on real hardware). The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed 2010-09-15 15:12 [Qemu-devel] [Bug 639651] [NEW] DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping Michal Suchanek ` (2 preceding siblings ...) 2010-09-17 11:29 ` Michal Suchanek @ 2010-09-20 12:55 ` Michal Suchanek 2010-10-07 9:05 ` Jes Sorensen ` (8 subsequent siblings) 12 siblings, 0 replies; 19+ messages in thread From: Michal Suchanek @ 2010-09-20 12:55 UTC (permalink / raw) To: qemu-devel ** Summary changed: - DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping + DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed -- DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed https://bugs.launchpad.net/bugs/639651 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in QEMU: New Status in Debian GNU/Linux: New Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. It turns out that the error is unrelated to storage drivers. It is triggered by Synaptics driver installing for the PS2 mouse in kvm (which does not happen in VirtualBox or on real hardware). The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed 2010-09-15 15:12 [Qemu-devel] [Bug 639651] [NEW] DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping Michal Suchanek ` (3 preceding siblings ...) 2010-09-20 12:55 ` [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed Michal Suchanek @ 2010-10-07 9:05 ` Jes Sorensen 2010-10-07 9:51 ` Michal Suchanek 2010-10-07 13:31 ` Michal Suchanek ` (7 subsequent siblings) 12 siblings, 1 reply; 19+ messages in thread From: Jes Sorensen @ 2010-10-07 9:05 UTC (permalink / raw) To: qemu-devel Just to be sure, you are not using the virtio-blk driver for Windows here? I have seen similar crashes with the older version of virtio-blk when used on recent versions of KVM. -- DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed https://bugs.launchpad.net/bugs/639651 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in QEMU: New Status in Debian GNU/Linux: New Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. It turns out that the error is unrelated to storage drivers. It is triggered by Synaptics driver installing for the PS2 mouse in kvm (which does not happen in VirtualBox or on real hardware). The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed 2010-10-07 9:05 ` Jes Sorensen @ 2010-10-07 9:51 ` Michal Suchanek 2010-10-07 10:01 ` Jes Sorensen 0 siblings, 1 reply; 19+ messages in thread From: Michal Suchanek @ 2010-10-07 9:51 UTC (permalink / raw) To: Bug 639651; +Cc: qemu-devel On 7 October 2010 11:05, Jes Sorensen <639651@bugs.launchpad.net> wrote: > Just to be sure, you are not using the virtio-blk driver for Windows > here? > > I have seen similar crashes with the older version of virtio-blk when used on > recent versions of KVM. > > -- > DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed > https://bugs.launchpad.net/bugs/639651 > You received this bug notification because you are a member of qemu- > devel-ml, which is subscribed to QEMU. > > Status in QEMU: New > Status in Debian GNU/Linux: New > > Bug description: > Positng the issue here since I did not get any reply on the ML. > > I was trying to update some windows XP (SP3) images in kvm. > > It worked fine several times but last time I added mass storage > drivers to sysprep and now on the second boot after reseal (the first > is mini-setup) I get a BSOD with message > DRIVER_IRQL_NOT_LESS_OR_EQUAL. > > It turns out that the error is unrelated to storage drivers. It is triggered by Synaptics driver installing for the PS2 mouse in kvm (which does not happen in VirtualBox or on real hardware). > > The image is originally created on hardware with MP acpi (not virtualization). > > qemu-kvm 0.12.5+dfsg-2 > Actually the issue is caused by the Synaptics touchpad driver binding to the PS/2 mouse device in qemu. I have no idea how PS/2 devices are detected but the one present in qemu is misdetected as a synaptics touchapd by the Synaptics driver for Windows. As a workaround I have patched my qemu to not enable the PS/2 mouse device. Thanks Michal ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed 2010-10-07 9:51 ` Michal Suchanek @ 2010-10-07 10:01 ` Jes Sorensen 2010-10-07 10:17 ` Michal Suchanek 0 siblings, 1 reply; 19+ messages in thread From: Jes Sorensen @ 2010-10-07 10:01 UTC (permalink / raw) To: Michal Suchanek; +Cc: qemu-devel, Bug 639651 On 10/07/10 11:51, Michal Suchanek wrote: > Actually the issue is caused by the Synaptics touchpad driver binding > to the PS/2 mouse device in qemu. > > I have no idea how PS/2 devices are detected but the one present in > qemu is misdetected as a synaptics touchapd by the Synaptics driver > for Windows. > > As a workaround I have patched my qemu to not enable the PS/2 mouse device. Hi Michal, If you have the time to look, it would be interesting to see what actually goes over the wire to/from the PS/2 driver in QEMU just prior to the crash. It would be good to get this fixed. Cheers, Jes ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed 2010-10-07 10:01 ` Jes Sorensen @ 2010-10-07 10:17 ` Michal Suchanek 2010-10-07 11:54 ` Jes Sorensen 0 siblings, 1 reply; 19+ messages in thread From: Michal Suchanek @ 2010-10-07 10:17 UTC (permalink / raw) To: qemu-devel I have no idea how to log the data. I looked at the qemu man page but it does not even mention the PS/2 mouse as a chardev nor offers an option to log traffic of chardevs without attaching them to a file and thus detaching them from the emulated device. Thanks Michal -- DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed https://bugs.launchpad.net/bugs/639651 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in QEMU: New Status in Debian GNU/Linux: New Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. It turns out that the error is unrelated to storage drivers. It is triggered by Synaptics driver installing for the PS2 mouse in kvm (which does not happen in VirtualBox or on real hardware). The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed 2010-10-07 10:17 ` Michal Suchanek @ 2010-10-07 11:54 ` Jes Sorensen 0 siblings, 0 replies; 19+ messages in thread From: Jes Sorensen @ 2010-10-07 11:54 UTC (permalink / raw) To: qemu-devel On 10/07/10 12:17, Michal Suchanek wrote: > I have no idea how to log the data. > > I looked at the qemu man page but it does not even mention the PS/2 > mouse as a chardev nor offers an option to log traffic of chardevs > without attaching them to a file and thus detaching them from the > emulated device. I would attack it by hacking hw/ps.c a bit to monitor the transactions in ps2_queue() and ps2_read_data(). Cheers, Jes -- DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed https://bugs.launchpad.net/bugs/639651 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in QEMU: New Status in Debian GNU/Linux: New Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. It turns out that the error is unrelated to storage drivers. It is triggered by Synaptics driver installing for the PS2 mouse in kvm (which does not happen in VirtualBox or on real hardware). The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed 2010-09-15 15:12 [Qemu-devel] [Bug 639651] [NEW] DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping Michal Suchanek ` (4 preceding siblings ...) 2010-10-07 9:05 ` Jes Sorensen @ 2010-10-07 13:31 ` Michal Suchanek 2010-10-07 13:33 ` Michal Suchanek ` (6 subsequent siblings) 12 siblings, 0 replies; 19+ messages in thread From: Michal Suchanek @ 2010-10-07 13:31 UTC (permalink / raw) To: qemu-devel Attaching logged PS/2 port communication. ** Attachment added: "PS/2 communication log" https://bugs.launchpad.net/qemu/+bug/639651/+attachment/1677112/+files/qemu-ps2.log -- DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed https://bugs.launchpad.net/bugs/639651 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in QEMU: New Status in Debian GNU/Linux: New Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. It turns out that the error is unrelated to storage drivers. It is triggered by Synaptics driver installing for the PS2 mouse in kvm (which does not happen in VirtualBox or on real hardware). The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed 2010-09-15 15:12 [Qemu-devel] [Bug 639651] [NEW] DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping Michal Suchanek ` (5 preceding siblings ...) 2010-10-07 13:31 ` Michal Suchanek @ 2010-10-07 13:33 ` Michal Suchanek 2012-09-10 17:40 ` Michal Suchanek ` (5 subsequent siblings) 12 siblings, 0 replies; 19+ messages in thread From: Michal Suchanek @ 2010-10-07 13:33 UTC (permalink / raw) To: qemu-devel For reference attaching the patch used for obtaining the log. ** Patch added: "patch used to obtain the above log" https://bugs.launchpad.net/qemu/+bug/639651/+attachment/1677122/+files/ps2dump.diff -- DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed https://bugs.launchpad.net/bugs/639651 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in QEMU: New Status in Debian GNU/Linux: New Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. It turns out that the error is unrelated to storage drivers. It is triggered by Synaptics driver installing for the PS2 mouse in kvm (which does not happen in VirtualBox or on real hardware). The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed 2010-09-15 15:12 [Qemu-devel] [Bug 639651] [NEW] DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping Michal Suchanek ` (6 preceding siblings ...) 2010-10-07 13:33 ` Michal Suchanek @ 2012-09-10 17:40 ` Michal Suchanek 2017-01-18 15:56 ` Thomas Huth ` (4 subsequent siblings) 12 siblings, 0 replies; 19+ messages in thread From: Michal Suchanek @ 2012-09-10 17:40 UTC (permalink / raw) To: qemu-devel I guess the problem here is that qemu emulates some very basic mouse (reported as PS/2 compatible mouse in Windows) whereas real hardware usually has a fancy mouse (reported as MS Explorer compatible mouse in Windows). I don't know how PS/2 mice are detected but due to different mice being detected differently there is obviously some detection mechanism. The Windos device IDs in a Touchpad driver that does not exhibit the problem (synaptics v8) [SynMfg] %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN010D %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN010E %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN010F %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0110 %PS2.SynDeviceDesc% = HP_GROUP3_PS2_Inst,*SYN0111 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0112 %PS2.SynDeviceDesc% = HP__0100__PS2_Inst,*SYN0113 %PS2.SynDeviceDesc% = HP__0100__PS2_Inst,*SYN0114 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0115 %PS2.SynDeviceDesc% = HP_GROUP3_PS2_Inst,*SYN0116 %PS2.SynDeviceDesc% = HP_GROUP1_PS2_Inst,*SYN0117 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0118 %PS2.SynDeviceDesc% = HP_GROUP5_PS2_Inst,*SYN0119 %PS2.SynDeviceDesc% = HP_GROUP6_PS2_Inst,*SYN011A %PS2.SynDeviceDesc% = HP_GROUP4_PS2_Inst,*SYN011B %PS2.SynDeviceDesc% = HP_GROUP3_PS2_Inst,*SYN011C %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN011D %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN011E %PS2.SynDeviceDesc% = HP_GROUP3_PS2_Inst,*SYN011F %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0120 %PS2.SynDeviceDesc% = HP_GROUP3_PS2_Inst,*SYN0121 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0122 %PS2.SynDeviceDesc% = HP_GROUP7_PS2_Inst,*SYN0123 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0124 %PS2.SynDeviceDesc% = HP_GROUP3_PS2_Inst,*SYN0125 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0126 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0127 %PS2.SynDeviceDesc% = HP_GROUP3_PS2_Inst,*SYN0128 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0129 %PS2.SynDeviceDesc% = HP_GROUP3_PS2_Inst,*SYN012A %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN012B %PS2.SynDeviceDesc% = HP_GROUP3_PS2_Inst,*SYN012C and in drivers that do exhibit the problem (note the first device): Synaptics v9 [SynMfg] %PS2.SynDeviceDesc% = HP__0100__PS2_Inst,*PNP0F13 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN010D %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN010E %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN010F %PS2.SynDeviceDesc% = HP_GROUP8_PS2_Inst,*SYN0110 %PS2.SynDeviceDesc% = HP_GROUP9_PS2_Inst,*SYN0111 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0112 %PS2.SynDeviceDesc% = HP__0100__PS2_Inst,*SYN0113 %PS2.SynDeviceDesc% = HP__0100__PS2_Inst,*SYN0114 %PS2.SynDeviceDesc% = HP_GROUP8_PS2_Inst,*SYN0115 %PS2.SynDeviceDesc% = HP_GROUP9_PS2_Inst,*SYN0116 %PS2.SynDeviceDesc% = HP_GROUP1_PS2_Inst,*SYN0117 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0118 %PS2.SynDeviceDesc% = HP_GROUP5_PS2_Inst,*SYN0119 %PS2.SynDeviceDesc% = HP_GROUP6_PS2_Inst,*SYN011A %PS2.SynDeviceDesc% = HP_GROUP4_PS2_Inst,*SYN011B %PS2.SynDeviceDesc% = HP_GROUP9_PS2_Inst,*SYN011C %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN011D %PS2.SynDeviceDesc% = HP_GROUP8_PS2_Inst,*SYN011E %PS2.SynDeviceDesc% = HP_GROUP9_PS2_Inst,*SYN011F %PS2.SynDeviceDesc% = HP_GROUP8_PS2_Inst,*SYN0120 %PS2.SynDeviceDesc% = HP_GROUP9_PS2_Inst,*SYN0121 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0122 %PS2.SynDeviceDesc% = HP_GROUP7_PS2_Inst,*SYN0123 %PS2.SynDeviceDesc% = HP_GROUP8_PS2_Inst,*SYN0124 %PS2.SynDeviceDesc% = HP_GROUP9_PS2_Inst,*SYN0125 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0126 %PS2.SynDeviceDesc% = HP_GROUP8_PS2_Inst,*SYN0127 %PS2.SynDeviceDesc% = HP_GROUP9_PS2_Inst,*SYN0128 %PS2.SynDeviceDesc% = HP_GROUP8_PS2_Inst,*SYN0129 %PS2.SynDeviceDesc% = HP_GROUP9_PS2_Inst,*SYN012A %PS2.SynDeviceDesc% = HP_GROUP8_PS2_Inst,*SYN012B %PS2.SynDeviceDesc% = HP_GROUP9_PS2_Inst,*SYN012C %PS2.SynDeviceDesc% = HP_GROUP8_PS2_Inst,*SYN012D %PS2.SynDeviceDesc% = HP_GROUP9_PS2_Inst,*SYN012E %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN012F %PS2.SynDeviceDesc% = HP_GROUP8_PS2_Inst,*SYN0130 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0131 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0132 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0133 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0134 %PS2.SynDeviceDesc% = HP_GROUP10_PS2_Inst,*SYN0135 %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN0136 %PS2.SynDeviceDesc% = HP_GROUP3_PS2_Inst,*SYN0137 %PS2.SynDeviceDesc% = HP_GROUP8_PS2_Inst,*SYN0138 %PS2.SynDeviceDesc% = HP_GROUP9_PS2_Inst,*SYN0139 %PS2.SynDeviceDesc% = HP_GROUP9_PS2_Inst,*SYN013A %PS2.SynDeviceDesc% = HP_GROUP8_PS2_Inst,*SYN013B %PS2.SynDeviceDesc% = HP_GROUP9_PS2_Inst,*SYN013C %PS2.SynDeviceDesc% = HP_GROUP8_PS2_Inst,*SYN013D %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN013E %PS2.SynDeviceDesc% = HP_GROUP2_PS2_Inst,*SYN013F Syanptics v14 [SynMfg] %PS2.DeviceDesc% = DEFAULT__0000__PS2_Inst,*PNP0F13,*PNP0F0E,*PNP0F03,*PNP0F12 ; Std PS/2 mouse %PS2.SynDeviceDesc% = DEFAULT__0000__PS2_Inst,*SYN0002 ; Synaptics PS2 TouchPad Either of the synaptics drivers v9 and v14 would bind to the qemu mouse and crash the system when installed. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/639651 Title: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed Status in QEMU: New Status in Debian GNU/Linux: New Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. It turns out that the error is unrelated to storage drivers. It is triggered by Synaptics driver installing for the PS2 mouse in kvm (which does not happen in VirtualBox or on real hardware). The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/639651/+subscriptions ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed 2010-09-15 15:12 [Qemu-devel] [Bug 639651] [NEW] DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping Michal Suchanek ` (7 preceding siblings ...) 2012-09-10 17:40 ` Michal Suchanek @ 2017-01-18 15:56 ` Thomas Huth 2017-01-20 18:31 ` Michal Suchanek 2017-02-08 8:59 ` Thomas Huth ` (3 subsequent siblings) 12 siblings, 1 reply; 19+ messages in thread From: Thomas Huth @ 2017-01-18 15:56 UTC (permalink / raw) To: qemu-devel QEMU 0.12 is pretty much outdated nowadays ... can you still reproduce this problem with the latest version of QEMU, or can we close this ticket nowadays? ** Changed in: qemu Status: New => Incomplete -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/639651 Title: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed Status in QEMU: Incomplete Status in Debian: New Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. It turns out that the error is unrelated to storage drivers. It is triggered by Synaptics driver installing for the PS2 mouse in kvm (which does not happen in VirtualBox or on real hardware). The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/639651/+subscriptions ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed 2017-01-18 15:56 ` Thomas Huth @ 2017-01-20 18:31 ` Michal Suchanek 0 siblings, 0 replies; 19+ messages in thread From: Michal Suchanek @ 2017-01-20 18:31 UTC (permalink / raw) To: qemu-devel Does qemu allow to disable the PS/2 port now? If so then there is easy workaround in case something similar ever happens. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/639651 Title: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed Status in QEMU: Incomplete Status in Debian: New Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. It turns out that the error is unrelated to storage drivers. It is triggered by Synaptics driver installing for the PS2 mouse in kvm (which does not happen in VirtualBox or on real hardware). The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/639651/+subscriptions ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed 2010-09-15 15:12 [Qemu-devel] [Bug 639651] [NEW] DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping Michal Suchanek ` (8 preceding siblings ...) 2017-01-18 15:56 ` Thomas Huth @ 2017-02-08 8:59 ` Thomas Huth 2018-10-11 9:47 ` Thomas Huth ` (2 subsequent siblings) 12 siblings, 0 replies; 19+ messages in thread From: Thomas Huth @ 2017-02-08 8:59 UTC (permalink / raw) To: qemu-devel Hmm, I'm not aware of a way to disable the PS2 mouse in QEMU yet. Looking at your other related bug (https://bugs.launchpad.net/qemu/+bug/813546), I think you might need to discuss that patch on the qemu-devel mailing list. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/639651 Title: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed Status in QEMU: Incomplete Status in Debian: New Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. It turns out that the error is unrelated to storage drivers. It is triggered by Synaptics driver installing for the PS2 mouse in kvm (which does not happen in VirtualBox or on real hardware). The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/639651/+subscriptions ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed 2010-09-15 15:12 [Qemu-devel] [Bug 639651] [NEW] DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping Michal Suchanek ` (9 preceding siblings ...) 2017-02-08 8:59 ` Thomas Huth @ 2018-10-11 9:47 ` Thomas Huth 2019-04-18 5:35 ` Thomas Huth 2019-06-18 4:17 ` Launchpad Bug Tracker 12 siblings, 0 replies; 19+ messages in thread From: Thomas Huth @ 2018-10-11 9:47 UTC (permalink / raw) To: qemu-devel ** Package changed: debian => qemu (Debian) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/639651 Title: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed Status in QEMU: Incomplete Status in qemu package in Debian: New Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. It turns out that the error is unrelated to storage drivers. It is triggered by Synaptics driver installing for the PS2 mouse in kvm (which does not happen in VirtualBox or on real hardware). The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/639651/+subscriptions ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed 2010-09-15 15:12 [Qemu-devel] [Bug 639651] [NEW] DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping Michal Suchanek ` (10 preceding siblings ...) 2018-10-11 9:47 ` Thomas Huth @ 2019-04-18 5:35 ` Thomas Huth 2019-06-18 4:17 ` Launchpad Bug Tracker 12 siblings, 0 replies; 19+ messages in thread From: Thomas Huth @ 2019-04-18 5:35 UTC (permalink / raw) To: qemu-devel ** Changed in: qemu (Debian) Status: New => Incomplete -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/639651 Title: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed Status in QEMU: Incomplete Status in qemu package in Debian: Incomplete Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. It turns out that the error is unrelated to storage drivers. It is triggered by Synaptics driver installing for the PS2 mouse in kvm (which does not happen in VirtualBox or on real hardware). The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/639651/+subscriptions ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed 2010-09-15 15:12 [Qemu-devel] [Bug 639651] [NEW] DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping Michal Suchanek ` (11 preceding siblings ...) 2019-04-18 5:35 ` Thomas Huth @ 2019-06-18 4:17 ` Launchpad Bug Tracker 12 siblings, 0 replies; 19+ messages in thread From: Launchpad Bug Tracker @ 2019-06-18 4:17 UTC (permalink / raw) To: qemu-devel [Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/639651 Title: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed Status in QEMU: Expired Status in qemu package in Debian: Incomplete Bug description: Positng the issue here since I did not get any reply on the ML. I was trying to update some windows XP (SP3) images in kvm. It worked fine several times but last time I added mass storage drivers to sysprep and now on the second boot after reseal (the first is mini-setup) I get a BSOD with message DRIVER_IRQL_NOT_LESS_OR_EQUAL. It turns out that the error is unrelated to storage drivers. It is triggered by Synaptics driver installing for the PS2 mouse in kvm (which does not happen in VirtualBox or on real hardware). The image is originally created on hardware with MP acpi (not virtualization). qemu-kvm 0.12.5+dfsg-2 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/639651/+subscriptions ^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~2019-06-18 4:32 UTC | newest] Thread overview: 19+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2010-09-15 15:12 [Qemu-devel] [Bug 639651] [NEW] DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP after sysprepping Michal Suchanek 2010-09-16 13:27 ` [Qemu-devel] [Bug 639651] " Michal Suchanek 2010-09-16 14:34 ` Michal Suchanek 2010-09-17 11:29 ` Michal Suchanek 2010-09-20 12:55 ` [Qemu-devel] [Bug 639651] Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL booting WIndows XP with Synaptics driver installed Michal Suchanek 2010-10-07 9:05 ` Jes Sorensen 2010-10-07 9:51 ` Michal Suchanek 2010-10-07 10:01 ` Jes Sorensen 2010-10-07 10:17 ` Michal Suchanek 2010-10-07 11:54 ` Jes Sorensen 2010-10-07 13:31 ` Michal Suchanek 2010-10-07 13:33 ` Michal Suchanek 2012-09-10 17:40 ` Michal Suchanek 2017-01-18 15:56 ` Thomas Huth 2017-01-20 18:31 ` Michal Suchanek 2017-02-08 8:59 ` Thomas Huth 2018-10-11 9:47 ` Thomas Huth 2019-04-18 5:35 ` Thomas Huth 2019-06-18 4:17 ` Launchpad Bug Tracker
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.