VirtualBox display problem: host 20.04

[zbigiman]

Hi,
I've just installed Virtualbox 6.1 - Version 6.1.10 r138449 (Qt5.12.8) - on Ubuntu 20.04 LTS and it works very slow. The Virtualbox interface is laggy, f.g. when I uncheck some checkbox in the setting it doesn't change, etc. It works very slow and laggy before running a virtual machine. There is some problem with screen refreshing, see screenshots, links below:

https://u.pcloud.link/publink/show?c...6ojqh7U55S51gk
https://u.pcloud.link/publink/show?c...5z40WcAJVIw79V

I was using Virtualbox on older ubuntu based distros and the interface was always smooth. Any ideas what's going on?

[ajgreeny]

Post moved to its own new thread.

[ajgreeny]

What is your host hardware?
This looks rather like a problem stemming from that rather than the guest.

Do you use the guest-additions of the same version as your Vbox, and have you installed them in the XP guest.
I still have, but do not use a VM of WinXP, mine having 2G ram compared to your 512MB, though I don't think that is your problem as it is the Vbox window display as well as the guest causing problems.

Perhaps it's worth trying using Vbox version 6.0 in place of 6.1 as some users have had much greater success with that earlier and still fully supported version.

[zbigiman]

My host hardware is:
Processor: Intel® Core™ i5-7200U CPU @ 2.50GHz × 4
Graphics: Mesa Intel® HD Graphics 620 (KBL GT2)
Ram: 7,5 GiB

It should be enough, I was using Virtualbox on worse configurations.

Finally I've installed Gnome Boxes and everything works perfectly, so I don't know what had happened with Virtualbox on Ubuntu 20.04.

Update:
My kernel is:
5.4.0-39-generic

What more information do You need?

[ajgreeny]

I will admit to not knowing of gnome-boxes, and I don't know if it's needed on a gnome host (I use Xubuntu), but if you are now happy and the problem is solved please mark SOLVED using Thread Tools menu at the top of this thread

[kneutron]

--Could be your video driver. Post results of ' lspci '

[monkeybrain20122]

What if you change graphic controller in Settings > Display to VBoxSVGA?

[zbigiman]

Here is lspci output

lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
03:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)

[ajgreeny]

OK. Now let's see the output of lspci -ks 00.02.0

That will show us the driver in use. It may not help, but all info is usually of use in some way..

[zbigiman]

I've recorded video, to show how the bug with VirtualBox display looks like. It's fresh instalation of VirtualBox:
https://u.pcloud.link/publink/show?c...AosjSCOYonLeck
It happens only in VirtualBox. All other applications works fine.