Create OVA Virtual Server

OVA virtual servers are created from the OVAs uploaded to the Control Panel and saved as specific OVA  templates . The OVAs are uploaded at the Control PanelCloud > Templates menu. For more information, refer to the Upload OVAs section of this guide. 

To create a virtual server from the OVA:

  1. Go to your Control Panel > Cloud > Virtual Servers menu and click the "+" button, or click the Create Virtual Server button at the bottom of the screen. This will start a VS creation wizard.
  2. Fill in the wizard step by step. Each of these steps is described in the corresponding sections below.
  3. Click the Create Virtual Server button to start the creation process. You will be taken to the virtual server details screen.

Step 1 of 4. Templates

At this step, choose a specific OVA template from which your virtual server will be built.  
To choose a template:

  1. Click the OVA template group.

    If you do not see OVA template group in the Template store, go to your Profile > Bucket tab and check Limits for template store section. If OVA template group is missing, add it by clicking the "+" button in the upper right corner of this section.

  2. Select the template. 
  3. Click Next.

 Licensing Type for Windows VSs

Choose the license type you require:

  • For the KMS type, choose the licensing server
  • For your own license, type your license key

If you don't specify the licensing type, MAK licensing will be set by default.

Consider the following when creating a VS on Windows templates:

  • It is possible to deploy Windows virtual servers without running sysprep. To do so, you need to disable the Run Sysprep option for the Compute zone the virtual server will be built on. See Create Compute Zone section for details.
  • If there are several virtual servers simply deployed from the same template in the cloud, they will have identical SIDS. This will result in the system conflict.

Windows 10/Windows Server 2016 Virtual Servers

If you want to build Windows 10/Windows Server 2016 VSs, the following limitations apply to KVM compute resources:

  • Windows 10/Windows Server 2016 VSs can be built on the CentOS 6/CentOS 7 compute resources with the following CPU models:
    • at least Ivy-Bridge-based Intel Xeon E series v2

    • Opteron G2, G3, G4, G5, and G6

  • CPU flag 'fsgsbase' is required. For more information on CPU flags refer to Manage Extended CPU Configuration for Compute Zone.

Proceed to the following step of the wizard and specify the virtual server properties.

Step 2 of 4. Virtual Server Properties

At this step you need to indicate your virtual server's properties.

Specify the following virtual server properties:

  • Label - the label of the virtual server. The required parameter.
  • Hostname - the hostname of the virtual server. The required parameter. The hostname should consist of letters [A-Z a-z], digits [0-9] and dash [ - ]. For more info on hostname validation, refer to RFC standard documentation.

    • The hostname length should be between 1 and 15 characters.
    • The following symbols are not allowed:
      • percent sign [%]
      • double quotation marks [“]
      • brackets [<,>]
      • vertical bar [|]
      • caret [^]
      • ampersand [&]
      • parentheses [(,)]
  • Domain - specify the domain for this VS. The default value is localdomain. This parameter is not applicable to Windows virtual servers. 

    For example: - specify ' test' as hostname, ''-  as domain. If you leave the domain field blank, the default value ' localdomain' will be used and you will get the following -
  • Password - a secure password for the VS. It can consist of 6-99 characters, letters [A-Za-z], digits [0-9], dash [ - ] and lower dash [ _ ], and the following special characters: ~ ! @ # $ * _ - + = ` \\ { } [ ] : ; ' , . ? /. You can use both lower- and uppercase letters. If you leave password field blank, it will be generated automatically. 

    The password, set at this step, will overwrite the password specified in OVA file.

  • Password confirmation - repeat the password to confirm it.
  • Encrypt password - move the Encrypt Password slider to the right, to encrypt your password, then enter an encryption key in the field that appears.

Click Next to proceed to the following step of the wizard to specify the virtual server resources.

Step 3 of 4. Resources

At this step, you get two tabs - Instance Packages and Create Your Own. You can not use instance package (it will be grayed out), as it is already preconfigured package which can differ from OVA configurations. OVA template already includes resource configurations, which are imported to the Create Your Own tab. You can change these resource configurations (except primary disk size).

