[lucid kvm-qemu]High cpu usage when moving mouse
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-input-vmmouse (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Binary package hint: xserver-
Running lucid beta1 64bit in kvm-qemu vm:
Sometime prior to beta1, system was responsive.
Now I can barely move the mouse without causing one of the cpus on the host machine to peg out.
And /usr/bin/X using all of the cpu resources on the guest machine.
After removing the xserver-
Subsequent reboot was responsive too.
After reinstalling the package, the system became sluggish again.
I notice in the changelog that 1:12.6.5-2ubuntu2 through ubuntu4 were released 2010-03-02 to 05.
This is about the time this issue occurred.
1:12.6.5-2ubuntu3 had a change regarding kvm detection:
* debian/
vmmouse_detect will work in kvm again.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xserver-
ProcVersionSign
Uname: Linux 2.6.32-18-generic x86_64
Architecture: amd64
CurrentDmesg: [ 16.901084] eth0: no IPv6 routers present
Date: Thu Apr 1 01:53:32 2010
DkmsStatus: Error: [Errno 2] No such file or directory
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: xserver-
dmi.bios.date: 01/01/2007
dmi.bios.vendor: QEMU
dmi.bios.version: QEMU
dmi.chassis.type: 1
dmi.modalias: dmi:bvnQEMU:
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-18-generic
Changed in xserver-xorg-input-vmmouse (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
I removed 1:12.6.5-4ubuntu1 and installed 1:12.6.5-2ubuntu4 from launchpad, and the system was responsive after reboot. Then, I installed 1:12.6.5-4ubuntu1 back and the system had poor response again after reboot.
What I don't understand though is that prior to today I had 1:12.6.5-2ubuntu4, but I had responsiveness issues then too.
I could try a fresh install tomorrow and see if I get the same results.