Upgrade to AlmaLinux 9.4 - Xorg results in high CPU usage.

Discussions about using Linux guests in VirtualBox.
Post Reply
agilis
Posts: 70
Joined: 21. Dec 2015, 18:46

Upgrade to AlmaLinux 9.4 - Xorg results in high CPU usage.

Post by agilis »

Hello,

My installation of AlmaLinux 9 was updated to 9.4 this morning. Ever since, X11, specifically the Xorg process, has been consuming a lot of CPU, especially when dragging windows, somewhere in the ballpark of 60% - 80%.

If I enable 3D Acceleration this issue goes away, however switching to 3D acceleration causes Window glitches such as screen redraws, artifacts, etc. consistently.

If I enable Gnome via Wayland, this issue goes away except I have the Wayland Copy and Paste issue that has not been resolved yet.
viewtopic.php?t=109447
agilis
Posts: 70
Joined: 21. Dec 2015, 18:46

Re: Upgrade to AlmaLinux 9.4 - Xorg results in high CPU usage.

Post by agilis »

Bumping this for views.

I cannot be the only one experiencing this issue. Something is no longer playing nice with VirtualBox and X11 that was part of this AlmaLinux 9.4 update.

Can anyone suggest a community I could post this issue in?
Mats62
Posts: 74
Joined: 23. Apr 2018, 08:06
Primary OS: MS Windows other
VBox Version: OSE other
Guest OSses: CentOS 7.6,7.2, 6.2,AlmaLinux 9.1

Re: Upgrade to AlmaLinux 9.4 - Xorg results in high CPU usage.

Post by Mats62 »

Hi agilis,
your post inspired me to try something out for the issue described in viewtopic.php?p=547125#p547125

When I change /etc/gdm/custom.conf to no longer disable Wayland, and select to start a Wayland Display Server at login, I can log in, also with the otherwise offending line present in /etc/gdm/custom.conf. (Wayland is then the only type of Display-server that lets me log in, the others still fail to start the screen, as described in the other post)

Our two issues are different but it looks like there may be some overlap.
Have you looked at X-Server logfiles and /var/log/messages for any hints? (in addition to looking at VBox logs)
(I looked at mine but could not determine what goes wrong and where)

In my case the 3D-Acceleration setting makes no difference for the current problem. (but that setting has often been a savior when it has come to X-related graphics problems in the past and VBox' interaction with Win10/Win11's "subtleties")
agilis
Posts: 70
Joined: 21. Dec 2015, 18:46

Re: Upgrade to AlmaLinux 9.4 - Xorg results in high CPU usage.

Post by agilis »

Hi Mat,

Excellent advice. I took a look at /var/log/messages and this log entry repeats non-stop when using X11 Display Server without 3D Acceleration:

Code: Select all

May  8 10:12:12 localhost /usr/libexec/gdm-x-session[3201]: (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
May  8 10:12:12 localhost /usr/libexec/gdm-x-session[3201]: (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
May  8 10:12:23 localhost /usr/libexec/gdm-x-session[3201]: (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
May  8 10:12:23 localhost /usr/libexec/gdm-x-session[3201]: (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
May  8 10:12:24 localhost /usr/libexec/gdm-x-session[3201]: (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
May  8 10:12:24 localhost /usr/libexec/gdm-x-session[3201]: (II) event6  - VirtualBox mouse integration: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.
May  8 10:12:47 localhost /usr/libexec/gdm-x-session[3201]: (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
May  8 10:12:47 localhost /usr/libexec/gdm-x-session[3201]: (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
May  8 10:12:49 localhost /usr/libexec/gdm-x-session[3201]: (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
May  8 10:12:49 localhost /usr/libexec/gdm-x-session[3201]: (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
May  8 10:12:52 localhost /usr/libexec/gdm-x-session[3201]: (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
Enabling 3D Acceleration with X11 Display Server stops these log entries

Switching to Wayland Display Server stops these entries as well.

Update 1: VBox.log and any of the logs offered by VirtualBox do not offer any information regarding this issue.

Update 2: ~/.local/share/xorg/Xorg.0.log yields the following:

Code: Select all

[   113.668] (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[   113.829] (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[   113.998] (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[   113.998] (II) event6  - VirtualBox mouse integration: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.
[   114.119] (EE) event6  - VirtualBox mouse integration: client bug: event processing lagging behind by 26ms, your system is too slow
[   116.404] (EE) event6  - VirtualBox mouse integration: client bug: event processing lagging behind by 68ms, your system is too slow
[   117.005] (EE) event6  - VirtualBox mouse integration: client bug: event processing lagging behind by 11ms, your system is too slow
[   119.932] (EE) event6  - VirtualBox mouse integration: client bug: event processing lagging behind by 20ms, your system is too slow
[   122.093] (EE) event6  - VirtualBox mouse integration: client bug: event processing lagging behind by 97ms, your system is too slow
[   122.093] (EE) event6  - VirtualBox mouse integration: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages.
[   140.051] (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[   140.411] (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[   141.784] (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[   141.894] (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[   142.452] (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[   142.452] (II) event6  - VirtualBox mouse integration: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.
[   218.789] (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[   219.123] (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[   219.464] (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[   219.722] (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[   220.021] (II) event6  - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[   220.022] (II) event6  - VirtualBox mouse integration: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.
Post Reply