[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:
** 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
** 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
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-
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:
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
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
On 7 October 2010 11:05, Jes Sorensen 639...@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
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
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
--
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
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
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
** 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
14 matches
Mail list logo
