#21806 new defect

Graphic artifacts with Windows 10 / 11 guests and Virtual Box 7

Reported by:	boxer01	Owned by:
Component:	guest additions/x11/graphics	Version:	VirtualBox-7.0.10
Keywords:	Windows 11 10	Cc:
Guest type:	Windows	Host type:	Windows

Description

I created this ticket as a followup for these tickets #21136, #21515(which were closed) and this one #21774(where just the black screen issue was handled). All logs and comments are in the previous tickets.

Long story short, I still see some graphic artifacts in the above-mentioned combination. The "new" Notepad of Windows 11 and .NET applications in both Windows 11 and 10.

Change History (29)

follow-up: 2 comment:1 by boxer01, 15 months ago

Still here in 7.0.11-158811.

in reply to: 1 ; follow-up: 3 comment:2 by tekstryder, 15 months ago

Replying to boxer01:

Still here in 7.0.11-158811.

I've been following the following tickets regarding the graphical issues introduced in the VB 7.0.x series:

We've such similar observances, I've not 'me-too'-ed. Thanks for continued testing.

Looks like I'll track this (#21806) and #21233 going forward.

Version 0, edited 15 months ago by tekstryder (next)

in reply to: 2 ; follow-up: 4 comment:3 by boxer01, 15 months ago

Replying to tekstryder:

We've such similar observances, I've not 'me-too'-ed. Thanks for continued testing.

Because I have no exclusive rights on these issues, it is OK to chime in. I am just "wondering" that you have similar issues with Linux as a host. But this could also be because of the OpenGL driver on your host system.

In the log file, at the start of the VM, all the supported and non-supported graphic possibilities of OpenGL are listed. Some of the things that are not supported in my or your case are causing these troubles. I think so.

in reply to: 3 ; follow-up: 5 comment:4 by tekstryder, 15 months ago

Replying to boxer01:

Replying to tekstryder:

We've such similar observances, I've not 'me-too'-ed. Thanks for continued testing.

I am just "wondering" that you have similar issues with Linux as a host. But this could also be because of the OpenGL driver on your host system.

Good point. Perhaps I should only follow #21233, as that's specific to Linux hosts.

I'll add my most recently noticed graphical glitches to that report.

FWIW, I've just been running with 3D Accel off, as I don't really need it, but wanted to help guinea pig the new graphics stack for the sake of the product's stability.

in reply to: 4 comment:5 by boxer01, 15 months ago

Replying to tekstryder:

Good point. Perhaps I should only follow #21233, as that's specific to Linux hosts.

You can follow both tickets; it isn't forbidden. ;-) Maybe it is a good idea to put the information about Windows on Windows combinations here and some Linux combinations in another ticket. But you could do it here as well.

As of the previous tickets, I see this error in nearly all combinations, so I don't think that this is somehow host or guest OS-dependent. There can be some general error in all realizations.

It would be nice if galitsyn (the closer of the original tickets) or some other developer would make some comments about this.

FWIW, I've just been running with 3D Accel off, as I don't really need it, but wanted to help guinea pig the new graphics stack for the sake of the product's stability.

And you are right—turning 3D acceleration off helps right now. I think there were issues with and without 3D acceleration previously. But now one can use it as a remedy. I just don't know if there are any problems because the user turned 3D acceleration in VM off.

Another point: one can't use VGA with 3D right now, and this isn't documented. As soon as I choose 3D acceleration and save the configuration of the VM, it silently changes the adapter to SVGA. One can see it only if one opens the configuration once again after saving the changes. So one can't test 3D with VGA. Maybe because there is no 3D acceleration in VGA and the VGA adapter is deprecated. But still, I can't find the documentation for this behavior.