Changes between Initial Version and Version 1 of Ticket #14501, comment 13

Ticket #14501, comment 13

initial	v1
13	13	In summary, until 5.0.30, I did not experience the issue with the mouse. Falling back to 5.1.10 in the VBox 5.1 series seems to remediate the problem (given 3 days without issue). My thinking is that maybe that i/o fix that was applied to both 5.0.32 and 5.1.12 is the source of my mouse problem since those were the point releases where the undesirable behavior began. This is only theory, and it's only a thought.
14	14
15		At any rate, I am debating altering one of my VMs -- the one that seemed to be most vulnerable to this mouse problem -- to use KVM paravirtualization instead of "None". That way, we can see if using KVM is or is not the/a culprit in this.
	15	At any rate, I am debating altering one of my VMs -- the one that seemed to be most vulnerable to this mouse problem -- to use KVM paravirtualization instead of "None" on 5.1.10. That way, we can see if using KVM is or is not the/a culprit in this.