3D Acceleration strangeness

[yurtesen]

I am running virtualbox 5.0.26 on an amd carrizo host with ubuntu 16.04 LTS server installation as guest with xfce/slim. I have enabled 3D acceleration with 64MB ram.

1- I have realized that the glx_info output is exactly same independent of 3D acceleration checkbox is selected or not.
2- I get about 250FPS on glxgears when 3D acceleration is selected active and when I disable 3D acceleration, I get 280FPS (one would expect this to work other way around or make significant difference).

I found another post here where somebody had such performance strangeness but it wasnt clear if there was a fix or not.

Since I am not using unity (and the unity 3d test program is not there) and glx_info shows exactly same information, it is difficult to say if the checkbox is doing anything. I also tested the same machine in VMWare Workstation and it gets 450-550fps when 3d is enabled and when 3d is disabled it gets about 250fps

Any ideas about what to do about this problem? What to check?

[Perryg]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

[yurtesen]

Is this the file you are looking for?

[Perryg]

Code: Select all

00:00:08.740768 supR3HardenedErrorV: supR3HardenedScreenImage/NtCreateSection: rc=VERR_BAD_EXE_FORMAT fImage=1 fProtect=0x5 fAccess=0x2 \Device\HarddiskVolume4\Windows\System32\drivers\atikmdag.sys: 

I would try updating the host GPU drivers first since there seems to be an issue with driver signing, Etc..

[yurtesen]

Perry, nice try but VirtualBox is broken because these are the drivers which are installed by Windows Update on Windows 10 by default. I am pretty sure they must be signed properly (and also file properties does not show any certificate errors)
Plus, the GPU works perfectly fine on Windows with any app (apps using GPU) including VMWARE, furmark etc.
As a matter of fact, if atikmdag.sys was broken, windows would blue screen or do some weird stuff. Since everything is working...

So, clearly the problem is virtualbox since it is only VirtualBox which thinks the file has some problem. So thanks for pointing out the fault of virtualbox from the logs. Now I hope virtualbox guys would fix this issue.

Also apparently this has been an ongoing problem with VirtualBox with different versions of AMD drivers, making it much more probable that the AMD drivers are fine but VirtualBox is broken.
https://community.amd.com/thread/195664
If you read the post, you can see that the person who made the post also tried at least 2 versions of the driver. Obviously, it has nothing to do with the file being broken in my machine....

[Perryg]

I don't recall saying that the AMD was the problem. I said it would be a good idea to first make sure that you had updated the driver. It is clear that VirtualBox is having and issue because it is mentioned in the log file ( supR3HardenedScreenImage/NtCreateSection: rc=VERR_BAD_EXE_FORMAT ). Since VirtualBox uses hardening ( for security reasons ) and the host nor any other Virtualizer do not, it runs tests to see if the drivers are signed properly. When it finds it is not it complains about it and does not load. This protects against malicious code injecting itself to a system DLL and taking over your PC. If you are sure that the driver is the newest and is signed properly then your next step is to post a ticket to bugtracker.

[yurtesen]

PerryG, sorry I was really tired and upset and having a bad day because every time I make a bug report people seem to blame the other software. my apologies...

About the file. When I open it, I see that it was signed by "Microsoft Windows Hardware Compatibility Publisher" and the purpose was "Ensures software came from software publisher, Protects software from alteration after publication"
BUT the valid dates show that one of the certificates expire at 19-Mar-16 and there was some other info in countersignatures section, a certificate from "Microsoft Time-Stamp Service" which said the purpose is "Allows data to be signed with the current time".

I am not sure if this is any problem but at least windows does not seem to think so...

Anyway, I ran the sigverif tool and below is the output about this file

Code: Select all

Log file generated on 14-Sep-16 at 00:39
OS Platform:  Windows (x64), Version:  10.0, Build: 14393, CSDVersion:  
Scan Results:  Total Files: 512, Signed: 511, Unsigned: 0, Not Scanned: 1

File                      Modified       Version             Status              Catalog              Signed By
------------------      ------------   -----------        ------------        -----------          -------------------
atikmdag.sys             08-Oct-15      8.1.1.1500          Signed              c0188821.cat        Microsoft Windows Hardware Compatibility Publisher

