The VM Import wizard leads you step by step through importing your own virtual machines (VMs) to CloudShare. It’s super easy and when it’s done, you have a template of your VM ready to add to any CloudShare environment.
CloudShare validates your OVF file very quickly and tells you straight away if there’s a problem with it.
Your heavy disk files will be uploaded in the background, after you’re done. If you have several VMs to import, you can start another VM import right away while the disks are uploading.
CloudShare connects the VM automatically to Cloud Folders and the CloudShare network.
CloudShare creates a template ready to add to a new or existing environment.
To ensure a smoother import process, review these tips before you start your VM import.
If your VM meets these requirements, you can import it to CloudShare.
VMWare hardware versions 4 through 12. For full CloudShare functionality, make sure that VMware Tools is installed on your VM.
Oracle VirtualBox OVF format 1.0 (fully supported)
Oracle VirtualBox OVF formats 0.9 and 2.0 (supported with CloudShare autocorrection, which overrides the memory and CPU defined in the OVF)
CPUs: Any. However, if the VM has greater than four CPUs, the import automatically reduces the number to four.
Disks: At least one attached disk. (The VM can include more than one disk but you will not be able to change the disk size of the additional drives after uploading the VM to CloudShare)
Network adapters: Up to 10 network adapters
CPU, RAM, Disk size: Totals should not exceed your CloudShare hardware quota as agreed upon in your contract
Your VM CPUID mask must not be set to use an AMD processor.
The recommended way to access Windows VMs from a CloudShare environment is via Remote Desktop Protocol (RDP). If RDP is already enabled on the VM before import, RDP will be enabled on the imported VM after import. (Of course, RDP will only work as a way to access a VM in a CloudShare environment if the VM is connected to the CloudShare network.)
Therefore, we recommend to:
Make sure Remote Desktop is enabled on the VM.
If a firewall is enabled, make sure that port 3389 is open for remote access (or disable the firewall, because you’re protected behind CloudShare’s firewall and access controls).
Make sure the administrator account whose credentials you will provide for accessing the machine belongs to the Remote Users group.
To find out how to perform these tasks on a specific version of Windows, refer to https://technet.microsoft.com.
If you do import a VM that is not configured to support remote access via RDP, then, when you add that imported VM to a CloudShare environment, access to the VM will initially be restricted to console access. Once you connect to the VM via console, you’ll be able to change the configuration to enable RDP if you want to.
Prepare a VM image by exporting your VM to Open Virtualization Format (OVF).
To export a VMWare-based VM:
Export the VM using VMWare infrastructure (Workstation, ESX, vCenter Server, Fusion).
Hardware versions 4 through 12 are supported.
To export a VirtualBox-based VM:
Export using Oracle VM VirtualBox Manager.
OVF 1.0 format is recommended and fully supported. OVF 2.0 and 0.9 are also supported. However, CloudShare autocorrects OVF 2.0 and OVF 0.9 on import, assigning a default CPU and RAM size.
The export results in an OVA file, which is a single file distribution of an OVF file package, stored in the TAR format.
Extract the resulting OVA file using any compression tool that supports TAR format.
The resulting OVF package will contain:
One OVF descriptor, with file extension .ovf. This is an XML file that describes the packaged virtual machine.
One or more disk image files with the file extension .vmdk.
Zero or more other files, such as an .mf file.
Before you do your first VM import, you need to install IBM Aspera components on both your web browser and computer.
CloudShare VM import requires two separate Aspera components:
the Aspera Connect browser plugin, installed directly from the browser; and
the Aspera Connect application, downloaded from the Aspera website.
To ensure maximum robustness and resilience of the VM import process, it is important that the latest versions of both Aspera Connect components are used.
Select VM Import from the menu.
CloudShare detects and notifies you when one or both of the Aspera Connect components are not installed on your computer:
This notice also appears when only one of the two Apera Connect components is found on your computer. You should ensure that the latest version of both components is installed.
Click Install to install the Aspera Connect plugin on your browser. Follow your browser's instructions to complete the process. In case a problem occurs, refer to the Aspera support site.
Click Download to download the Aspera Client application. Follow the instructions provided by the application wizard to complete the process. In case a problem occurs, refer to the Aspera support site.
When you have completed the setup wizard, open your browser and the CloudShare VM Import page again.
If the VM Import page still displays the Aspera prerequisites message, try refreshing the page.
If you do not have permission to download or install an Aspera Connect component, you can still perform the VM import using the manual process supported by CloudShare. For complete information, see VM upload via Cloud Folders.
Select VM Import > Import VM.
If prompted, click Open Aspera Connect.
The STEP1: OVF Validation page appears.
Click UPLOAD to upload the .ovf file for validation, and browse to the file location.
CloudShare checks the .ovf file to verify the compatibility of the VM you are importing. This typically takes up to one minute.
If validation is complete and successful, the Validation Success! message appears.
If you imported a VirtualBox VM version 2.0 or version 0.9, a warning appears with an autocorrect option.
If validation fails, a validation error message appears. The message tells you the reason for the validation failure and provides guidance for solving the error. Follow the guidance provided and repeat the steps as necessary until you obtain a Validation Success! message.
If validation is successful, click Upload your VM to continue.
For VirtualBox version 2.0 or version 0.9, click Autocorrect OVF to continue.
CloudShare will make the necessary correction to your OVF file to enable the import. Your resulting VM will have 1 GB RAM and 1 CPU. These resources are modifiable after import, but if you prefer the imported VM to inherit the original RAM and CPU, you can choose to fix and upload again and then you can upload a VirtualBox 1.0 OVF file instead.
Click Browse VMDKs and browse to each .vmdk file. Repeat until all the .vmdk files from the VM export are added.
(You can multi-select files.)
Optionally, change the Machine name and Machine description.
Using the Admin Username and Admin Password fields, provide the login credentials for the VM.
Select a Project from the dropdown.
The imported VM will be accessible to the users who have access to the selected project.
Select the OS Type for the VM (Linux or Windows).
For the full benefit of the VM import process, leave Automatically connect machine to CloudShare network checked. CloudShare will automatically assign an IP address to the VM and connect it to the CloudShare network. For Linux VMs, this option also installs the CIFS client on the machine, which is needed for the machine to access Cloud Folders.
Click Upload VM.
If Aspera Connect requests permission to allow a connection with the Aspera server, click Allow.
The VM import begins.
You do not need to leave the page open while the import is in progress. The import may take hours or days, depending on the speed of your internet connection and the size of your files. There is no need to leave your page or browser running during the process.
While the import is in progress, you can start the import process again to import another VM, if needed.
To check the import status at any time, select Import VM from the menu and then VM Import List. The VM Imports page lists all VM imports and their status. From the list, you can click on one import job in the Name column to see more details.
Following VM Import and creating a basic environment from the import snapshot, your resulting VM has a default configuration:
The VM is connected to a Cloudshare network with secure access (accessible only via the Cloudshare Environment Viewer).
The Environment Viewer has a standard Overview tab and a tab for connecting to the imported VM.
Review the basic template and make any adjustments you need.
We recommend you review the following:
Click Edit Environment > Edit Networks to check and modify the network configuration.
Click Edit Environment > Customize Viewer to customize the end user's viewing experience (this customization is available only for CloudShare Enterprise). For more information, see Customizing The Environment Viewer.
Next: Take a snapshot to create a blueprint for reuse. (Note also that this is practice saves your work which is essential since environments expire after a period determined by the environment's policy.)