Page 1 of 1
VMSVGA and Google-Chrome
Posted: 25. Apr 2019, 14:31
by piggyz
I have to admit that 6.0.6 fixed many problems with VBOXSVGA driver related with Linux Guest.
Then there is an evident and big problem running Linux binary version of Google-Chrome (NOT Chromium) under pretty much every Linux I do try.
Beware: this do NOT happen when you start the program, you have to run it for more, in my experience it can even need two or three days to crash the virtual machine with an exception error. It happen ALWAYS in my experience. It doesn't happen with the same driver in native VMware, obviously.
Here a log of what happen when the virtual machine crash related to Google-Chrome.
Hope It is usefull.
PS: the log file was 157 KB, so becouse this forum doesn't accept attachment bigger then 128 K I've been forced to cut it. I cut the CFG part. If you need it complete, just allow bigger attachment of explain me how to provide it.
Gentoo2015_64bit-2019-04-18-23-27-06_cut.txt
Re: VMSVGA and Google-Chrome
Posted: 25. Apr 2019, 14:42
by andyp73
piggyz wrote:the log file was 157 KB, so becouse this forum doesn't accept attachment bigger then 128 K I've been forced to cut it. I cut the CFG part.
Partial log files are almost always problematical. You should compress it using your favourite tool: zip, gzip, rar, etc. and then attach it.
-Andy.
Re: VMSVGA and Google-Chrome
Posted: 25. Apr 2019, 15:22
by mpack
The OP has been on this site for 6 years and has provided compressed logs before, so I'm not sure what the difficulty was this time. The restriction on attachment size is a deliberate policy to conserve server space. That policy is not going to change any time soon.
Re: VMSVGA and Google-Chrome
Posted: 25. Apr 2019, 16:31
by piggyz
Just forgot I can attach zipped files. Here it is, the whole log compressed.
Re: VMSVGA and Google-Chrome
Posted: 25. Apr 2019, 16:40
by mpack
This appears in the log, and should certainly be fixed.
00:00:28.802184 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=7 \Device\HarddiskVolume4\Program Files (x86)\Samsung\Easy Printer Manager\SmartScreenPrint\CDAKEYMonitor64.dll
00:00:28.802321 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files (x86)\Samsung\Easy Printer Manager\SmartScreenPrint\CDAKEYMonitor64.dll' (C:\Program Files (x86)\Samsung\Easy Printer Manager\SmartScreenPrint\CDAKEYMonitor64.dll): rcNt=0xc0000190
00:00:28.892920 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=8 \Device\HarddiskVolume4\Program Files (x86)\Samsung\Easy Printer Manager\SmartScreenPrint\CDAKEYMonitor64.dll
00:00:28.893005 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files (x86)\Samsung\Easy Printer Manager\SmartScreenPrint\CDAKEYMonitor64.dll' (C:\Program Files (x86)\Samsung\Easy Printer Manager\SmartScreenPrint\CDAKEYMonitor64.dll): rcNt=0xc0000190
The crash itself may be related to suspend/resume. A workaround would be to shut guests down fully.
09:58:40.769997 Changing the VM state from 'RESUMING' to 'RUNNING'
09:58:40.770194 Console: Machine state changed to 'Running'
09:58:43.512707 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
09:58:50.778366 TMR3UtcNow: nsNow=1 555 620 775 768 763 200 nsPrev=1 555 586 866 405 187 239 -> cNsDelta=33 909 363 575 961 (offLag=0 offVirtualSync=0 offVirtualSyncGivenUp=0, NowAgain=1 555 620 775 768 763 200)
09:58:50.779188 VMMDev: Guest Log: 20:52:55.768554 timesync vgsvcTimeSyncWorker: Radical host time change: 33 909 363 000 000ns (HostNow=1 555 620 775 768 000 000 ns HostLast=1 555 586 866 405 000 000 ns)
09:58:50.780601 VMMDev: GuestHeartBeat: Guest is alive (gone 11 275 001 402 ns)
09:58:50.800066 AIOMgr: Async flushes not supported
09:59:00.780621 VMMDev: Guest Log: 20:53:05.769797 timesync vgsvcTimeSyncWorker: Radical guest time change: 33 906 641 159 000ns (GuestNow=1 555 620 785 769 629 000 ns GuestLast=1 555 586 879 128 470 000 ns fSetTimeLastLoop=true )
10:33:01.381181
10:33:01.381183 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000001270!!!
10:33:01.381196
Re: VMSVGA and Google-Chrome
Posted: 25. Apr 2019, 16:50
by mpack
Looking closer at the log, the exception seems to occur in d3d9.dll, which is a Direct3D DLL. Do you really need 3D acceleration in this VM?
00:00:20.017682 VMMDev: Guest Additions information report: Version 6.0.5 r128811 '6.0.5'
In any case it's not good that this VM is still running an obsolete test build of the GAs when a later matching release build is available.
Re: VMSVGA and Google-Chrome
Posted: 26. Apr 2019, 01:42
by piggyz
I'm now in 6.0.6 and the workaround is not running Google-Chrome. This problem just happen with Google-Chrome loaded.
As I said this happen with ANY not just this VM when running in SVGA3D video mode. And yes, 3D is a really important feature with modern OS, so I will never ever play without 3D, it help with everything multitasking related, moving windows, etc etc
Then, as I stated, 6.0.6 improved things related with VMSVGA driver, but Google-Chrome interaction.
PS: VBoxVGA driver is no more a choice becouse it pretty much can't do 3D anymore.