Connect to the DevCloud using SSH Clients.
The Cygwin* environment offers a convenient way of connecting to the Intel® DevCloud from a local machine running Windows*, whether you have a direct connection or find yourself behind a proxy. If you already have Cygwin installed, please skip to the SSH connection instructions.
The following instruction will help you install a minimal version of Cygwin for accessing Intel DevCloud. For your convenience we’re providing a simple script that automates the installation of Cygwin. As an alternative, we’ve also provided instructions for the manual installation.
Download this simple Windows batch script install_cygwin.bat. It can be run from anywhere on your disk, either by executing it from the terminal or by double clicking on it.
The script uses curl to download the Cygwin setup file. When asked to provide proxy details, you can do so by entering proxy:port when asked, or by simply hitting enter to continue without a proxy.
The default installation path is c:\cygwin64. The script will prompt you to change this if you wish to install elsewhere.
A number of Cygwin packages are downloaded during the installation. The script is configured to use mirrors.kernal.org as the default download site. A full list of Cygwin mirror sites can be found on the Cygwin homepage https://www.cygwin.com/.
There are two options for configuring your SSH connection.
The easiest method to set up an SSH connection to is by downloading and running an automated installer. The installer will add SSH configuration entries to ~/.ssh/config and create a private SSH key file inside ~/.ssh.
In the interest of security, some business networks require that all outgoing connections are established via a corporate proxy. If you followed the instructions above but are getting the error "Connection timed out", you are likely on such a business network. To comply with the security rules of your company, modify ~/.ssh/config as below:
Here, <proxy_name> and <port> are, respectively, the hostname and port of the corporate proxy. It is usually provided to you by your IT department.
Log into the Intel DevCloud
The first time you log in you will be asked to add the hostdevcloud to the list of know hosts. Answer “yes” to the prompts
If you are running Linux or a macOS operating system you can access the cluster using the native Secure Shell (SSH) client, you will need to set up SSH tunneling as described below.
The easiest method to set up SSH connection to is by downloading and running an automated installer. The installer will add SSH configuration entries to ~/.ssh/config and create a private SSH key file inside ~/.ssh. This method works best if you have only one account.
Alternatively, if you do not want a script to modify your SSH configuration, you can proceed with manual installation instructions below.
The following SSH settings are required for Visual Studio Code* remote access.
In the interest of security, some business networks require that all outgoing connections are established via a corporate proxy. If you followed the instructions above but are getting the error "Connection timed out", you are likely on such a business network. To comply with the security rules of your company, modify ~/.ssh/config as below:
Here, <proxy_name> and <port> are, respectively, the hostname and port of the corporate proxy. It is usually provided to you by your IT department.
After the preparation steps above, you should be able to log in to your login node in the Intel® DevCloud without a password.
Upon the first login, you will be asked to add the hostdevcloud to the list of known hosts. Answer "yes":
Next time you log in, you will only need to type ssh devcloud to log in:
Once your connection is set up, you can copy local files to your login node like this:
And you can copy files from your login node back to your home computer like this:
To get started with Microsoft Visual Studio Code* and establishing a connection to Intel® DevCloud follow the instructions below.
The easiest method to set up an SSH connection to is by downloading and running an automated installer. The installer will add SSH configuration entries to ~/.ssh/config and create a private SSH key file inside ~/.ssh.
In the interest of security, some business networks require that all outgoing connections are established via a corporate proxy. If you followed the instructions above but are getting the error "Connection timed out", you are likely on such a business network. To comply with the security rules of your company, modify ~/.ssh/config as below:
Here, <proxy_name> and <port> are, respectively, the hostname and port of the corporate proxy. It is usually provided to you by your IT department.
The Sample Browser for Intel OneAPI Toolkits Extension allows you to view code samples directly in Visual Studio Code*. Learn how to install the extension and download your first sample below.
Once completed working on DevCloud you can close the remote connection by selecting File -> Close Remote Connection from the VS Code* menu. Alternatively, click the remote-ssh notification in the lower-left corner of the VS Code* window that says SSH:devcloud-vscode and select Close Remote Connection from the list of Remote-SSH commands
This tutorial will walk you through the steps of running a sample with Intel® Open Volume Kernel Library, one of the libraries included in the Intel® oneAPI Rendering Toolkit (Render Kit) for Linux* (Beta). Since the Render Kit is a collection of powerful libraries for high-fidelity visualization applications we’re enabling VNC remote access on a limited number of compute nodes which will be labeled renderkit.
Note: This guide depends on SSH settings that have been introduced recently. Please review the Linux or macOS* (SSH client) page in order to make the necessary SSH configuration changes.
In order to establish a VNC remote connection you will need to follow these steps:
For more information about how to install the TurboVNC client please visit:
The TurboVNC server will generate a one time password (OTP) that is required later when starting the TurboVNC client.Note: Please review the Linux or macOS* (SSH client) page in order to make the necessary SSH configuration changes required for this step.
Use the name of the compute node you acquired at the previous step:
Enter the OTP as indicated.
You can adjust the quality of the connection as well as the resolution to fit your needs using the Options menu.
Locate and execute the vklExamples demo:
Before releasing the compute node back to the resource pool please shutdown the TurboVNC server using the following command:
The Cygwin* environment offers a convenient way of connecting to the Intel® DevCloud from a local machine running Windows*, whether you have a direct internet connection or find yourself behind a proxy. If you already have Cygwin installed, please skip to the SSH connection instructions.
The following instruction will help you install a minimal version of Cygwin for accessing Intel DevCloud. For your convenience we’re providing a simple script that automates the installation of Cygwin. As an alternative, we’ve also provided instructions for the manual installation.
Download this simple Windows batch script install_cygwin.bat. It can be run from anywhere on your disk, either by executing it from the terminal or by double clicking on it.
The script uses curl to download the Cygwin setup file. When asked to provide proxy details, you can do so by entering proxy:port when asked, or by simply hitting enter to continue without a proxy.
The default installation path is c:\cygwin64. The script will prompt you to change this if you wish to install elsewhere.
A number of Cygwin packages are downloaded during the installation. The script is configured to use mirrors.kernal.org as the default download site. A full list of Cygwin mirror sites can be found on the Cygwin homepage https://www.cygwin.com/.
There are two options for configuring your SSH connection.
The easiest method to set up an SSH connection to is by downloading and running an automated installer. The installer will add SSH configuration entries to ~/.ssh/config and create a private SSH key file inside ~/.ssh.
In the interest of security, some business networks require that all outgoing connections are established via a corporate proxy. If you followed the instructions above but are getting the error "Connection timed out", you are likely on such a business network. To comply with the security rules of your company, modify ~/.ssh/config as below:
Here, <proxy_name> and <port> are, respectively, the hostname and port of the corporate proxy. It is usually provided to you by your IT department.





