[Solved] Mouse stucks and then only works in certain areas.

[softmonaut]

Version 6.0.10 r132072 (Qt5.9.5), Host: LM 19.1, Guest: LM 19.1
Sometimes the mouse stops working properly. It can be moved around completely, mouseover works on menu items in programs (they are highlighted) but nothing except the items in the taskbar is clickable. The problem often occurs while using Intellij IDEA but I am not sure if that is the cause of the problem. I have already tried both settings PS2 / USB tablet: no difference.
I am aware that there are many contributions to the subject of mouse problems. However, I have not found any, where obviously only the Taskbar still works properly.

Does anyone know (a pointer to) a workaround or a solution to this problem?

Thanks in advance
Jörg

[socratis]

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe or recreate the problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[softmonaut]

Unfortunately, it took a little bit longer, because the problem has not yet reappeared on the Linux Mint host/guest combination, after I had reactivated a previously deactivated IPv6. Whether there is a connection is not clear. In any case, the observed phenomenon often occurred even with Firefox open.
The attached log comes from a Windows 8.1 host with Linux Mint guest as described above. The observable error corresponds to the above description.

[socratis]

The attached log comes from a Windows 8.1 host with Linux Mint guest

00:00:01.926014 Guest OS type: 'Linux_64'

You got to pick the correct template, in which case it is 'Ubuntu_64' (most probably, not 32).

00:00:01.965018 NumCPUs <integer> = 0x0000000000000004 (4)
00:00:02.589666 CPUM: Physical host cores: 4
00:00:02.589899 Full Name: "Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz"

You have assigned all your CPUs to the VM. The host is going to run low on resources, since VirtualBox cares about physical processors (cores), not logical ones (threads).

Just check the link for your CPU above, and make sure you read the text in the "?" next to the "# of Cores" and "# of Threads" in that Intel page...

00:00:01.965232   VMSVGA3dEnabled  <integer> = 0x0000000000000001 (1)
00:00:01.965240   VMSVGAEnabled    <integer> = 0x0000000000000001 (1)
00:00:01.965241   VRamSize         <integer> = 0x0000000008000000 (134 217 728, 128 MB)

You seem to have the VBoxSVGA Graphics Controller selected. This is for Windows guests, not Linux guests. Go to the VM Settings » Display » Screen. Change the Graphics controller from "VBoxSVGA" to "VMSVGA".

00:00:17.406364 VMMDev: Guest Additions information report: Version 5.2.32 r132056 '5.2.32_Ubuntu'

Not only you have an older version of the Guest Additions (GAs) installed, but you have the forked version installed. You need to install the Guest Additions that match your main VirtualBox program.

With the VM window having the focus, go to the host's menu "Devices" » "Insert Guest Additions CD Image...". If not prompted by auto-run, run "VBoxLinuxAdditions.run" from the CD. Make sure there are no errors or suggestions during the install. You can safely ignore the "modprobe vboxsf" one.



BTW, you have a hardening problem in your Nvidia drivers:

00:00:02.932119 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll:
    rc=VERR_CR_PKCS7_KEY_USAGE_MISMATCH fImage=1 fProtect=0x0 fAccess=0x0
    \Device\HarddiskVolume2\Windows\System32\nvd3dumx.dll: fKeyUsage=0x0,
    missing 0x1: \Device\HarddiskVolume2\Windows\System32\nvd3dumx.dll

Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues for some generic guidelines/ideas.

[softmonaut]

Dear socratis,

Thank you very much for your helpful hints.
The number of CPUs is displayed with 8 by VB Manager GUI. Therefore, I assumed that selecting 4 CPUs was not a bad choice. Anyway, I reduced to 2 CPUs now.
The selection options for the video driver are also not helpful. I did not know that VMSVGA is the choice for Linux (until know)
In my distress I installed the following after installing the desired guest additions version

Code: Select all

sudo apt install virtualbox-guest-x11 virtualbox-guest-utils virtualbox-guest-dkms (DOES NOT WORK HERE)

This threw me unnoticed back to the 5.2.32 r132056 '5.2.32_Ubuntu' version.

After correcting all this stuff it's now:

Code: Select all

00:00:01.696616   Guest OS type: 'Ubuntu_64'
00:00:01.729875   NumCPUs <integer> = 0x0000000000000002 (2)
00:00:01.730007   VMSVGA3dEnabled    <integer> = 0x0000000000000001 (1)
00:00:01.730008   VMSVGAEnabled      <integer> = 0x0000000000000001 (1)
00:00:01.730010   VRamSize           <integer> = 0x0000000008000000 (134 217 728, 128 MB)  (Can't see any changes after switching to VMSVGA here?)
00:00:02.511722   VMMDev: Guest Log: BIOS: VirtualBox 6.0.12

The hardening thread is gone after updating nvidia drivers.

Again, thanks a lot.
Regards Jörg

[socratis]

Thank you very much for your helpful hints.

Sure thing...
But you didn't tell me if your initial problem is fixed or not.

[softmonaut]

Hi socratis,

sure you wanna know!

The initial problem seems to be fixed, at least I could not observe the mouse problems after the changes again. Concurrently with the installation of the latest Nvidia drivers, the notice inside the LM guest that the software rendering mode is active also disappeared.
As a result, however, there are several system crashes with checkerboard pattern on the screen, which were probably due to the latest Nvidia driver, which I had downloaded directly from the Nvidia website. After installing the stock video driver suggested by Microsoft, the reference to the active software rendering mode appears and some hardening errors occur again:

Code: Select all

00:00:02.948732 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_PKCS7_KEY_USAGE_MISMATCH fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Windows\System32\nvd3dumx.dll: fKeyUsage=0x0, missing 0x1: \Device\HarddiskVolume2\Windows\System32\nvd3dumx.dll
00:00:02.948860 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\nvd3dumx.dll': rcNt=0xc0000190
00:00:02.949032 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_CR_PKCS7_KEY_USAGE_MISMATCH fImage=1 fProtect=0x0 fAccess=0x0 cHits=1 \Device\HarddiskVolume2\Windows\System32\nvd3dumx.dll
00:00:02.949064 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\nvd3dumx.dll': rcNt=0xc0000190

To what extent this constellation is stable I can not say yet.

Bye
Jörg

[socratis]

The initial problem seems to be fixed, at least I could not observe the mouse problems after the changes again.

Good, that's all I care for as far as this thread goes, I can mark it as [Solved].

If you keep having other issues, open a new thread with an appropriate title, we like to observe the "One issue, one thread" rule...