and I ran the dxdiag tool and let it verify the files as well and here is the result below for the GPU:

Code: Select all

     Name: AMD Radeon R8 M365DX
Device ID: PCI\VEN_1002&DEV_6900&SUBSYS_80B5103C&REV_81\4&9E08BB8&0&0019
   Driver: C:\WINDOWS\system32\DRIVERS\atikmdag.sys, 8.01.0001.1500 (English), 10/8/2015 19:38:36, 21653520 bytes
   Driver: C:\WINDOWS\system32\DRIVERS\ati2erec.dll, 1.00.0000.0024 (English), 10/8/2015 19:38:32, 62480 bytes
   Driver: C:\WINDOWS\system32\DRIVERS\amdacpksd.sys, 2.15.0030.0019 (English), 10/8/2015 19:38:30, 315104 bytes
   Driver: C:\WINDOWS\system32\atiumd64.dll, 9.14.0010.1128 (English), 10/8/2015 19:39:18, 8950512 bytes
   Driver: C:\WINDOWS\system32\atiumd6a.dll, 8.14.0010.0513 (English), 10/8/2015 19:39:18, 9069104 bytes
   Driver: C:\WINDOWS\system32\atitmm64.dll, 6.14.0011.0025 (English), 10/8/2015 19:38:34, 209936 bytes
   Driver: C:\WINDOWS\system32\amdpcom64.dll, 8.14.0010.0023 (English), 10/8/2015 19:39:16, 99104 bytes
   Driver: C:\WINDOWS\system32\atimpc64.dll, 8.14.0010.0023 (English), 10/8/2015 19:39:16, 97584 bytes
   Driver: C:\WINDOWS\system32\atiadlxx.dll, 7.15.0020.1301 (English), 10/8/2015 19:38:32, 1265184 bytes
   Driver: C:\WINDOWS\system32\atiumd6a.cap, 9/5/2015 10:40:12, 3437632 bytes
   Driver: C:\WINDOWS\system32\atimuixx.dll, 6.14.0010.1002 (English), 10/8/2015 19:38:34, 47128 bytes
   Driver: C:\WINDOWS\system32\atiapfxx.exe, 6.14.0010.1001 (English), 10/8/2015 19:38:32, 384536 bytes
   Driver: C:\WINDOWS\system32\ativvsva.dat, 9/5/2015 10:40:18, 157144 bytes
   Driver: C:\WINDOWS\system32\ativvsvl.dat, 9/5/2015 10:40:18, 204952 bytes
   Driver: C:\WINDOWS\system32\ativvaxy_cik.dat, 9/5/2015 10:40:18, 234420 bytes
   Driver: C:\WINDOWS\system32\ativvaxy_cik_nd.dat, 9/5/2015 10:40:18, 232752 bytes
   Driver: C:\WINDOWS\system32\ativce02.dat, 9/5/2015 10:40:18, 100816 bytes
   Driver: C:\WINDOWS\system32\amdmmcl6.dll, 1.06.0000.0000 (English), 10/8/2015 19:38:30, 69648 bytes
   Driver: C:\WINDOWS\system32\atiesrxx.exe, 6.14.0011.1199 (English), 10/8/2015 19:38:32, 264224 bytes
   Driver: C:\WINDOWS\system32\atieclxx.exe, 6.14.0011.1199 (English), 10/8/2015 19:38:32, 692256 bytes
   Driver: C:\WINDOWS\system32\atidemgy.dll, 4.05.5696.36523 (English), 10/8/2015 19:38:32, 459800 bytes
   Driver: C:\WINDOWS\system32\atio6axx.dll, 6.14.0010.13399 (English), 10/8/2015 19:38:38, 30783520 bytes
   Driver: C:\WINDOWS\system32\aticalrt64.dll, 6.14.0010.1848 (English), 10/8/2015 19:38:32, 79904 bytes
   Driver: C:\WINDOWS\system32\aticalcl64.dll, 6.14.0010.1848 (English), 10/8/2015 19:38:32, 73240 bytes
   Driver: C:\WINDOWS\system32\aticaldd64.dll, 6.14.0010.1848 (English), 10/8/2015 19:38:34, 15734304 bytes
   Driver: C:\WINDOWS\system32\atiapfxx.blb, 9/5/2015 10:39:40, 662032 bytes
   Driver: C:\WINDOWS\system32\amdhdl64.dll, 10/8/2015 19:38:30, 153608 bytes
   Driver: C:\WINDOWS\system32\hsa-thunk64.dll, 10/8/2015 19:38:36, 120352 bytes
   Driver: C:\WINDOWS\system32\amdmantle64.dll, 9.01.0010.0077 (English), 10/8/2015 19:38:30, 6496264 bytes
   Driver: C:\WINDOWS\system32\mantle64.dll, 9.01.0010.0077 (English), 10/8/2015 19:38:36, 146448 bytes
   Driver: C:\WINDOWS\system32\mantleaxl64.dll, 9.01.0010.0077 (English), 10/8/2015 19:38:36, 110624 bytes
   Driver: C:\WINDOWS\system32\ativce03.dat, 9/5/2015 10:40:18, 177344 bytes
   Driver: C:\WINDOWS\system32\ativvaxy_vi.dat, 9/5/2015 10:40:18, 322868 bytes
   Driver: C:\WINDOWS\system32\ativvaxy_vi_nd.dat, 9/5/2015 10:40:18, 321200 bytes
   Driver: C:\WINDOWS\system32\ativvaxy_cz_nd.dat, 9/5/2015 10:40:18, 255808 bytes
   Driver: C:\WINDOWS\system32\amde31a.dat, 9/5/2015 10:39:04, 175648 bytes
   Driver: C:\WINDOWS\system32\detoured.dll, 2.01.0000.0207 (English), 10/8/2015 19:38:34, 23056 bytes
   Driver: C:\WINDOWS\system32\amdgfxinfo64.dll, 10/8/2015 19:38:30, 222240 bytes
   Driver: C:\WINDOWS\system32\atieah64.exe, 10/8/2015 19:38:32, 177688 bytes
   Driver: C:\WINDOWS\system32\ativvaxy_FJ.dat, 9/5/2015 10:40:18, 250884 bytes
   Driver: C:\WINDOWS\system32\ativvaxy_FJ_nd.dat, 9/5/2015 10:40:18, 249088 bytes
   Driver: C:\WINDOWS\system32\amdocl12cl64.dll, 0.08.0000.0000 (English), 10/8/2015 19:38:32, 27553312 bytes
   Driver: C:\WINDOWS\system32\amdicdxx.dat, 9/5/2015 10:39:04, 833800 bytes
   Driver: C:\WINDOWS\system32\atiicdxx.dat, 9/5/2015 10:39:54, 737410 bytes
   Driver: C:\WINDOWS\system32\amdmiracast.dll, 10/8/2015 19:39:16, 484176 bytes
   Driver: C:\WINDOWS\system32\atidxx64.dll, 8.17.0010.0625 (English), 10/8/2015 19:39:18, 12175392 bytes
   Driver: C:\WINDOWS\SysWOW64\atiumdag.dll, 9.14.0010.1128 (English), 10/8/2015 19:39:18, 7555672 bytes
   Driver: C:\WINDOWS\SysWOW64\atiumdva.dll, 8.14.0010.0513 (English), 10/8/2015 19:39:18, 8087568 bytes
   Driver: C:\WINDOWS\SysWOW64\amdpcom32.dll, 8.14.0010.0023 (English), 10/8/2015 19:39:16, 92160 bytes
   Driver: C:\WINDOWS\SysWOW64\atimpc32.dll, 8.14.0010.0023 (English), 10/8/2015 19:39:16, 92152 bytes
   Driver: C:\WINDOWS\SysWOW64\atiadlxy.dll, 7.15.0020.1301 (English), 10/8/2015 19:38:32, 944152 bytes
   Driver: C:\WINDOWS\SysWOW64\atiadlxx.dll, 7.15.0020.1301 (English), 10/8/2015 19:38:32, 944152 bytes
   Driver: C:\WINDOWS\SysWOW64\atiumdva.cap, 9/5/2015 10:40:16, 3471376 bytes
   Driver: C:\WINDOWS\SysWOW64\ativvsva.dat, 9/5/2015 10:40:18, 157144 bytes
   Driver: C:\WINDOWS\SysWOW64\ativvsvl.dat, 9/5/2015 10:40:18, 204952 bytes
   Driver: C:\WINDOWS\SysWOW64\amdmmcl.dll, 1.06.0000.0000 (English), 10/8/2015 19:38:30, 56864 bytes
   Driver: C:\WINDOWS\SysWOW64\atioglxx.dll, 6.14.0010.13399 (English), 10/8/2015 19:38:36, 25329680 bytes
   Driver: C:\WINDOWS\SysWOW64\atidxx32.dll, 8.17.0010.0625 (English), 10/8/2015 19:39:18, 10288368 bytes
   Driver: C:\WINDOWS\SysWOW64\aticalrt.dll, 6.14.0010.1848 (English), 10/8/2015 19:38:32, 69664 bytes
   Driver: C:\WINDOWS\SysWOW64\aticalcl.dll, 6.14.0010.1848 (English), 10/8/2015 19:38:32, 66592 bytes
   Driver: C:\WINDOWS\SysWOW64\aticaldd.dll, 6.14.0010.1848 (English), 10/8/2015 19:38:34, 14319648 bytes
   Driver: C:\WINDOWS\SysWOW64\atiapfxx.blb, 9/5/2015 10:39:40, 662032 bytes
   Driver: C:\WINDOWS\SysWOW64\amdhdl32.dll, 10/8/2015 19:38:30, 140832 bytes
   Driver: C:\WINDOWS\SysWOW64\hsa-thunk.dll, 10/8/2015 19:38:36, 119840 bytes
   Driver: C:\WINDOWS\SysWOW64\amdmantle32.dll, 9.01.0010.0077 (English), 10/8/2015 19:38:30, 5085728 bytes
   Driver: C:\WINDOWS\SysWOW64\mantle32.dll, 9.01.0010.0077 (English), 10/8/2015 19:38:36, 131104 bytes
   Driver: C:\WINDOWS\SysWOW64\mantleaxl32.dll, 9.01.0010.0077 (English), 10/8/2015 19:38:36, 103968 bytes
   Driver: C:\WINDOWS\SysWOW64\detoured.dll, 2.01.0000.0207 (English), 10/8/2015 19:38:34, 23048 bytes
   Driver: C:\WINDOWS\SysWOW64\amdgfxinfo32.dll, 10/8/2015 19:38:30, 208912 bytes
   Driver: C:\WINDOWS\SysWOW64\atieah32.exe, 10/8/2015 19:38:32, 161312 bytes
   Driver: C:\WINDOWS\SysWOW64\amdocl12cl.dll, 0.08.0000.0000 (English), 10/8/2015 19:38:32, 22336032 bytes
   Driver: C:\WINDOWS\system32\ATIODCLI.exe, 1.00.0000.0001 (English), 10/8/2015 19:38:34, 68632 bytes
   Driver: C:\WINDOWS\system32\ATIODE.exe, 1.00.0000.0001 (English), 10/8/2015 19:38:34, 350232 bytes
   Driver: C:\WINDOWS\system32\amdave64.dll, 8.04.0006.0000 (English), 10/8/2015 19:39:16, 127440 bytes
   Driver: C:\WINDOWS\SysWOW64\amdave32.dll, 8.04.0006.0000 (English), 10/8/2015 19:39:16, 120080 bytes
   Driver: C:\WINDOWS\system32\atisamu64.dll, 7.01.0000.0001 (English), 10/8/2015 19:38:34, 106520 bytes
   Driver: C:\WINDOWS\system32\amdhcp64.dll, 1.00.0000.0001 (English), 10/8/2015 19:39:16, 163608 bytes
   Driver: C:\WINDOWS\system32\kapp_ci.sbin, 9/5/2015 10:40:22, 47664 bytes
   Driver: C:\WINDOWS\system32\kapp_si.sbin, 9/5/2015 10:40:22, 43536 bytes
   Driver: C:\WINDOWS\system32\samu_krnl_ci.sbin, 9/5/2015 10:40:22, 140240 bytes
   Driver: C:\WINDOWS\system32\samu_krnl_isv_ci.sbin, 9/5/2015 10:40:22, 138832 bytes
   Driver: C:\WINDOWS\SysWOW64\atisamu32.dll, 7.01.0000.0001 (English), 10/8/2015 19:38:34, 98336 bytes
   Driver: C:\WINDOWS\SysWOW64\amdhcp32.dll, 1.00.0000.0001 (English), 10/8/2015 19:39:16, 148400 bytes
   Driver: C:\WINDOWS\system32\DRIVERS\atikmpag.sys, 8.14.0001.6463 (English), 10/8/2015 19:38:34, 683032 bytes
   Driver: C:\WINDOWS\system32\atiu9p64.dll, 8.14.0001.6463 (English), 10/8/2015 19:39:16, 141528 bytes
   Driver: C:\WINDOWS\system32\atiuxp64.dll, 8.14.0001.6463 (English), 10/8/2015 19:39:18, 172432 bytes
   Driver: C:\WINDOWS\system32\atig6txx.dll, 8.14.0001.6463 (English), 10/8/2015 19:38:32, 175632 bytes
   Driver: C:\WINDOWS\system32\atiglpxx.dll, 8.14.0001.6463 (English), 10/8/2015 19:38:32, 87072 bytes
   Driver: C:\WINDOWS\system32\aticfx64.dll, 8.17.0010.1404 (English), 10/8/2015 19:39:16, 1494528 bytes
   Driver: C:\WINDOWS\system32\amdxc64.dll, 8.18.0010.0043 (English), 10/8/2015 19:39:18, 9429368 bytes
   Driver: C:\WINDOWS\SysWOW64\aticfx32.dll, 8.17.0010.1404 (English), 10/8/2015 19:39:16, 1238224 bytes
   Driver: C:\WINDOWS\SysWOW64\amdxc32.dll, 8.18.0010.0043 (English), 10/8/2015 19:39:18, 7744400 bytes
   Driver: C:\WINDOWS\system32\OpenCL.dll, 2.00.0004.0000 (English), 10/8/2015 19:38:32, 82456 bytes
   Driver: C:\WINDOWS\system32\amdocl64.dll, 10.00.1800.0011 (English), 10/8/2015 19:38:34, 47804432 bytes
   Driver: C:\WINDOWS\system32\amdocl_as64.exe, 10/8/2015 19:38:32, 1204784 bytes
   Driver: C:\WINDOWS\system32\amdocl_ld64.exe, 10/8/2015 19:38:30, 1080864 bytes
   Driver: C:\WINDOWS\system32\clinfo.exe, 10/8/2015 19:38:34, 252440 bytes
   Driver: C:\WINDOWS\SysWOW64\OpenCL.dll, 2.00.0004.0000 (English), 10/8/2015 19:38:30, 76832 bytes
   Driver: C:\WINDOWS\SysWOW64\amdocl.dll, 10.00.1800.0011 (English), 10/8/2015 19:38:34, 39731728 bytes
   Driver: C:\WINDOWS\SysWOW64\amdocl_as32.exe, 10/8/2015 19:38:32, 1014304 bytes
   Driver: C:\WINDOWS\SysWOW64\amdocl_ld32.exe, 10/8/2015 19:38:30, 816176 bytes
   Driver: C:\Program Files\AMD\amdkmpfd\amdkmpfd.stz, 8.14.0001.6028 (English), 10/8/2015 19:38:30, 91400 bytes
   Driver: C:\Program Files\AMD\amdkmpfd\amdkmpfd.itz, 9/5/2015 10:39:04, 1988 bytes
   Driver: C:\Program Files\AMD\amdkmpfd\amdkmpfd.ctz, 9/5/2015 10:39:04, 9805 bytes
   Driver: C:\WINDOWS\system32\atig6pxx.dll, 8.14.0001.6463 (English), 10/8/2015 19:38:32, 92704 bytes
   Driver: C:\WINDOWS\SysWOW64\atiu9pag.dll, 8.14.0001.6463 (English), 10/8/2015 19:39:16, 123648 bytes
   Driver: C:\WINDOWS\SysWOW64\atiuxpag.dll, 8.14.0001.6463 (English), 10/8/2015 19:39:18, 153104 bytes
   Driver: C:\WINDOWS\SysWOW64\atigktxx.dll, 8.14.0001.6463 (English), 10/8/2015 19:38:32, 159264 bytes
   Driver: C:\WINDOWS\SysWOW64\atiglpxx.dll, 8.14.0001.6463 (English), 10/8/2015 19:38:32, 87072 bytes
   Driver: C:\WINDOWS\system32\coinst_15.20.dll, 1.00.0005.0009 (English), 10/8/2015 19:38:34, 884752 bytes

So now the question in my mind is how does VirtualBox decide that the file is bad when other tools seem to disagree? I mean isnt it enough that the file is signed and all?
I opened a ticket already and posted this info and the vbox log there -> https://www.virtualbox.org/ticket/15918

Thanks

[Perryg]

Well perhaps you should also update your post at the other site since it is clear that no one said it was for sure AMDs fault.

As for the issue it will be answered in bugtracker as the DEVs are the only ones that know about this code and are the ones that can fix it if it is in fact a VBox code issue.

[yurtesen]

PerryG I updated the amd forums also I just made too many bug reports and they really take time and most of the time the problem is not fixed or you need to re-submit all the information because they made a new version of something so data was invalidated. It is just nerve wrecking and often feels like a big waste of time. (no wonder why open source software have so many bugs and almost unusable, because they never fix them lol)

I think I will leave this to the very capable hands of the developers. After all, they probably do not even need my input. All they need is a system with AMD GPU since I have a feeling that all AMD drivers are all causing this error message.

[Ignis]

Hello everyone.

Quite a lot of time it took me to end up in this thread, but I am sure I finally found people with same issues, so I'll add my small input.

I have tried several guest linux distros (Fedora24, Arch, Linux Mint 18.1) and in all of them I have terrible performance, like <10 FPS at scrolling entries in menu for example, in non-lightweight desktop environments (GNOME, Cinnamon), while lighter (Xfce, MATE and LXDE) are doing reasonably well.
In my google search voyage I have seen tons of posts how everything became smooth and nice after ticking 3D acceleration check box in VritualBox. But mom says I'm special and in my case disabling 3D acceleration and running with software rendering actually boosts things up to a tolerable level, but still far from desired.