There are two options for configuring your SSH connection.
The easiest method to set up an SSH connection to is by downloading and running an automated installer. The installer will add SSH configuration entries to ~/.ssh/config and create a private SSH key file inside ~/.ssh.
Alternatively, if you do not want a script to modify your SSH configuration, you can proceed with manual installation instructions below.
In the interest of security, some business networks require that all outgoing connections are established via a corporate proxy. If you followed the instructions above but are getting the error "Connection timed out", you are likely on such a business network. To comply with the security rules of your company, modify ~/.ssh/config as below:
Here, <proxy_name> and <port> are, respectively, the hostname and port of the corporate proxy. It is usually provided to you by your IT department.





Use this simple sample to confirm that you are connected to oneAPI DevCloud
The following describes the process of submitting build and run jobs to PBS.
A job is a script that is submitted to PBS through the qsub utility. By default, the qsub utility does not inherit the current environment variables or your current working directory. For this reason, it is necessary to submit jobs as scripts that handle the setup of the environment variables. In order to address the working directory issue, you can either use absolute paths or pass the -d <dir> option to qsub to set the working directory.
Jobs submitted in batch mode are placed in a queue waiting for the necessary resources (compute nodes) to become available. The jobs will be executed on a first come basis on the first available node(s) having the requested property or label.
The interactive mode offers the most familiar way to work with the DevCloud. In this mode you will be able to work with a compute node just like you would normally do on a local system.
There are some caveats. First, a request for an interactive session will be placed in a queue. A compute node will be allocated as soon as possible, and no guarantees can be made regarding the wait time. Secondly, any tasks started on a compute node in interactive mode will be terminated when the connection is interrupted.
Our recommendation is to use the interactive mode sparingly and only for scenarios not feasible in batch mode like stepping through code when debugging applications.
You can compile or run oneAPI designs on the FPGA platform using the Intel DevCloud, which is set up with an Intel® Programmable Acceleration Card with Intel® Arria® 10 GX FPGA and the necessary software stack. For more information, refer to FPGA Design Development and Workloads for Hardware Acceleration.
The same vector-add sample from above can be compiled to target the FPGA Emulator or the FPGA Hardware.
Explore the samples already installed in Step 2.