[Solved] Mouse pointer disappears when guest captures it

[cdgarcia]

To all,

I am sorry but I have searched far and wide and could not find the resolution for this problem. I installed Virtualbox 6.0.4 as well as the 6.0.4 extension pack on my Mac with macOS High Sierra 10.13.6. Downloaded OEL 7.6 ISO image and created a guest but, when I start it, after the click the Capture button, the mouse pointer disappears and lose control of the mouse in the guest OS (I can regain control of it clicking the host key). Keyboard seems to be working fine.

Could someone point me in the right direction to resolve this?

Thanks

[socratis]

Shut down the VM (completely, not paused or saved-state), go to the VM Settings » System » Motherboard » Pointing Device: change that to USB Tablet.

If that doesn't address the problem, 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 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.

[cdgarcia]

Thank you for your help. Attached is the log.

[cdgarcia]

Tested using combination os PS/2 and USB to no avail, still have the issue. Keyboard seems to work though

[mpack]

First, you need to install OEL Linux properly: according to the log you are still booting it in demo mode from a (virtual) CD.

Next, since you now have a persistent installation, you can install the Guest Additions, which provides mouse cursor integration among other things. See the user manual for GAs installation instructions.

[socratis]

I compared your log with my "Oracle Linux 7.6" VM. There are few differences, noted below:

00:00:13.078104 VMSVGA3dEnabled  <integer> = 0x0000000000000000 (0)
00:00:13.078105 VMSVGAEnabled    <integer> = 0x0000000000000001 (1)
00:00:13.078105 VMSVGAPciId      <integer> = 0x0000000000000001 (1)
00:00:13.078105 VRamSize         <integer> = 0x0000000001000000 (16 777 216, 16 MB)

Shut down the VM. Go to the VM Settings » Display » Screen. Change the Graphics controller from "VMSVGA" to "VBoxVGA". Enable 3D acceleration. Increase the VRAM to the max MB. Start the VM...

I have another unexplained question. Compare the start times of your VM with mine:

00:00:13.012377 VirtualBox VM 6.0.4 r128413 darwin.amd64 (Jan 25 2019 19:26:11) release log
00:00:00.927915 VirtualBox VM 6.0.5 r128870 darwin.amd64 (Feb 15 2019 15:06:08) release log

It takes you 13" just to say "Hello world!". That seems really awfully slow. Any explanations?

First, you need to install OEL Linux properly: according to the log you are still booting it in demo mode from a (virtual) CD.

Maybe that's the problem, because there's no mouse, the OP can't continue with the installation. I think it might be the VMSVGA doing that...

you can install the Guest Additions, which provides mouse cursor integration among other things

No need for that. The OP, just like me, is using the USB Tablet option, there's no need for GAs for that. The GAs are needed only in the PS/2 mouse case.

[cdgarcia]

Hi there,

Quite a bummer, tried the recommendations and still no change, I have attached a new log.

Regarding the performance, it is a new MacBook Pro 15-inch (i7 with 32GB) running macOS 10.13.6). Not sure what is causing the issue.

Wondering if there is some company software installation that is causing this problem...

- Jorge

[cdgarcia]

It is running now, not sure what was fixed but working now. The only change I remember doing was to maximize the video memory.

Thanks,
Jorge

[socratis]

The only change I remember doing was to maximize the video memory.

That was one of the suggested remedies actually:

00:00:13.078105 VRamSize         <integer> = 0x0000000001000000 (16 777 216, 16 MB)

... Increase the VRAM to the max MB...

There's reason behind the madness...

Marking as [Solved].