VirtualBox

Opened 7 years ago

Last modified 6 years ago

#17014 new defect

Fedora Gnome slow UI performance

Reported by: mate Owned by:
Component: guest additions/x11/graphics Version: VirtualBox 5.1.26
Keywords: guest addition, 3D acceleration Cc:
Guest type: Linux Host type: Windows

Description

I've installed fresh and latest Fedora 26 as a VM and when I'm trying to use it, I'm receiving slow GUI response and overall graphic performance is bad. I've tried to use 3d acceleration as well, so the guest starts normally but when GUI part is loaded and login window appeared it's starts to work so slowly, that it's impossible to do anything.

The guest has 4vcpu's, 128mb of video memory and virtualbox additions installed. I'm using windows 10x64 Enterprise (build 10240) with latest intel video drivers (Intel® Graphics Driver for Windows* [15.33]) and latest virtualbox (Version 5.1.26 r117224 (Qt5.6.2)). I have plenty of RAM and i5-3470.

Attachments (2)

VBox.zip (28.8 KB ) - added by mate 7 years ago.
VBox log with 3D acceleration enabled
vbox.log.log (223.4 KB ) - added by JoergK 6 years ago.
Log from rhel 7.4 guest

Download all attachments as: .zip

Change History (13)

by mate, 7 years ago

Attachment: VBox.zip added

VBox log with 3D acceleration enabled

comment:2 by martinrist, 7 years ago

I've experienced what looks like a similar problem, using Ubuntu 16.04.2 LTS guest on a Windows 8.1 host. I found that the issue seems to occur on all versions of Guest Additions from 5.0.18 onwards, but isn't present in 5.0.16. There's more information about the setup (including log files) on the forum topic mentioned in comment 1.

As an example, switching the gnome-terminal app to full screen ad back again can take 20-30s. Whilst it's doing this, the CPU utilisation in the gnome-shell process spikes and an strace attached to the process shows a lot of additional ioctl calls which aren't present when doing the same thing with VBox 5.0.16. There are various logs (including the strace logs) attached to the linked forum post.

comment:3 by Michael Thayer, 7 years ago

I expect that these are two different issues with the same root cause (lack of developer time to improve 3D for Linux guests). Changes were made to the way 3D is set up in VirtualBox 5.0.18. In some situations this caused graphics regressions, though I have not heard of problems with Ubuntu 16.04.2 (it sounds like 3D may not be in use at all when you use the 5.0.18 or later Additions; did you try up until current?). And Fedora 26 uses Wayland, which we can not accelerate at the moment (and I cannot see that changing in the near future). Contributions welcome of course.

comment:4 by Michael Thayer, 7 years ago

@martinrist I had a look at the forum topic. Sounds like a problem of gnome-session loading before 3D is set up. Are you able to completely stop and restart gnome-session without rebooting the guest?

comment:5 by Herb Thompson, 6 years ago

I have a similar problem running Fedora 26 in VirtualBox 5.1.28 on Windows 10. When 3D Acceleration is enabled, switching gnome-terminal to/from full-screen takes many seconds. Response to other GUI actions is similarly too slow to be usable. Disabling 3D Acceleration for the guest greatly improves performance but GUI intensive apps such as system-monitor consume a non negligible percentage of CPU time when acceleration is disabled.

by JoergK, 6 years ago

Attachment: vbox.log.log added

Log from rhel 7.4 guest

comment:6 by JoergK, 6 years ago

Hello, I got this problem in Virtualbox 5.2.0-118431 on a Windows 10 Host with a RHEL 7.4 guest. 3D acceleration is enabled. You could find the vbox.log.log attached to this post.

The ticket was opened again a version of 5.1. Do I have to open a new ticket because I got this problem in version 5.2?

I've restarted the gnome-session with the following commands, but the problem still exists:

sudo systemctl isolate multi-user.target
suso systemctl isolate graphical.target

Regards, JoergK

Last edited 6 years ago by JoergK (previous) (diff)

in reply to:  6 comment:7 by Socratis, 6 years ago

Replying to JoergK:

The ticket was opened again a version of 5.1. Do I have to open a new ticket because I got this problem in version 5.2?

No, you don't. The report simply indicates when the ticket was first opened. If something changed, this would have been noted at the ticket. You do not open a new ticket for a new VirtualBox version, you simply note it in the existing ticket (if you need to). Can you imagine what would happen if somebody opened a new ticket for every VirtualBox release? Chaos...

comment:8 by szx, 6 years ago

I have the same performance issue with Fedora 27 in GNOME session, especially in Firefox. After a few minutes the system becomes so slow that it's barely usable. I didn't notice such problem when I used the GNOME Classic environment.

  • Host: Windows 10 x64
  • Guest: Fedora 27 4.13.12-300.fc27.x86_64
  • VirtualBox version: 5.1.30 r118389 (Qt5.6.2)
  • Guest additions: 5.1.30

comment:9 by Christopher Chavez, 6 years ago

For now, one workaround is to choose "GNOME on xorg" under the ⚙ gear icon on the login screen (cf. https://docs.fedoraproject.org/f27/system-administrators-guide/Wayland.html).

Also, in /etc/gdm/custom.conf there is a line that when uncommented will make the GDM login screen use xorg: WaylandEnable=false (cf. https://ask.fedoraproject.org/en/question/96134/how-can-i-set-xorg-as-a-default-on-fedora-25/?answer=96135#post-id-96135)

in reply to:  9 comment:10 by IcepickSU, 6 years ago

Just disabling Wayland did not do the trick for me. I also had to turn off 3D in the Virtual Box settings. I don't quite understand why.Replying to chrstphrchvz:

For now, one workaround is to choose "GNOME on xorg" under the ⚙ gear icon on the login screen (cf. https://docs.fedoraproject.org/f27/system-administrators-guide/Wayland.html).

Also, in /etc/gdm/custom.conf there is a line that when uncommented will make the GDM login screen use xorg: WaylandEnable=false (cf. https://ask.fedoraproject.org/en/question/96134/how-can-i-set-xorg-as-a-default-on-fedora-25/?answer=96135#post-id-96135)

comment:11 by naisanza, 6 years ago

Host: Windows 10 Home Edition 64bit Guest: Ubuntu 17.10.1

Using "GNOME on xorg" got it to be less unstable. But /etc/gdm/custom.conf doesn't exist on 17.10.1

Also, File Drag-And-Drop from Host to Guest is doesn't work; there's no logs in dmesg.

And File Drag-And-Drop from Guest to Host errors, shown below:

Current drop operation still in progress.

Result Code: 
E_FAIL (0x80004005)
Component: 
GuestDnDSourceWrap
Interface: 
IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee: 
IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d
Version 2, edited 6 years ago by naisanza (previous) (next) (diff)
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use