VirtualBox 6.0.2 with Windows 10 1809 x64 Guest, dual monitor - graphics in guest "torn"

Discussions about using Windows guests in VirtualBox.
Post Reply
Portsmouth Dude
Posts: 4
Joined: 7. Jan 2019, 17:46

VirtualBox 6.0.2 with Windows 10 1809 x64 Guest, dual monitor - graphics in guest "torn"

Post by Portsmouth Dude »

Host: Ubuntu 16, x64 (Lubuntu), 16GB RAM, Dell Latitude E5470
Guest: Windows 10 1809 x64, 4GB RAM. Dual monitor, 2@ 1920x1080, VBoxSVGA, 2d & 3d acceleration enabled, 256 MB video memory, guest additions installed.

When rebooting the guest from the initial Guest Additions installation, graphics on the start menu are "torn" (see attached pic). This does not occur if the machine is in single monitor mode, only dual.

Vbox log attached, along with a picture of the phonomenon.

I'm new-ish here, and have read a number of threads about dual monitor mode, keyboard & mouse integration enabled/disabled, etc., but wondering if this is something caused by my hardware or is this an issue with VirtualBox?

For the record, I've used VirtualBox for about 3 years now with a Windows 7 guest, and love it! I'm trying to migrate to Windows 10 ... unfortuantely ...

Thanks in advance.
Attachments
Image-1.png.jpg
Image-1.png.jpg (45 KiB) Viewed 1401 times
rf2ovmw1064-master-2019-01-17-17-02-03.zip
(44.64 KiB) Downloaded 13 times
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: VirtualBox 6.0.2 with Windows 10 1809 x64 Guest, dual monitor - graphics in guest "torn"

Post by socratis »

Portsmouth Dude wrote: Dual monitor, 2@ 1920x1080, VBoxSVGA, 2d & 3d acceleration enabled, 256 MB video memory
00:00:00.718224 [/Devices/vga/0/Config/] (level 4)
00:00:00.718225   3DEnabled        <integer> = 0x0000000000000001 (1)
00:00:00.718225   CustomVideoModes <integer> = 0x0000000000000000 (0)
00:00:00.718226   FadeIn           <integer> = 0x0000000000000001 (1)
00:00:00.718226   FadeOut          <integer> = 0x0000000000000001 (1)
00:00:00.718227   HeightReduction  <integer> = 0x0000000000000000 (0)
00:00:00.718228   LogoFile         <string>  = "" (cb=1)
00:00:00.718228   LogoTime         <integer> = 0x0000000000000000 (0)
00:00:00.718229   MonitorCount     <integer> = 0x0000000000000002 (2)
00:00:00.718229   ShowBootMenu     <integer> = 0x0000000000000002 (2)
00:00:00.718230   VRamSize         <integer> = 0x0000000010000000 (268 435 456, 256 MB)
No, it's not the VBoxSVGA that you have selected, it's the VBoxVGA, without the "S". That's a GoodThing™ actually.
Portsmouth Dude wrote:graphics on the start menu are "torn" (see attached pic)
The picture itself doesn't help. Can you take a guest screenshot from VirtualBox (default is HostKey+E), crop it to the area of interest, and post that? Much, much clearer...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Portsmouth Dude
Posts: 4
Joined: 7. Jan 2019, 17:46

Re: VirtualBox 6.0.2 with Windows 10 1809 x64 Guest, dual monitor - graphics in guest "torn"

Post by Portsmouth Dude »

3 pics attached, along with an updated vbox log (I deleted the original machine, thinking it was bunk).

The tiles in the start menu on the right seem to (sort of) rectify themselves after some time, though that's not 100%. It's principally the icons in the start menu on the left that seem to have this odd behavior. Some reboots they're fine, some reboots they're "torn".

I've considered that maybe my .iso is corrupted, so I installed with another, newly downloaded one. Same behavior.

A couple of (naiive) observations - it seems as if the "tearing" sort of fixes itself here and there. Maybe there's an icon file that's not being updated quickly enough? And, in two monitor mode, windows update crashes repeatedly. I know, I know .. single topic.

Strange behavior. Just curious as to any thoughts you might have. I'm wondering if this is due to my hardware. I've got an Intel 530 Skylake (GT2) graphics processor.

Thanks for your help!
Attachments
VirtualBox_rf2ovmw1064-master_18_01_2019_10_45_27-2.jpg
VirtualBox_rf2ovmw1064-master_18_01_2019_10_45_27-2.jpg (46.14 KiB) Viewed 1372 times
VirtualBox_rf2ovmw1064-master_18_01_2019_10_42_22-2.jpg
VirtualBox_rf2ovmw1064-master_18_01_2019_10_42_22-2.jpg (56.5 KiB) Viewed 1372 times
VirtualBox_rf2ovmw1064-master_18_01_2019_10_30_27-2.jpg
VirtualBox_rf2ovmw1064-master_18_01_2019_10_30_27-2.jpg (80.14 KiB) Viewed 1372 times
Portsmouth Dude
Posts: 4
Joined: 7. Jan 2019, 17:46

Re: VirtualBox 6.0.2 with Windows 10 1809 x64 Guest, dual monitor - graphics in guest "torn"

Post by Portsmouth Dude »

And here is the new vbox log
Attachments
rf2ovmw1064-master-2019-01-18-10-48-01.zip
(57.64 KiB) Downloaded 14 times
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: VirtualBox 6.0.2 with Windows 10 1809 x64 Guest, dual monitor - graphics in guest "torn"

Post by socratis »

Portsmouth Dude wrote: I'm wondering if this is due to my hardware
I think so, yes:
00:00:00.698951 OpenGL Info: Render SPU: GL_VENDOR:   Intel Open Source Technology Center
00:00:00.698962 OpenGL Info: Render SPU: GL_RENDERER: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) 
00:00:00.698964 OpenGL Info: Render SPU: GL_VERSION:  3.0 Mesa 18.0.5
We've seen a lot of issues with Intel GPUs. I don't know if it the hardware or the drivers, but it seems to be a common denominator for such artifacts.

You don't happen to have another GPU that you could try with, do you?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply