WinXP I/O stutter
-
For some unfortunate reasons I still have to use WinXP, running in a VirtualBox. After installing .NET 4.0 I get some kind of I/O stutter, which shows by the mouse pointer getting stuck in place or keyboard input not being recognized for roughly a second. I had the same thing when XP was still running "outside" of VirtualBox, so I don't think it's a VirtualBox issue. I have zero clue how I could remedy or investigate this further. Google isn't helping. Anyone got some kind of idea?
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
-
For some unfortunate reasons I still have to use WinXP, running in a VirtualBox. After installing .NET 4.0 I get some kind of I/O stutter, which shows by the mouse pointer getting stuck in place or keyboard input not being recognized for roughly a second. I had the same thing when XP was still running "outside" of VirtualBox, so I don't think it's a VirtualBox issue. I have zero clue how I could remedy or investigate this further. Google isn't helping. Anyone got some kind of idea?
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
Following WinXP, Microsoft made an effort to make the OS more game friendly by improving the async handling of commands. I do not think there is any kind of 'fix' within WinXP.
-
For some unfortunate reasons I still have to use WinXP, running in a VirtualBox. After installing .NET 4.0 I get some kind of I/O stutter, which shows by the mouse pointer getting stuck in place or keyboard input not being recognized for roughly a second. I had the same thing when XP was still running "outside" of VirtualBox, so I don't think it's a VirtualBox issue. I have zero clue how I could remedy or investigate this further. Google isn't helping. Anyone got some kind of idea?
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
More details needed. Type of keyboard and mouse? Type of machine (basics).
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
-
More details needed. Type of keyboard and mouse? Type of machine (basics).
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Are you kidding me? He's running it in a VM.
-
More details needed. Type of keyboard and mouse? Type of machine (basics).
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Meanwhile I made a new observation: Looks like it's not specifically I/O but the task scheduling as a whole that freezes up. Keyboard is a Cherry MX3000 connected via PS/2, Mouse is a Logitech G5 (USB..). Host system is a i7-2600 running Windows 7. No problems there at all. Only in the WinXP-VirtualBox and only after installing .NET 4.0.
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
-
For some unfortunate reasons I still have to use WinXP, running in a VirtualBox. After installing .NET 4.0 I get some kind of I/O stutter, which shows by the mouse pointer getting stuck in place or keyboard input not being recognized for roughly a second. I had the same thing when XP was still running "outside" of VirtualBox, so I don't think it's a VirtualBox issue. I have zero clue how I could remedy or investigate this further. Google isn't helping. Anyone got some kind of idea?
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
Sascha Lefèvre wrote:
Google isn't helping
BLASPHEMY! Google knows all!
-
For some unfortunate reasons I still have to use WinXP, running in a VirtualBox. After installing .NET 4.0 I get some kind of I/O stutter, which shows by the mouse pointer getting stuck in place or keyboard input not being recognized for roughly a second. I had the same thing when XP was still running "outside" of VirtualBox, so I don't think it's a VirtualBox issue. I have zero clue how I could remedy or investigate this further. Google isn't helping. Anyone got some kind of idea?
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
Hi, If your mouse is freezing in the VM... then I doubt there is much you can do about it besides upgrading to a better CPU with a larger L1,L2,L3 CPU cache and perhaps more cores. That's a clear sign of thread i/o starvation in the VirtualBox parent process. I would be willing to bet that the root cause is TLB cache misses... Best Wishes, -David Delaune
-
Are you kidding me? He's running it in a VM.
Not at all. Let's say he was a wireless mouse. Not unusual at all to have performance issues with these things. I would dig into the polling rate for the mouse. Smells like the 4.0 update changed some behavior. Long ago, I always tried to avoid a s/w polled mouse - you were very dependent on your system performance. It's been years since I worried about it, as the processors are just so fast it's not much of an issue. I use VM Workstation, and one of the chronic issues there is with the vm tools going bat crap crazy. It has gotten better, but when things go south, the first thing you try is a re-installation of vm tools.
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759