Compute Resources

  • Compute Zone - the compute zone where the VS should be imported
  • Compute Resource - the specific compute resource where the VS from OVA will be imported. Compute resource may be selected automatically according to the set provisioning type.
  • RAM - set the amount of virtual server's RAM.The minimum value is the RAM value taken from OVA file. The maximum RAM depends on your bucket's settings. The maximum RAM that can be assigned to a VS is 168 GB regardless of the Max RAM value set in the bucket. 
  • CPU Cores - set the amount of virtual server's CPU cores. The minimum value is the amount of CPU cores specified in OVA file.For KVM compute resources, this parameter sets CPU sockets by default, unless CPU topology is enabled.
  • CPU Priority (or CPU Units) - set virtual server's CPU priority. If the CPU units are switched on in the bucket for this user, then CPU priority is replaced with CPU units. Refer to Billing Calculation section for details on CPU units and CPU priority.

  • Use CPU Topology - move the slider to the right, to set the following parameters:
    • CPU Sockets - set the amount of sockets.

Storage Resources

When you create a VS from the OVA template, you can select different data stores to put disks on them. During the creation process, all disks are imported from the OVA configuration and their size cannot be changed. The first disk becomes primary and the next disks will be numbered in the subsequent order starting from 2 (Disk 2, Disk 3, etc.). When you select a data store for each of your VS`s disks, pay attention to its price and the total free disk capacity

How the data store free space is calculated

Case A. There are no limits in the bucket, so the available space is “unlimited”. In this case, the actual free disk space for each data store is displayed. When you select a data store, the free space for this data store will decrease by the number of GB of the disk selected. 

Case B. There are some limits in the bucket, and only one data store zone is available. In this case, two options are possible:

  • If the maximum space allowed by bucket is less than the actual available space on the data store, then the total free disk space for all data stores for this user is displayed. When a data store is selected for a disk, the available disk size will decrease per each data store.
  • If the data store disk space is less than the bucket limit, then the actual free disk space is displayed. When a data store is selected for a disk, the available disk size will not decrease. 

Case C. There are some limits in the bucket, and several data stores are available. In this case, the data stores from different zones in the wizard are displayed. The data store free space will be displayed and calculated similarly to Case B with one exception. When a data store is selected for a disk from zone A, but there are also data stores in the wizard from zone B, the available disk size will not decrease for data stores from zone B.

Primary Disk

  • Data Store - choose a data store for VS's primary disk. Each data store free space is indicated in brackets.
  • Size - fixed primary disk size imported from OVA configuration

Disk 2

  • Data Store - choose a data store for VS's disk. Each data store free space is indicated in brackets.
  • Size - fixed disk size imported from OVA configuration

Network Configuration

Network Interface 1

When you create a VS from the OVA template, you can select in which network the VS will be created. The first network becomes Network Interface 1 and the next networks will be numbered in the subsequent order starting from 2 (Network Interface 2, Network Interface 3, etc.). The amount of network interfaces will be taken from the OVA configuration. If the OVA has several network interfaces, you can change the following parameters for each of them. 

  • Network - choose the network from which the VS should get the IP address
  • IP net - select from the drop-down list the IP net from which the IP address should be assigned
  • IP range - select from the drop-down list the IP range from which the IP address should be assigned
  • IP address - assign an IP address for the VS from the drop-down menu. Indicate compute resource and network to have the list of available IPs.

    Be aware, that you should choose only public IP address. Otherwise VS, built from OVA, will not work properly.

  • Show only my IP address - tick this checkbox to view only own IP addresses in the IP addresses dropbox.
  • Selected IP address - if the option is available, you can also assign an IP address for the VS from the drop-down menu. Indicate Compute resource and network to have the list of available IPs.
  • Port Speed - set the port speed for this VS
  • Selected IP address option is enabled via the "Show IP address selection for new VS" slider on the Settings > Configuration screen (under the System tab).
  • You can't select unlimited port speed if the Network Zone is not selected. In this case the port speed will be 1 by default.
    It's possible to create virtual server with unlimited network speed without selecting a network zone only if you have only one Network Zone assigned to your bucket.

Click Next to proceed to the last step of the wizard.

Step 4 of 4. Confirmation

At this step, configure the automation settings. This is the final step of the virtual server creation wizard.
  • Move the Build Virtual Server slider to the right if you want the system to automatically build the VS. If you leave this box blank, you will have to build your server manually after it is created.
  • Move the Boot Virtual Server slider to the right if you want the virtual server to be started up automatically.

At the Confirmation step you can find the configuration summary of VS, which will be created.  You can view template's name, RAM size, number of networks, primary disk size, number of cores.

After you set up all parameters, click the Create Virtual Server button to start the creation process.

When virtual server is created, you will be redirected to VS details page. 

You can view VS creation logs at VS details page (activity log section). If ProvisionGRUB log fails during VS creation, take the following steps:

  1. Go to VS console.
  2. Log in with credentials, created at step 2 of the VS creation wizard.
  3. Run the following command:

    grub2-install /dev/sda || grub-install /dev/sda

    After running the command, reboot the VS.