You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the issue
Unfortunately I don't have any logs to provide, but I'll try to explain the problem.
When I start a virtualized OSX guest (Sonoma or Sequoia), after logging in, the mouse cursor on the guest screen is giant.
When I move the mouse cursor out of the guest screen area, it's back to normal.
It seems to be related to the screen resolution (I'm using 2560 x 1440), because when I change the resolution or resize the guest window by dragging from the bottom right corner (first smaller and then back to larger), the mouse cursor returns to normal for a while, but when I move the mouse out of the guest screen and back to the guest screen, the mouse is giant again.
However, when I record a video of this phenomenon, the mouse cursor is normal while watching the video. So I had to take photos to show it.
Configuration
UTM Version: 4.5.4
macOS Version: Sonoma 14.7.1
Mac Chip: M2
The text was updated successfully, but these errors were encountered:
Describe the issue
Unfortunately I don't have any logs to provide, but I'll try to explain the problem.
When I start a virtualized OSX guest (Sonoma or Sequoia), after logging in, the mouse cursor on the guest screen is giant.
When I move the mouse cursor out of the guest screen area, it's back to normal.
It seems to be related to the screen resolution (I'm using 2560 x 1440), because when I change the resolution or resize the guest window by dragging from the bottom right corner (first smaller and then back to larger), the mouse cursor returns to normal for a while, but when I move the mouse out of the guest screen and back to the guest screen, the mouse is giant again.
However, when I record a video of this phenomenon, the mouse cursor is normal while watching the video. So I had to take photos to show it.
Configuration
The text was updated successfully, but these errors were encountered: