claud9999 wrote:I'm having the same issue and would appreciate instructions on how to set dmabuf_capable to false.
If you're running a version of Xorg new enough to support this new option, I believe you would edit your xorg.conf file or appropriate xorg.conf.d/* file, and add:
Code: Select all
Section "ServerFlags"
Option "Debug" "dmabuf_capable" "false"
EndSection
If you have an existing ServerFlags section, you might have to add the dmabuf_capable line to it, rather than making a new section; not sure.
I am also getting:
Code: Select all
[drm:drm_crtc_helper_set_config [drm_kms_helper]] *ERROR* failed to set mode on [CRTC:28:crtc-0]
errors on my CentOS 7.x guest, but in my case the GUI works fine other than warning me about that kern.err message every time I maximize the VirtualBox 5.2.22 console window on my Windows 7 host (which I do pretty often, as I move the console window between my two monitors).
Also, in my case, the dmabuf_capable option does not exist in the CentOS 7.x Xorg, so I can't do anything about these notifications until either that option (assuming it would fix this) gets added by Red Hat and CentOS, or VirtualBox addresses whatever introduced the problem in 5.2.20 (assuming it wasn't actually a Red Hat / CentOS kernel or Xorg update that did it). I've started a new thread about this:
Linux guest kernel DRM CRTC error when maximizing Windows host VirtualBox console in 5.2.22.