VirtualBox

Opened 4 months ago

Last modified 3 weeks ago

#21955 accepted defect

Heavy screen flickering VirtualBox 6.1.48 / 7.0.12 Ubuntu Wayland guest kernels 6.4 / 6.5

Reported by: Erwin Owned by: Dmitrii Grigorev
Component: GUI Version: VirtualBox-7.0.14
Keywords: screen flickering, ubuntu updates, display, guest additions Cc: Erwin
Guest type: Linux Host type: Windows

Description (last modified by Erwin)

Heavy screen flickering occurs with Ubuntu Wayland guest after installing guest Ubuntu updates.

Screenshot:

VirtualBox Forum:

Reproducible on AMD Ryzen 7/9 Windows/Linux host computers as all guests running Ubuntu (Wayland) flavors are affected after updated kernel versions 6.4/6.5:

  • Ubuntu 22.04 / 23.10 desktops running kernel versions 6.4 and 6.5
  • Fedora 39, kernel 6.6.9-200.fc39
  • Hosts Windows 10 and any Linux
  • VirtualBox versions 6.1.50, 7.0.14 and older
  • Corresponding Guest additions installed
  • Guest Display settings: 128MB, 3D acceleration unchecked (as 3D graphics acceleration is not supported by VirtualBox)
  • Latest Windows 10 host NVidia driver v546.33

Problems:

  • Screen flickering occurs especially in full screen of the guest and maximized guest window.
  • Additionally, the Ubuntu 23.10 / 24.04 installation window does not start or is white (popup asks to quit as there is no GUI response).
  • Very slow GUI guest response.

Attachments (7)

guest_dmesg_logs.zip (63.2 KB ) - added by Erwin 4 months ago.
VirtualBoxLogs21955.zip (67.6 KB ) - added by Erwin 4 months ago.
2024-01-19 22_35_06-Greenshot.jpg (99.9 KB ) - added by macsek 4 months ago.
stripes_logs.zip (252.8 KB ) - added by macsek 4 months ago.
VirtualBoxVM_2024-01-29_15-41-32.jpg (62.0 KB ) - added by Erwin 4 months ago.
VirtualBoxHeavyScreenFlickering.jpg (187.3 KB ) - added by Erwin 4 months ago.
VirtualBoxHeavyScreenFlickeringSmall.jpg (45.5 KB ) - added by Erwin 4 months ago.

Download all attachments as: .zip

Change History (33)

by Erwin, 4 months ago

Attachment: guest_dmesg_logs.zip added

by Erwin, 4 months ago

Attachment: VirtualBoxLogs21955.zip added

comment:1 by pm4492, 4 months ago

Getting this error in Xorg.0.log with kernel 6.6 not with kernel 6.1

[    53.021] (EE) vmwgfx_scanout_update: failed to send dirty (-12, Cannot allocate memory)
[    53.021] (EE) vmwgfx_scanout_update: failed to send dirty (-12, Cannot allocate memory)

comment:2 by pm4492, 4 months ago

Among the kernels that I can find, 6.3.9 is the last one that works and 6.4 is the first one that has this issue.

comment:3 by Erwin, 4 months ago

Description: modified (diff)

comment:4 by bradfordwetmore, 4 months ago

This may be related to:

https://forums.virtualbox.org/viewtopic.php?t=110879

There were reports of similar vmwgfx errors in that one as well.

Was seeing large rectangles for where the cursor was supposed to be, along with major flickering.

by macsek, 4 months ago

by macsek, 4 months ago

Attachment: stripes_logs.zip added

comment:5 by macsek, 4 months ago

Same issue here, different hardware (12th Gen Intel(R) Core(TM) i7-1255U 1.70 GHz, 32GB RAM), more recent VirtualBox version.

https://forums.virtualbox.org/viewtopic.php?p=545533

Freshly installed VirtualBox 7.0.14 r161095 (Qt5.15.2) and VirtualBox 7.0.14 Oracle VM VirtualBox Extension Pack running on Win11, the only VM created is an Ubuntu 22.04 LTS 64 bits. Ubuntu was installed from the official (just downloaded) iso automatically by VirtualBox. (I like this feature 8) ) Nothing is modified at all, no additional program is installed. The windows screen is working well, however the ubuntu VM window (and only that) shows stripes, like on an old monitor. I suspected the VirtualBox video driver (VMSVGA) and tried to change it to VBoxSVGA and VBoxVGA but setting either resulted me not able to log in so I reverted. I restarted more times, reinstalled Guest Additions two times, no change.

After retaining the original software state (no updates, no installs) the stripes does not show the next day, screen is normal. However when tried to start terminal (to check kernel version) I received an error message and terminal did not start, even on 2nd try. I have sent the problem report right now.

stripes_logs.zip contains the logfiles. Please let me know if you need more information.

comment:6 by discoverix558, 4 months ago

I can confirm the problem, I work with a Windows 10 host and Ubuntu 22.04 LTS guests in seamless mode. After updating VBox to version 7.0.14 – including corresponding guest additions – graphics are unstable. VBox „forgets“ the seamless mode (that was always the case in version 7), means when I do something else and then return to the guest, I often have to switch the seamless mode on again as the screen does not fit the display. With version 7.0.14 I experience now that the guest starts flickering once I switch to seamless – not at the first time, but latest at the 3rd. I have not found a way to stop it other than to reboot the guest. As I am updating ubuntu regularly and I noticed that the kernel is now on version 6.0.15-14. My CPU type is AMD 5700G without an additional graphics card, I am working with a resolution of 3820 x 2160 (x 2026 seamless). I am happy to provide more details or log data if that is of any help to resolve the problem. Does anyone know a „least annoying“ workaround while this issue is pending ?

