OpenCL* for CPU
Ask questions and share information on Intel® SDK for OpenCL™ Applications and OpenCL™ implementations for Intel® CPU.
Announcements
This forum covers OpenCL* for CPU only. OpenCL* for GPU questions can be asked in the GPU Compute Software forum. Intel® FPGA SDK for OpenCL™ questions can be ask in the FPGA Intel® High Level Design forum.
1719 Discussions

OpenCL SDK on VMWare

Bradley_S_
Beginner
1,886 Views

I have installed OpenCL SDK on VMWare and can run the example "Capsbasic" but if I try to run "MonteCarlo" or "GEMM" they fail with CL_DEVICE_NOT_AVAILABLE. Here is the otuput of all three:

[xxxx@xxxx CapsBasic]$ ./capsbasic
Number of available platforms: 1
Platform names:
    [0] Intel(R) OpenCL [Selected]
Number of devices available for each type:
    CL_DEVICE_TYPE_CPU: 1
    CL_DEVICE_TYPE_GPU: 0
    CL_DEVICE_TYPE_ACCELERATOR: 0

*** Detailed information for each device ***

CL_DEVICE_TYPE_CPU[0]
    CL_DEVICE_NAME: Intel(R) Xeon(R) CPU           E5410  @ 2.33GHz
    CL_DEVICE_AVAILABLE: 1
    CL_DEVICE_VENDOR: Intel(R) Corporation
    CL_DEVICE_PROFILE: FULL_PROFILE
    CL_DEVICE_VERSION: OpenCL 1.2 (Build 67279)
    CL_DRIVER_VERSION: 1.2
    CL_DEVICE_OPENCL_C_VERSION: OpenCL C 1.2
    CL_DEVICE_MAX_COMPUTE_UNITS: 2
    CL_DEVICE_MAX_CLOCK_FREQUENCY: 2330
    CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
    CL_DEVICE_ADDRESS_BITS: 64
    CL_DEVICE_MEM_BASE_ADDR_ALIGN: 1024
    CL_DEVICE_MAX_MEM_ALLOC_SIZE: 492150784
    CL_DEVICE_GLOBAL_MEM_SIZE: 1968603136
    CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE: 131072
    CL_DEVICE_GLOBAL_MEM_CACHE_SIZE: 6291456
    CL_DEVICE_GLOBAL_MEM_CACHELINE_SIZE: 64
    CL_DEVICE_LOCAL_MEM_SIZE: 32768
    CL_DEVICE_PROFILING_TIMER_RESOLUTION: 1
    CL_DEVICE_IMAGE_SUPPORT: 1
    CL_DEVICE_ERROR_CORRECTION_SUPPORT: 0
    CL_DEVICE_HOST_UNIFIED_MEMORY: 1
    CL_DEVICE_EXTENSIONS: cl_khr_fp64 cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_intel_printf cl_ext_device_fission cl_intel_exec_by_local_thread
    CL_DEVICE_PREFERRED_VECTOR_WIDTH_INT: 1
    CL_DEVICE_PREFERRED_VECTOR_WIDTH_LONG: 1
    CL_DEVICE_PREFERRED_VECTOR_WIDTH_FLOAT: 1
    CL_DEVICE_PREFERRED_VECTOR_WIDTH_DOUBLE: 1
    CL_DEVICE_NATIVE_VECTOR_WIDTH_INT: 4
    CL_DEVICE_NATIVE_VECTOR_WIDTH_LONG: 4
    CL_DEVICE_NATIVE_VECTOR_WIDTH_FLOAT: 2
    CL_DEVICE_NATIVE_VECTOR_WIDTH_DOUBLE: 2

[xxxx@xxxx GEMM]$ ./gemm
Platforms (1):
    [0] Intel(R) OpenCL [Selected]
Devices (1):
    [0] Intel(R) Xeon(R) CPU           E5410  @ 2.33GHz [Selected]
[ ERROR ] Sample application specific error: OpenCL error CL_DEVICE_NOT_AVAILABLE happened in file ../common/oclobject.cpp at line 322.

[xxxx@xxxx MonteCarlo]$ ./montecarlo
Platforms (1):
    [0] Intel(R) OpenCL [Selected]
Devices (1):
    [0] Intel(R) Xeon(R) CPU           E5410  @ 2.33GHz [Selected]
[ ERROR ] OpenCL error CL_DEVICE_NOT_AVAILABLE happened in file ../common/oclobject.cpp at line 322.

0 Kudos
4 Replies
Evgeny_F_Intel
Employee
1,886 Views

Hello Bradley S.,

Thank you for sharing your issue.

In general VM doesn't report SSE4.2/SSE4.1 instrunction set required by the OpenCL driver.

Could you please check if it's the case with your VM.

Evgeny

0 Kudos
Bradley_S_
Beginner
1,886 Views

a cat /proc/cpuinfo yields these flags:

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc arch_perfmon pebs bts xtopology tsc_reliable nonstop_tsc aperfmperf unfair_spinlock pni ssse3 cx16 sse4_1 xsave hypervisor lahf_lm dts

0 Kudos
Pameela
Beginner
1,886 Views

Operating system virtualization is a convenient way to run multiple operating systems at the same time, on the same hardware, without requiring rebooting. There are several technologies that allow sharing of the GPU by both the host (native) and guest (virtualized) operating systems.

0 Kudos
Jeffrey_M_Intel1
Employee
1,886 Views

In case you're still interested in the topic of virtualization, there is an emerging pathway for access to the GPU in a virtual machine described here:

https://software.intel.com/en-us/articles/how-to-setup-media-server-studio-r6-on-vt-d

Please watch for more on this topic on this forum as well as Media SDK's.  

0 Kudos
Reply