I have removed all virtualbox related packages coming with the installation and then installed guest additions 5.1.14 from .iso
Seamless mode, widow resize, clipboard, shared folders, all works and installation went without errorrs, so I assume guest additions installed correctly.
Linux guest tells me it is ready to go and everything should work nicely, alas someone is putting sticks in the wheel.

Code: Select all

$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string:   Humper
OpenGL renderer string: Chromium
OpenGL version string:  2.1 Chromium 1.9

Not software rendered:    yes
Not blacklisted:          yes
GLX fbconfig:             yes
GLX texture from pixmap:  yes
GL npot or rect textures: yes
GL vertex program:        yes
GL fragment program:      yes
GL vertex buffer object:  yes
GL framebuffer object:    yes
GL version is 1.4+:       yes

Unity 3D supported:       yes

Just like yurtesen, I have this in my vbox.log

Code: Select all

00:00:03.409505 supR3HardenedErrorV: supR3HardenedScreenImage/NtCreateSection: rc=VERR_BAD_EXE_FORMAT fImage=1 fProtect=0x7 fAccess=0x2 \Device\HarddiskVolume2\Windows\System32\drivers\atikmdag.sys: 
00:00:03.410783 supR3HardenedErrorV: supR3HardenedScreenImage/NtCreateSection: cached rc=VERR_BAD_EXE_FORMAT fImage=1 fProtect=0x2 fAccess=0x7 cHits=1 \Device\HarddiskVolume2\Windows\System32\drivers\atikmdag.sys

And after all my search, I assume there are some issues between VirtualBox and AMD drivers, may be in this whole "switchable graphics" part, as changing preferences of graphics card has no effect whatsoever.
(While I had an older version of AMD drivers 14.* I had an option to explicitly tell it to use discrete card for VBox, but with 17.2.1 now I can only set general behavior)

I am quite noob to linux (however this whole story made me learn lot of stuff) so tell me if I can add some usefull info here.
And I can use some suggestions if there is a fix, or I should just be a man and run linux as primary OS. Or be more of a man and pass through AMD card to the VM.

I am running
VirtualBox 5.1.14 r112924 (Qt5.6.2)
Guest Additions 5.1.14
Intel HD and AMD Radeon HD 8600M switchable graphics
AMD drivers 17.2.1
Host Windows 7 64bit
Guest Linux Mint 18.1 64bit with Cinnamon
VBox.log is attached