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.

Ubuntu install results in CL_DEVICE_NOT_AVAILABLE

Seth_P_
Beginner
628 Views

I've installed the Intel SDK on my Ubuntu VM, and the install seems to have worked fine. I can run the program here:

https://gist.github.com/rmcgibbo/6314452/download#

Which results in this info. As near as I can tell, it's all right. (Dunno if preferred vector widths are supposed to be 1, though.)

$ ./clDeviceQuery 

clDeviceQuery Starting...

 

1 OpenCL Platforms found

 

 CL_PLATFORM_NAME:     Intel(R) OpenCL

 CL_PLATFORM_VERSION:     OpenCL 1.2 LINUX

OpenCL Device Info:

 

 1 devices found supporting OpenCL on: Intel(R) OpenCL

 

 ----------------------------------

 Device Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz

 ---------------------------------

  CL_DEVICE_NAME:             Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz

  CL_DEVICE_VENDOR:             Intel(R) Corporation

  CL_DRIVER_VERSION:             1.2.0.8

  CL_DEVICE_TYPE:            CL_DEVICE_TYPE_CPU

  CL_DEVICE_MAX_COMPUTE_UNITS:        2

  CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS:    3

  CL_DEVICE_MAX_WORK_ITEM_SIZES:    8192 / 8192 / 8192 

  CL_DEVICE_MAX_WORK_GROUP_SIZE:    8192

  CL_DEVICE_MAX_CLOCK_FREQUENCY:    2300 MHz

  CL_DEVICE_ADDRESS_BITS:        64

  CL_DEVICE_MAX_MEM_ALLOC_SIZE:        626 MByte

  CL_DEVICE_GLOBAL_MEM_SIZE:        2507 MByte

  CL_DEVICE_ERROR_CORRECTION_SUPPORT:    no

  CL_DEVICE_LOCAL_MEM_TYPE:        global

  CL_DEVICE_LOCAL_MEM_SIZE:        32 KByte

  CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE:    128 KByte

  CL_DEVICE_QUEUE_PROPERTIES:        CL_QUEUE_OUT_OF_ORDER_EXEC_MODE_ENABLE

  CL_DEVICE_QUEUE_PROPERTIES:        CL_QUEUE_PROFILING_ENABLE

  CL_DEVICE_IMAGE_SUPPORT:        1

  CL_DEVICE_MAX_READ_IMAGE_ARGS:    480

  CL_DEVICE_MAX_WRITE_IMAGE_ARGS:    480

 

  CL_DEVICE_IMAGE <dim>            2D_MAX_WIDTH     16384

                    2D_MAX_HEIGHT     16384

                    3D_MAX_WIDTH     2048

                    3D_MAX_HEIGHT     2048

                    3D_MAX_DEPTH     2048

  CL_DEVICE_PREFERRED_VECTOR_WIDTH_<t>    CHAR 1, SHORT 1, INT 1, FLOAT 1, DOUBLE 1

 

 

clDeviceQuery, Platform Name = Intel(R) OpenCL, Platform Version = OpenCL 1.2 LINUX, NumDevs = 1, Device = Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz

 

System Info: 

 

 Local Time/Date =  19:13:19, 10/24/2014

 CPU Name: Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz 

 # of CPU processors: 2

 Linux version 3.2.0-23-generic (buildd@crested) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu4) ) #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012

 

 

TEST PASSED

 

However, I can't get further than CL_DEVICE_NOT_AVAILABLE when I call clCreateContext(). If I run the test program on this page:

http://wiki.tiker.net/OpenCLHowTo

The output looks like this:
 

$ ./cl-demo 1000000 10

Choose platform:

[0] Intel(R) Corporation

Enter choice: 

Choose device:

[0] Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz

Enter choice: 

*** 'clCreateContext' in 'cl-helper.c' on line 342 failed with error 'device not available'.

Aborted

 

Any ideas on what I'm doing wrong? As near as I can tell, the processor *should* be supported.

0 Kudos
1 Reply
Yuri_K_Intel
Employee
628 Views
Hi Seth, You mentioned that you are using a Virtual Machine. Please, have a look at the similar threads: https://software.intel.com/en-us/forums/topic/506830 https://software.intel.com/en-us/forums/topic/530471 To summarize, SSE4.2 should be available inside guest OS in order for Intel OpenCL CPU runtime to work. If you are using VirtualBox here is the note from corresponding ticket (https://www.virtualbox.org/ticket/8651): "VBox 4.3.8 RC1 provides experimental support for passing through SSE 4.1/4.2. Please have a look at the user manual -- it is required to enable this support manually per-VM." Thanks, Yuri
0 Kudos
Reply