Opened 9 years ago
Closed 7 years ago
#14845 closed defect (obsolete)
Ubuntu host "OHCI#0: Lagging too far behind..." 100% cpu core load
Reported by: | ehallq | Owned by: | |
---|---|---|---|
Component: | USB | Version: | VirtualBox 5.0.10 |
Keywords: | cpu, load, usb | Cc: | |
Guest type: | Linux | Host type: | Linux |
Description
I recently upgraded my setup from running Domoticz on RPi2 to a vm on my new server. To use Domoticz to control my lights I have a USB device named rfxtrx433e. This works well, and I didnt have any problems..that was until I watched my cpu load. The vm ran at 100% on 1 core (watching from hostside). I ssh into my vm and "top" reveiled that nothing had a load over 1-5%, so the problem shouldnt be anything on the actual vm. When I deactivated the rfxtrx433e from domoticz i.e. turning off the communication with the usb device, then the load dropped instantly. When I activated the rfx again, it maintain around 12% load for a while, but after getting this message below in the VBox.log once or twice, the cpu load jumped up to 100% again. Any idea to solve this?
00:02:56.660142 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices
I use the latest virtualbox with ubuntu server 14.04 LTS. The cpu is a pentium G3258. The device is hooked up using USB 2.0
I am a member of the vboxusers group. The usb device works without any problem all the time, however the cpu load is 100% on the core the vm runs on, doesnt affect my everyday use, but it generates heat :(
Result of top command on my server:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 13355 erik 20 0 1626640 406784 381624 S 96.1 2.5 0:17.82 VBoxHeadle+ (DOMOTICZ VM) 12339 erik 20 0 2326268 413164 370116 S 1.0 2.5 12:44.97 VBoxHeadle+ 12280 erik 20 0 1403096 151996 127748 S 0.3 0.9 7:54.48 VBoxHeadle+ /.....
Result of top command on vm:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1212 erik 20 0 105780 4688 3612 R 0.4 0.2 0:00.02 sshd: erik@+ 1 root 20 0 33484 3964 2672 S 0.0 0.2 0:00.75 /sbin/init 2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kthreadd]
As you can see, there is no problem in the actual vm.
Attachments (1)
Change History (2)
by , 9 years ago
comment:1 by , 7 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Please reopen if this is still relevant with a recent version of VirtualBox.
Vbox log