comment:7 by bradfordwetmore, 4 months ago

@discoverix558:

Until this issue is resolved, I've been booting into an older kernel.

For booting to an older kernel, the best solution for me was to set (in /etc/default/grub):

GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true

With this settings the last selected value is kept for the next boot. If you have a new kernel you don't have to edit your config.

Don't forget to re-run sudo update-grub. Then boot into grub and select the a downrev'd kernel.

Not ideal.

I've heard the VB devs are aware of the issue, but that's all the insight I have.

comment:8 by Erwin, 4 months ago

Description: modified (diff)

comment:9 by Erwin, 4 months ago

Description: modified (diff)

comment:10 by Erwin, 4 months ago

@VirtualBox developers, can you reproduce this issue? It is still listed as "new defect".

Updates: Bug still exists in VirtualBox versions 6.1.50, 7.0.14 and older.

comment:12 by Erwin, 4 months ago

Description: modified (diff)

comment:13 by Erwin, 4 months ago

Description: modified (diff)

comment:14 by discoverix558, 4 months ago

@Erwin: Thanks for your suggestions to use a downlevel kernel. I tried different things and now found that the easiest workaround is to simply switch off Wayland as described here  https://linuxconfig.org/how-to-enable-disable-wayland-on-ubuntu-22-04-desktop which replaces Wayland by Xorg as display manager.

I had to reboot the machine in order to get my stuff working properly, just restarting gdm was not enough. Results are promising: flickering is gone, seamless mode works fine and I cannot see any other graphical limitation. I am just using it for 24 hours now, but let’s hope it‘s a possible clue.

P.S.: other than stated my kernel version is 6.5.0-14.

comment:15 by Erwin, 4 months ago

@discoverix558 Thanks for your feedback. Please noticed that several people on different platforms already reported that this major screen flickering VirtualBox bug exists in both Wayland and Xorg. Switching Xorg may temporary work for you.

Probably all VirtualBox users installing Linux guest with kernel >= 6.4 and VirtualBox <= 7.0.14 are affected since there is no official solution.

The only workaround at this moment is downgrading the Linux kernel back to 6.3 or older.

This bug needs to be confirmed and fixed by VirtualBox developers.

comment:16 by Erwin, 4 months ago

Q1) @VirtualBox moderators: Can you change the affected version + title to 7.0.14? Otherwise I'll create a new ticket for 7.0.14 at 6 Februrary as I cannot modify version/title of this ticket.

Q2) @VirtualBox developers: Can you confirm that this bug is reproducible?

As long as we do not receive a confirmation, we assume as community that this critical bug has no priority. Oracle, please keep us informed about the progress as the issue is already open for more than 3 weeks without a response.

Last edited 4 months ago by Erwin (previous) (diff)

comment:17 by Erwin, 4 months ago

Duplicate ticket https://www.virtualbox.org/ticket/21981 created for 6.1.50 / 7.0.14 since there is no moderator to change the title of this ticket.

comment:18 by Erwin, 3 months ago

5 weeks after opening this issue:

@VirtualBox developers: Can you confirm that this bug is reproducible? What is the roadmap/schedule to fix this critical bug?

comment:19 by Erwin, 3 months ago

Duplicate ticket https://www.virtualbox.org/ticket/21981 has been closed. No progress.

@MODERARTORS: Can you change VirtualBox version to 7.0.14 in this ticket?

comment:20 by Erwin, 3 months ago

+1

comment:21 by paulson, 3 months ago

Version: VirtualBox-7.0.12VirtualBox-7.0.14

in reply to:  10 comment:22 by Dmitrii Grigorev, 3 weeks ago

Replying to Erwin:

@VirtualBox developers, can you reproduce this issue? It is still listed as "new defect".

Updates: Bug still exists in VirtualBox versions 6.1.50, 7.0.14 and older.

Hello Erwin. Sorry for delay with answer, the flickering issue is reproduced on our side and fixing is in progress. As a temporary workaround please try to use X session instead of Wayland in GDM.

comment:23 by Dmitrii Grigorev, 3 weeks ago

Owner: set to Dmitrii Grigorev
Status: newaccepted

comment:24 by phillang, 3 weeks ago

As a cheap workaround, running the following command stabilizes things:

sudo rcvboxadd reload
Last edited 3 weeks ago by phillang (previous) (diff)

comment:25 by Erwin, 3 weeks ago

5 months later:

  • VirtualBox 7.0.12 released, reported graphics problem
  • VirtualBox 7.0.14 released, same graphics problem
  • VirtualBox 7.0.16 released, same graphics problem, additionally crashing the host with Ethernet in bridged mode -> Useless release
  • VirtualBox 7.0.18 released, same graphics problem.

What is the roadmap to fix this major bug?

in reply to:  24 comment:26 by Erwin, 3 weeks ago

Replying to phillang:

As a cheap workaround, running the following command stabilizes things:

sudo rcvboxadd reload

The problem returns as soon as the window is resized. Still waiting for a solution.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use