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

[Erwin]

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

Screenshot:

VirtualBox Forum:

• ​Heavy screen flickering VirtualBox 6.1.50 / 7.0.14 Ubuntu guest kernels 6.4 / 6.5
• ​Graphical corruption with VB 7.0.14 and Ubuntu 22.04.3
• ​Artifacts in Ubuntu 22.04 guest on Kubuntu 22.04 host, Nvidia RTX 3060 Ti

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.

[pm4492]

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)

[pm4492]

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.

[bradfordwetmore]

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.

[macsek]

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.

[discoverix558]

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 ?

[bradfordwetmore]

@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.

[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.

[Erwin]

New duplicate bugreports on VirtualBox forum related to this issue:

• ​Graphical corruption with VB 7.0.14 and Ubuntu 22.04.3
• ​Artifacts in Ubuntu 22.04 guest on Kubuntu 22.04 host, Nvidia RTX 3060 Ti

[discoverix558]

@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.

[Erwin]

@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.

[Erwin]

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.

[Erwin]

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.

[Erwin]

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?

[Erwin]

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?

[Erwin]

+1

[Dmitrii Grigorev]

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.

[phillang]

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

sudo rcvboxadd reload

[Erwin]

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?

[Erwin]

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.

[Erwin]

6 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.
• VirtualBox 7.0.20 released, same graphics problem.

What is the roadmap to fix this major bug?

[boxer01]

I added your ticket to the list of the graphic issues in my graphics ticket #21515, months ago. Just so you know. ;-)

[Erwin]

Easiest workaround until a real VirtualBox fix has been released by VirtualBox is to switch Ubuntu guest from Wayland to X11 as follows:

Edit /etc/gdm3/custom.conf as root
Uncomment line: WaylandEnable=false

[Francesco Pretto]

I'm possibly also affected.

• Host: Win 10
• Guest: Ubuntu 24.04
• VBox version: 7.0.20 (guest and extension updated)
• Graphical adapter: VMSVGA (with or without 3D acceleration enabled)

If I have VBox 3D acceleration enabled login (GDM) and Gnome Desktop start but Nautilus and other Gnome applications are corrupted. If I 3D acceleration disabled now I have to disable Wayland in /etc/gdm3/custom.conf otherwise I have black screen at login or other graphics corruption and the system frozen. In Ubuntu 22.04 I had still to disable 3D Acceleration but at least Wayland was fine. Since this was an upgrade from 22.04 -> 24.04 (while keeping VBox fixed at 7.0.20 or 7.0.18), it's unclear to me who is more responsabile for the Wayland fiasco. For sure it's quite a while that I have to keep 3D acceleration disabled because of graphics corruptions, which I guess it's more related to bugs in Virtualbox.

[boxer01]

Current test version 7.0.21-164265 has some changes in 3D acceleration and these changes could be tested.

What about the new 7.1 beta?

[Francesco Pretto]

I will definitely test any development build if a developer would recommend that with specific reference to this ticket/Wayland issues.

[bricowan]

There are related issues with RHEL 9, and likely others. The forum posting that referred me to this defect mentioned that setting the virtual screen resolution to a 16:9 aspect ratio (like literally 1600x900) helps stabilize the issue. And now my mouse pointer stops disappearing and I don't get screen corruption.

[Francesco Pretto]

If it helps for debugging: I'm affected by either corruptions or black screen/freezes, depending on enablement of 3D acceleration or Wayland, and the resolution I use in the Ubuntu guest is always 1920 x 1013, which is what I get in a 1920x1080 display with Windows host by setting the Windows taskbar to small and removing menu/status bars in the VirtualBox VM window.

[Francesco Pretto]

Just updated to 7.1.0 r164728, with guest additions, extensions, Ubuntu 24.04.1 packages full updated as well. Switched WaylandEnable in /etc/gdm3/custom.conf to true again (3D acceleration is disabled) and at the next boot I got black screen, so no improvements from 7.0.* for me. I'm seeing there are clipboard related fixes for Wayland in the changelog, but this situation should be investigated in depth because for some users Wayland is not working at all.

[Erwin]

Correct, Wayland with kernel >= 6.5 is defect in all VirtualBox versions <= v7.0.20.

A suggested temporary workaround:

1. Set guest video memory to maximum 128MB.
2. Never enable 3D acceleration (which is an unreliable experimental VirtualBox feature for any guest OS).
3. Enable line WaylandEnable=false in /etc/gdm3/custom.conf.

Login takes more time as Xorg crashes. The black screen in Ubuntu 24.04 is a different issue and has been reported by other users.

Unclear if the heavy screen flickering bug in VirtualBox will ever be fixed as you can see: Nobody at Oracle or VirtualBox was able to reply with technical details in this bug report.

For this reason, we stopped paying Oracle for premium support. Ubuntu 24.4.1 runs fine without issues in VMWare Workstation 17.5.2. It is way cheaper to purchase Broadcom licenses than waiting for VirtualBox bugfixes.

[Erwin]

9 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.
• VirtualBox 7.0.20 released, same graphics problem.
• VirtualBox 7.1.0 released, same graphics problem.

[Dmitrii Grigorev]

Hello folks.

Could you install and test a recent (>=165012) development snapshot from here https://www.virtualbox.org/wiki/Testbuilds. Update of the Guest Additions is not required, only base VirtualBox package update is enough. On both Windows and Linux hosts the flickering issue should be much less severe.

As already described above to observe the flickering issue the following is required:

• '3D acceleration' is OFF in VM config
• Wayland session
• A recent linux kernel >= 6.4

The full VirtualBox's workaround for VMWare bug in vmwgfx.ko kernel module introduced in the commit ​https://github.com/torvalds/linux/commit/a44df74c720eb45d16a92ab9fc8a780d961d5e2b is expected very soon.

Thank you for patience and sorry for delay with the fix.

With best regards, Dmitrii

[galitsyn]

Hi guys,

We just released VirtualBox 7.0.22 and 7.1.4. We have improvements for this issue there. You can give it a try on Downloads page.

[Francesco Pretto]

Black screen with Wayland affected user here: I just tested the new release and 7.1.4 is not a fix for me so comments by user @Erwin were correct: black screen issue is not a duplicate of this one. Sorry if I involuntarily hijacked the ticket but only here I could find a workaround (disable Wayland) which is working for me. I'm moving to https://www.virtualbox.org/ticket/21955 which seems to better address my issue (please point me if you know other relevant tickets/forum posts). @galitsyn: if also that ticket can receive some love because there are clearly some remaining issues with Wayland.

[Francesco Pretto]

I'm moving to https://www.virtualbox.org/ticket/21955 which seems to better address my issue

Sorry, I meant https://www.virtualbox.org/ticket/22085

[Erwin]

This screen flickering bug has been marked as resolved in the VirtualBox 7.1.4 changelog at https://www.virtualbox.org/wiki, but there is no difference in behavior:

• 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.
• VirtualBox 7.0.20 released, same graphics problem.
• VirtualBox 7.1.0 released, same graphics problem.
• VirtualBox 7.1.2 released, same graphics problem.
• VirtualBox 7.1.4 released marked as resolved, same graphics problem, no change.

Before marking as resolved in the changelog, it should be tested. A very simple 100% reproducible test case is included in this ticket. How is it possible that there is no change in release 7.1.4?

[elvp]

Hello I wanted to add few cents because the new 7.1.4 actually helped a bit in my case

My previous config for version 7.0.18.

Wayland OFF (Because of heavy flickering for Wayland ON)

3D accleration OFF (setting to ON hanged my system 100% of time)

It was usable, but annoying as about 50% - 70% of time there was system hanging during logging screen and I needed to restart again and again until it works

Now for 7.1.4:

If I only enable Wayland then flickering is less severe, but still disturbing enough when many windows are opened

BUT, when I set 3D acceleration ON (it works now in 7.1.4), then all flickering issues are gone for me. The only issue is that about 10% - 20% of time system hangs on login screen and I need to restart VM. Still it is nice improvement

[Francesco Pretto]

The only issue is that about 10% - 20% of time system hangs on login screen and I need to restart VM. Still it is nice improvement

@elvp: what you are describing is still an highly unreliable system. Also I think we should really focus in having the 2D path to be fixed first since it's supposed to be a safe fallback.

VirtualBox 7.1.4 released "improved graphics issues", but no change in screen flicking

@Ervin: after all I still suspect my black screen issue is the same, or it's somewhat realted. See this video at the 53th second: ​https://www.youtube.com/watch?v=IrjKf10IuwY

It's not "flickering" (intended as a dynamic, high frequency distortion) but there's a huge static corruption. Maybe it's something host hardware related? I have a laptop with Intel 10th generation integrated GPU and discrete nvidia RTX 2070 Super.

[Erwin]

VirtualBox cannot be used in a professional environment as long as the graphics screen flickering, black login screens, system hangs are not resolved. "Improvements" is not enough, it should work stable and reliable.

Never enable 3D acceleration as this is still an experimental feature for developers and is not ready to enable by default.

[Erwin]

@Francesco Pretto, The black screen on the Youtube video is reproducible. No idea how to resolve it. We did not see this with VMWare Workstation Pro 17.6 so far.

[Francesco Pretto]

I had some time to try it out a fresh install of Ubuntu 24.04, with VMSVGA and 128mb RAM as usual, guest additions installed. Result: no black screen so far but still corruptions/flickering.

See ​https://youtu.be/riacvKqVO3g for something I would call heavy flickering.

In this video ​https://youtu.be/Ag2A-uKjEww instead you see instead some light flickering, after heavy flickering stopped after random reboots/UI changes like enabling/disabling bars.

This mean that the issue is quite easily reproducible, with the right conditions (hardware?).

@Erwin: do you have a laptop or desktop?

[Dmitrii Grigorev]

Hello all.

The flickering issue was fixed for VirtualBox 7.1 (version >= 165995).

Please visit the Latest 7.1.x test builds chapter here https://www.virtualbox.org/wiki/Testbuilds and download Windows or Linux 64-bit package - depending on your host OS type. A Guest Additions update is not required.

Thank you for testing and I apologize for the long wait.

With best regards, Dmitrii

[Francesco Pretto]

First quick feedback: it appears to work for me, but with some errors that appeared just with this new build (165995). If the DisplayLink evdi driver/module is running (​https://github.com/DisplayLink/evdi), this will mess with DKMS in and will not run launch gdm at all. No corruption/flickering: just a stable black screen with a still cursor (black screen as described before was actually a corrupted screen, so it's not the same thing). DisplayLink is a technology to plug display screens in the USB bus. Not the kind of driver you usually install in VM(s), but still quite easy to riproduce even without the actual hardware. If the module/driver is removed, then gdm starts correctly. The excerpt below is from the journal when the DisplayLink hardware is running. Do you think it may be related to the VirtualBox recent changes?

nov 20 17:42:58 laptopbbkl2 kernel: ------------[ cut here ]------------
nov 20 17:42:58 laptopbbkl2 kernel: WARNING: CPU: 6 PID: 2389 at kernel/dma/mapping.c:206 __dma_map_sg_attrs+0x57/0xd0
nov 20 17:42:58 laptopbbkl2 kernel: Modules linked in: nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntra>
nov 20 17:42:58 laptopbbkl2 kernel: CPU: 6 PID: 2389 Comm: KMS thread Tainted: G        W  OE      6.8.0-49-generic #49-Ubuntu
nov 20 17:42:58 laptopbbkl2 kernel: Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
nov 20 17:42:58 laptopbbkl2 kernel: RIP: 0010:__dma_map_sg_attrs+0x57/0xd0
nov 20 17:42:58 laptopbbkl2 kernel: Code: 8b 40 58 e8 0b e0 05 01 85 c0 7e 11 5d 31 d2 31 c9 31 f6 31 ff 45 31 c0 c3 cc cc cc cc 8d 50 16 83 fa 11 76 3f 83 f8 87 74 e2 <0f> 0b b8 fb f>
nov 20 17:42:58 laptopbbkl2 kernel: RSP: 0018:ffffa5a4822cf780 EFLAGS: 00010213
nov 20 17:42:58 laptopbbkl2 kernel: RAX: 0000000000000000 RBX: ffff8b4b51149650 RCX: 0000000000000000
nov 20 17:42:58 laptopbbkl2 kernel: RDX: 0000000000000016 RSI: 0000000000000000 RDI: 0000000000000000
nov 20 17:42:58 laptopbbkl2 kernel: RBP: ffffa5a4822cf780 R08: 0000000000000000 R09: 0000000000000000
nov 20 17:42:58 laptopbbkl2 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff8b4b51149650
nov 20 17:42:58 laptopbbkl2 kernel: R13: ffff8b4b44fc0000 R14: ffff8b4b51149600 R15: ffff8b4b4676e840
nov 20 17:42:58 laptopbbkl2 kernel: FS:  0000797e2a0006c0(0000) GS:ffff8b4c57d00000(0000) knlGS:0000000000000000
nov 20 17:42:58 laptopbbkl2 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
nov 20 17:42:58 laptopbbkl2 kernel: CR2: 0000797e0c07e758 CR3: 0000000112d4e005 CR4: 00000000000706f0
nov 20 17:42:58 laptopbbkl2 kernel: Call Trace:
nov 20 17:42:58 laptopbbkl2 kernel:  <TASK>
nov 20 17:42:58 laptopbbkl2 kernel:  ? show_regs+0x6d/0x80
nov 20 17:42:58 laptopbbkl2 kernel:  ? __warn+0x89/0x160
nov 20 17:42:58 laptopbbkl2 kernel:  ? __dma_map_sg_attrs+0x57/0xd0
nov 20 17:42:58 laptopbbkl2 kernel:  ? report_bug+0x17e/0x1b0
nov 20 17:42:58 laptopbbkl2 kernel:  ? handle_bug+0x51/0xa0
nov 20 17:42:58 laptopbbkl2 kernel:  ? exc_invalid_op+0x18/0x80
nov 20 17:42:58 laptopbbkl2 kernel:  ? asm_exc_invalid_op+0x1b/0x20
nov 20 17:42:58 laptopbbkl2 kernel:  ? __dma_map_sg_attrs+0x57/0xd0
nov 20 17:42:58 laptopbbkl2 kernel:  dma_map_sgtable+0x1d/0x40
nov 20 17:42:58 laptopbbkl2 kernel:  vmw_ttm_map_dma+0xf6/0x150 [vmwgfx]
nov 20 17:42:58 laptopbbkl2 kernel:  vmw_move+0x1da/0x2f0 [vmwgfx]
nov 20 17:42:58 laptopbbkl2 kernel:  ttm_bo_handle_move_mem+0xe8/0x1f0 [ttm]
nov 20 17:42:58 laptopbbkl2 kernel:  ttm_bo_validate+0xf2/0x160 [ttm]
nov 20 17:42:58 laptopbbkl2 kernel:  vmw_resource_pin+0xea/0x240 [vmwgfx]
nov 20 17:42:58 laptopbbkl2 kernel:  vmw_stdu_primary_plane_prepare_fb+0x199/0x430 [vmwgfx]
nov 20 17:42:58 laptopbbkl2 kernel:  ? crtc_or_fake_commit.part.0+0x6f/0x110
nov 20 17:42:58 laptopbbkl2 kernel:  drm_atomic_helper_prepare_planes.part.0+0x32/0x1e0
nov 20 17:42:58 laptopbbkl2 kernel:  drm_atomic_helper_prepare_planes+0x5d/0x70
nov 20 17:42:58 laptopbbkl2 kernel:  drm_atomic_helper_commit+0x84/0x160
nov 20 17:42:58 laptopbbkl2 kernel:  drm_atomic_commit+0x99/0xd0
nov 20 17:42:58 laptopbbkl2 kernel:  ? __pfx___drm_printfn_info+0x10/0x10
nov 20 17:42:58 laptopbbkl2 kernel:  drm_mode_atomic_ioctl+0x560/0x850
nov 20 17:42:58 laptopbbkl2 kernel:  ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
nov 20 17:42:58 laptopbbkl2 kernel:  drm_ioctl_kernel+0xbc/0x120
nov 20 17:42:58 laptopbbkl2 kernel:  drm_ioctl+0x2d4/0x550
nov 20 17:42:58 laptopbbkl2 kernel:  ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
nov 20 17:42:58 laptopbbkl2 kernel:  vmw_generic_ioctl+0xc6/0x190 [vmwgfx]
nov 20 17:42:58 laptopbbkl2 kernel:  ? __pfx_drm_ioctl+0x10/0x10
nov 20 17:42:58 laptopbbkl2 kernel:  vmw_unlocked_ioctl+0x15/0x30 [vmwgfx]
nov 20 17:42:58 laptopbbkl2 kernel:  __x64_sys_ioctl+0xa3/0xf0
nov 20 17:42:58 laptopbbkl2 kernel:  x64_sys_call+0x143b/0x25c0
nov 20 17:42:58 laptopbbkl2 kernel:  do_syscall_64+0x7f/0x180
nov 20 17:42:58 laptopbbkl2 kernel:  ? __handle_mm_fault+0x653/0x790
nov 20 17:42:58 laptopbbkl2 kernel:  ? __count_memcg_events+0x6b/0x120
nov 20 17:42:58 laptopbbkl2 kernel:  ? count_memcg_events.constprop.0+0x2a/0x50
nov 20 17:42:58 laptopbbkl2 kernel:  ? handle_mm_fault+0xad/0x380
nov 20 17:42:58 laptopbbkl2 kernel:  ? do_user_addr_fault+0x32c/0x670
nov 20 17:42:58 laptopbbkl2 kernel:  ? irqentry_exit_to_user_mode+0x7b/0x260
nov 20 17:42:58 laptopbbkl2 kernel:  ? irqentry_exit+0x43/0x50
nov 20 17:42:58 laptopbbkl2 kernel:  ? exc_page_fault+0x94/0x1b0
nov 20 17:42:58 laptopbbkl2 kernel:  entry_SYSCALL_64_after_hwframe+0x78/0x80
nov 20 17:42:58 laptopbbkl2 kernel: RIP: 0033:0x797e38324ded
nov 20 17:42:58 laptopbbkl2 kernel: Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f>
nov 20 17:42:58 laptopbbkl2 kernel: RSP: 002b:0000797e29ffea20 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
nov 20 17:42:58 laptopbbkl2 kernel: RAX: ffffffffffffffda RBX: 0000797e0c07b660 RCX: 0000797e38324ded
nov 20 17:42:58 laptopbbkl2 kernel: RDX: 0000797e29ffeac0 RSI: 00000000c03864bc RDI: 000000000000000c
nov 20 17:42:58 laptopbbkl2 kernel: RBP: 0000797e29ffea70 R08: 0000797e0c0008e0 R09: 0000000000000000
nov 20 17:42:58 laptopbbkl2 kernel: R10: 0000000000000018 R11: 0000000000000246 R12: 0000797e29ffeac0
nov 20 17:42:58 laptopbbkl2 kernel: R13: 00000000c03864bc R14: 000000000000000c R15: 0000797e0c07bf50
nov 20 17:42:58 laptopbbkl2 kernel:  </TASK>
nov 20 17:42:58 laptopbbkl2 kernel: ---[ end trace 0000000000000000 ]---
nov 20 17:42:58 laptopbbkl2 kernel: vmwgfx 0000:00:02.0: [drm] VSG table map failed!
nov 20 17:42:58 laptopbbkl2 rtkit-daemon[2307]: Supervising 7 threads of 4 processes of 1 users.
nov 20 17:42:58 laptopbbkl2 rtkit-daemon[2307]: Supervising 7 threads of 4 processes of 1 users.
nov 20 17:42:58 laptopbbkl2 rtkit-daemon[2307]: Successfully made thread 2389 of process 2360 owned by '125' RT at priority 20.
nov 20 17:42:58 laptopbbkl2 rtkit-daemon[2307]: Supervising 8 threads of 5 processes of 1 users.
nov 20 17:42:58 laptopbbkl2 kernel: evdi: [I] (card1) Closed by Task 3027 ((sd-close)) of process 3027 ((sd-close))
nov 20 17:42:58 laptopbbkl2 kernel: evdi: [I] (card3) Closed by Task 3028 ((sd-close)) of process 3028 ((sd-close))
nov 20 17:42:58 laptopbbkl2 gnome-shell[2360]: Page flip failed: drmModeAtomicCommit: Input/output error
nov 20 17:42:58 laptopbbkl2 gnome-shell[2360]: Failed to post KMS update: drmModeAtomicCommit: Input/output error
nov 20 17:42:58 laptopbbkl2 kernel: evdi: [I] (card2) Closed by Task 3029 ((sd-close)) of process 3029 ((sd-close))
nov 20 17:42:58 laptopbbkl2 gsd-media-keys[2756]: Failed to grab accelerator for keybinding settings:hibernate
nov 20 17:42:58 laptopbbkl2 gsd-media-keys[2756]: Failed to grab accelerator for keybinding settings:playback-repeat
nov 20 17:42:58 laptopbbkl2 org.gnome.Shell.desktop[2952]: MESA: error: ZINK: failed to choose pdev
nov 20 17:42:58 laptopbbkl2 org.gnome.Shell.desktop[2952]: libEGL warning: egl: failed to create dri2 screen
nov 20 17:42:58 laptopbbkl2 /usr/libexec/gdm-wayland-session[2297]: dbus-daemon[2297]: [session uid=125 pid=2297] Activating service name='org.gnome.ScreenSaver' requested by ':1.23' >
nov 20 17:42:58 laptopbbkl2 /usr/libexec/gdm-wayland-session[2297]: dbus-daemon[2297]: [session uid=125 pid=2297] Successfully activated service 'org.gnome.ScreenSaver'
nov 20 17:42:58 laptopbbkl2 gnome-shell[2360]: Page flip failed: drmModeAtomicCommit: Input/output error
nov 20 17:42:58 laptopbbkl2 kernel: vmwgfx 0000:00:02.0: [drm] VSG table map failed!
nov 20 17:42:58 laptopbbkl2 org.gnome.Shell.desktop[2952]: MESA: error: ZINK: failed to choose pdev
nov 20 17:42:58 laptopbbkl2 org.gnome.Shell.desktop[2952]: glx: failed to create drisw screen
nov 20 17:42:58 laptopbbkl2 gnome-shell[2360]: Page flip failed: drmModeAtomicCommit: Input/output error
nov 20 17:42:58 laptopbbkl2 kernel: vmwgfx 0000:00:02.0: [drm] VSG table map failed!
nov 20 17:43:00 laptopbbkl2 gnome-shell[2360]: Page flip failed: drmModeAtomicCommit: Input/output error
nov 20 17:43:00 laptopbbkl2 kernel: vmwgfx 0000:00:02.0: [drm] VSG table map failed!

[Francesco Pretto]

I'm adding more details to reproduce the issue I'm having with the DisplayLink driver installed paired with the new VirtualBox build. To reproduce:

wget https://www.synaptics.com/sites/default/files/Ubuntu/pool/stable/main/all/synaptics-repository-keyring.deb\
    && sudo dpkg -i ./synaptics-repository-keyring.deb\
    && sudo apt update\
    && sudo apt install -y displaylink-driver

And reboot. To restore the system to working conditions (from a CTRL+ALT+F2 terminal):

sudo apt purge -y evdi && sudo autoremove --purge

And reboot. @Dmitrii, can you please check if there are obvious issues still left?