scottgus1 wrote:Does your usage of Virtualbox require you to turn mouse integration on and off constantly?
No.
I have used Virtualbox for years too, never had a problem with M.I. because I always just leave it turned on.
When I have seen the "The Virtual Machine reports that the guest OS supports mouse pointer integration" notice, there's a "Don't show this message again" clickbox, and I click it, and it's gone for good.
That is precisely what I have done for amost 10 years. If you review my top post you'll see that as option (A).
Does your message not have that clickbox?
Yes, it does. See "Note" below the options (A) & (B).
In my current VBox session (which started yesterday), I have only moments ago discovered that the symptoms have dramatically changed. I came to this forum to document it and discovered your reply.
In my current VBox session, when I'm in the Host (Win 10) and I Alt+Tab to the VMM (which contains the Guest... a Guest that also uses Alt+Tab as switcher) and stop (release the keys) and then press Alt+Tab once again with focus on the VMM, instead of cycling through the Guest's windows as it did yesterday (and the day before, etc.), a succeeding Alt+Tab instead proceeds in the Host as though the Guest is not there! Now follow me please... When I entered the current VBox session I did something different. If you've been following my recent posts you will see that I'm conducting some experiments to resolve issues that I've been ignoring til now.
I need to recreate what I did in this current session that was different from option (A). I reitterate that what I usually do is what you do: option (A). I think that by doing something different when the VMM initializes, I may have uncovered a longstanding bug. Now I need to reproduce it.
Oh, one last thing:
When I Alt+Tab to the VMM, stop, then click on a Guest window within the VMM, further Alt+Tabs cycle through the Guest windows as normal, but:
When I Alt+Tab to the VMM, stop, then Alt+Tab again (without clicking on a Guest window), instead of cycling through the Guest windows, cycling continues with the Host windows. That is entirely new behavior I've not experienced before.
The key is: What did I do this time that's different from option (A)?
And one more last thing: If you already have the VM configured for mouse pointer integration (as shown in the icon row at the bottom of the window), then why would the VMM show you a notification that the guest OS supports mouse pointer integration, eh? I bet there's a state failure within VBox code that allows 2 separate records of mouse pointer integration to get out of sync.
For now, I need to close this session (which is running in the Guest), then launch a new session and see if I can reproduce the current symptoms.
I'm actually markfilipak (which somehow became 'markfilipak2', then 'abcdefgh'). I've been here since 15 Jul 2012 but lost my name during the great shift to SSO (single sign-on) during 2017, and have not been able to recover it.