...
This opens the Create Compute Instance window.
| Div | ||
|---|---|---|
| ||
Step 3: on the first part of Create Compute Instance window, name your instance and select an appropriate Linux image for it.
...
To select the correct image, select Change Image Source. This will allow you to browse the different available categories.
...
...
The image below shows an example of the image selection screen (choose a supported Linux version or - if appropriate - a prepackaged Charon-SSP VE marketplace image):
Selecting the Optionally, change the compartment. Select the correct image and confirming confirm your selection by clicking on Select Image at the bottom of the page. This will take you back to the Create Compute Instance window.
Step 4: on in the middle part of the Create Compute Instance window, select the appropriate shape (i.e., the virtual Linux Charon host hardware), the subnet membership of the instance and whether to assign a public IP address. If required, you can also create a new virtual cloud network or a new subnet here.
To select an appropriate shape conforming to the hardware requirements of the emulated SPARC system, click on Change Shape.
...
This will open a window where you can select the correct system type.
...
Confirming you selection will take you back to the Create Compute Instance window.
| Div | ||
|---|---|---|
| ||
Step 5: on the bottom of the Create Compute Instance window create a new SSH key-pair or upload the public SSH key of an existing key-pair that you will use to access your instance. If you create a new key-pair, you must download the private key and store it in a save place for later use. You can also download the public key.
Step 6: optionally define non-default parameters (including the size) for the boot volume.
The boot volume section allows you to configure the boot volume of your instance with additional non-default parameters. For example, you can configure disk encryption parameters and a non-default system disk size (recommended minimum system disk size: 30GB).
| Div | ||
|---|---|---|
| ||
Step 7 (supported starting with Charon-SSP marketplace images version 4.2.2 and VE license server 1.0.33): support an IMDSv2 authorization header for applications relying on the IMDS service to improve security. For this, open the additional options by clicking on Show Advanced Options at the bottom of the instance creation page, select the Management tab, and activate the authorization header, as shown below:
On existing instances, this parameter can be changed, by editing the instance metadata service settings for the instance (go to Instance Details and click on Edit in the line Instance Metadata Service).
Only change the configuration to IMDSv2 if the image you launched the instance from supports it. Otherwise, you may not be able to connect to your instance. Please note: at the time of writing, the official CentOS 7 image on OCI did not support the new feature. If you create an instance to be used as a host for a manual VE license server or Charon-SSP VE installation, verify the capabilities of the image used before you enable the new IMDSv2 feature.
Step 8 (only for Charon-SSP versions before 4.1.32): the correct networking type selection is important. Charon-SSP disables offloading parameters on the Ethernet interfaces it uses. This is required for proper functionality and good performance of the emulator. To allow this configuration to be correctly reflected in the underlying cloud instance NICs for Charon-SSP versions before 4.1.32, the correct networking type (HARDWARE ASSISTED (SR-IOV) NETWORKING) must be chosen for the instance. For this, open the additional options section by clicking on Show Advanced Options at the bottom of the instance creation page and select the Networking tab as shown below:
On this tab select HARDWARE ASSISTED (SR-IOV) NETWORKING (after creation, the instance will display the NIC Attachment Type ). Please observe the warning displayed: not all shapes support this type properly.
Step 8: Click on Create to create your instance.
Step 69: verify that your instance is running.
Your instance should now be visible in the list of compute instances.
...
Initial Access to the Instance
...