[Solved] Leaving guest while mousedown freezes the guest

[OoDeLally]

Hello,

I run a Debian 8.2 guest on a W7 host. The Guest additions are installed.

I use 2 monitors with the guest on the left, and the host on the right.
The Mouse Integration allows me to go from a monitor to another with the cursor. This is very convenient.

However, most scrollbars are on the right border of the guest. If while scrolling in the guest (in mousedown state), my cursor accidentally leaves the guest, it results in the following:

- The guest window completely freezes for ~8 secs. It resumes immediately after this duration.
- During these 8 secs, I can still go to the host system and do stuff. I noticed that during this time, the keyboard input is lagging on host. It stops lagging when the 8 secs are expired.

I suspect there is a problem related to missing the mouseup event when the cursor leaves the guest zone. But I'm no expert.

Since the whole VM window freezes, I dont believe the problem comes from the guest OS, but more from virtualbox VM that runs it.

It is a very annoying bug, as I obviously scroll very often while using the guest. I have to avoid leaving the guest zone while scrolling. This is difficult since the host zone is adjacent to the scroll bar.

I would be curious to know if this problem exists with other host/guest system.

Let me know if you need further info.

Thanks

[OoDeLally]

bump

[mpack]

You should provide a VM log as a matter of course when asking questions, otherwise you might get ignored in favor of folks who make it easier to help them. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

One thing I won't get from the log: is Drag and Drop enabled?

[socratis]

One thing I won't get from the log: is Drag and Drop enabled?

Hmm... Just out of curiosity... Why don't you get that in the log? From a random log of one of my VMs, it's right there at the beginning:

00:00:09.634188 Shared clipboard service loaded
00:00:09.634204 Shared clipboard mode: Bidirectional
00:00:09.658447 Drag and drop service loaded
00:00:09.658464 Drag and drop mode: Bidirectional

[mpack]

Ah yes, I forgot that had been added.

[OoDeLally]

You should provide a VM log as a matter of course when asking questions, otherwise you might get ignored in favor of folks who make it easier to help them. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

One thing I won't get from the log: is Drag and Drop enabled?

Hello,

Thank you for your answer.

I booted up debian, tried the drag&drop thing, waited for the unfreeze, and turned off the VM immediatly after.
I attached to this post the log.

I hope it helps!

Thank you

[mpack]

00:00:01.010630 Host RAM: 8135MB total, 4659MB available
...
00:00:01.594206 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 GB)

Not much RAM left for host use. Reduce to 2GB.

00:00:01.594201 NumCPUs <integer> = 0x0000000000000002 (2)
...
00:00:01.975863 CPUM: Physical host cores: 2

No cores at all left for host use. Reduce to 1.

00:00:13.233741 VMMDev: Guest Additions information report: Version 4.3.26 r98988 '4.3.26'

Guest Additions out of date. Since mouse input is part of the GAs we would need to know if the problem still exists in the current GAs.

[OoDeLally]

Hello,

Thank you for your advice.
This is strange. I have a Athlon X4 860K, which is a quadcore. VB only sees 2 CPUs. I ran across some similar forums threads, where people had this issue, but most of time, it was because the CPU had only 2 physical cores with hyperthreading.
But I believe my CPU really has 4 physical cores (http://www.cpu-world.com/CPUs/Bulldozer ... 0860K.html). Let me know if I'm wrong.

Anyway I reduced the VM to 1 CPU and 2GB of RAM. I still have this problem.

Code: Select all

00:00:18.024933 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices

I attached the logs.
Let me know if you need more info about anything.

Thank you.

[mpack]

AMD uses a different definition of "core" which the rest of the world has yet to catch up with. Google for "AMD CPU cores lawsuit". I don't know if it applies to the Athlon X4.

[OoDeLally]

I see. Thank you for the info.
However, I still have to problem with 1CPU and 2GB Ram (see my last reply).
Is there something else we can look at ?

[mpack]

Well, the only thing I notice is that you are using 5.0.0 - which is by definition the buggiest member of the 5.x family. If you expect to benefit from bugfixes you need to be using the current maintenance version. Today that is 5.0.14.

It's strange, we've recently had a whole spate of people using 5.0.0... did you all buy a second hand VM from the same guy or something?

[OoDeLally]

Hey guys,

I just installed the VBoxAdditions 5.0.14, and it solved my problem! I was in 4.x.x.

Thanks!

[mpack]

Thanks for reporting back.

I was in 4.x.x.

Uh, your own log said you had 5.0.0, as already discussed above. Best to keep the information accurate I think.

[OoDeLally]

Thanks for reporting back.

I was in 4.x.x.

Uh, your own log said you had 5.0.0, as already discussed above. Best to keep the information accurate I think.

Yes I had 5.x.x VB, but still with 4.x.x guest addition