VMWare (that I used in the past) is also not capable of using CUDA. (hope this helps)
2016-04-26 9:29 GMT+02:00 Bastien Montagne <[email protected]>: > This issue sounds rather odd indeed - though trying to run Blender on a > linux VM from win10 host is looking for issues, imho… :P > > A couple of things to try: > * Run blender on that VM with the software OpenGL drivers (using the > `blender-softwaregl` distributed with official blender), this should > definitively rule out potential graphic driver issues. > * Run official Blender releases (archives from > download.blender.org/releases), those are nearly totally statically > linked, so should help spotting possible libs issues. > * Create a debug build with asan enabled > ( > https://wiki.blender.org/index.php/Dev:Doc/Tools/Debugging/GCC_Address_Sanitizer > ), > found that tool tremendously easier to use than valgrind, and it already > catches a lot of memory errors. > > Hope this help, > Bastien > > Le 26/04/2016 08:52, Dave Plater a écrit : > > Hi, I maintain blender for openSUSE and wondered if someone can help to > > shed light on a difficult bug I'm working on. See: > > https://bugzilla.suse.com/show_bug.cgi?id=976293 > > I've had the reporter run gdb and strace on blender but I can't see > > anything in his output. After building a debug blender with gdb symbols, > > jemalloc and valgrind, blender ran under valgrind. > > Thanks, > > Dave Plater > > _______________________________________________ > > Bf-committers mailing list > > [email protected] > > https://lists.blender.org/mailman/listinfo/bf-committers > > > > _______________________________________________ > Bf-committers mailing list > [email protected] > https://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list [email protected] https://lists.blender.org/mailman/listinfo/bf-committers
