LMDE 3 - Weird graphical glitch in Virtualbox guest

[craigwilliamsonnz]

Hi there,

I've just installed LMDE3 Cinnamon as a Virtualbox 6.0.4 guest (Manjaro KDE as host) and I'm seeing some weird graphical glitches. See the following image for more information -

I'm sure it has been documented online somewhere but I can't find anything related. If anyone could help that would be greatly appreciated. Other than that its a great distro. I prefer it to MX Linux!

The system information for the guest system is the following:

Code: Select all

inxi -Fxz
System:
  Host: craigw-lmde Kernel: 4.9.0-8-amd64 x86_64 bits: 64 compiler: gcc 
  v: 6.3.0 Desktop: Cinnamon 4.0.10 Distro: LMDE 3 Cindy 
  base: Debian 9.3 stretch 
Machine:
  Type: Virtualbox System: innotek product: VirtualBox v: 1.2 
  serial: <filter> 
  Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek 
  v: VirtualBox date: 12/01/2006 
Battery:
  ID-1: BAT0 charge: 48.5 Wh condition: 50.0/50.0 Wh (100%) model: innotek 1 
  status: Unknown 
CPU:
  Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MCP 
  arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 10847 
  Speed: 2712 MHz min/max: N/A Core speeds (MHz): 1: 2712 2: 2712 
Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.12.0.0 
  bus ID: 00:02.0 
  Display: x11 server: X.Org 1.19.2 driver: vmware 
  unloaded: fbdev,modesetting,vesa resolution: 1600x900~60Hz 
  OpenGL: renderer: Gallium 0.4 on SVGA3D; build v: 2.1 Mesa 13.0.6 
  direct render: Yes 
Audio:
  Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 
  v: kernel bus ID: 00:05.0 
  Sound Server: ALSA v: k4.9.0-8-amd64 
Network:
  Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: 7.3.21-k8-NAPI 
  port: d020 bus ID: 00:03.0 
  IF: enp0s3 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge 
  driver: piix4_smbus v: N/A port: d200 bus ID: 00:07.0 
Drives:
  Local Storage: total: 64.00 GiB used: 198.22 GiB (309.7%) 
  ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 64.00 GiB 
Partition:
  ID-1: / size: 58.71 GiB used: 10.91 GiB (18.6%) fs: ext4 dev: /dev/sda2 
  ID-2: swap-1 size: 4.10 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda1 
Sensors:
  Message: No sensors data was found. Is sensors configured? 
Info:
  Processes: 161 Uptime: N/A Memory: 3.86 GiB used: 519.8 MiB (13.1%) 
  Init: systemd runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 
  inxi: 3.0.32 

[ChrisMW]

The SVGA sometimes can do this, mainly on Windows 10 I see it often fail. But as with all things windows, it is not constant. I have one Windows 10 which seems fine with the SVGA adapter, one that freezes within 3 mins and wants VGA. My results have been better with the VBOXSVGA rather than the VMSGVA you're using. I also tend to set the virtualization interface to KVM for linux and Hyper-V for windows.