https://bugzilla.suse.com/show_bug.cgi?id=1178360 https://bugzilla.suse.com/show_bug.cgi?id=1178360#c36 --- Comment #36 from Stefan Hundhammer --- I don't know what's going on there. But I do know that the problem started with the latest kernel 5.9.1, and it's the same with VirtualBox 6.1.10 using the VBoxVGA graphics driver there. When I look at that pixel garbage (see screenshot), I can see remnants of the framebuffer console with kernel and systemd messages with green [success] messages. The pixel lines are of course not aligned to make a proper image (different resolution), but it looks very much like what used to be the framebuffer during the boot process. At the same time, the X11 screen content appears to be offset downwards and to the right (which probably explains why keyboard echo does not appear where it should). So, knowing nothing about how the kernel, the framebuffer or the graphics drivers work, it appears to me as if the start pointer of the graphics pixel buffer is offset in that scenario. From previous ventures into low-level graphics stuff back in the early 90s that reminds me of base parameters of how the graphics are set up are wrong; back then it was bit order vs. byte order, pixel line padding and similar things. Maybe that newer kernel departed from previous such settings that were always taken for granted (and thus coded into that VBoxVGA driver on the VirtualBox side). But that is pure speculation, of course. My point is when I have that problem, others will have it as well; this may very well be a ticking time bomb. I personally can live for a while (weeks or months) with simply not updating that kernel, and when I have to (which sooner or later will happen), try my luck with another virtualization solution like libvirt or VmWare. Paying SLE customers may see that differently, though, and insist on a solution (with filing L3 support calls). I don't know how far L3 support for VirtualBox in SLE goes, but customers may argue that it's a SUSE problem, not their VirtualBox host. -- You are receiving this mail because: You are on the CC list for the bug.