Before you begin the VM import process, you'll need to perform the following preparation activities.
Ensuring the VM is CloudShare Compatible
If your VM meets these specifications, it can be imported into CloudShare.
Formats Supported by CloudShare
- For VMWare, hardware versions up to 21 are supported. For full CloudShare functionality, make sure that VMware Tools are installed on your VM.
- Oracle VirtualBox, OVF 1.0 is fully supported.
- Other OVF formats are supported with auto-correction. When required, CloudShare will override the imported OVF hardware specification - including the memory and CPU parameters that are defined there - in order to automatically create a valid CloudShare VM.
Guest OS
CloudShare supports VMs running any Linux or Windows guest OS.
Virtual Hardware Specification
- CPUs: Any number of CPUs are supported. However, if the VM used more than four CPUs, the import will automatically reduce 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). Only Virtual Machine Disk (VMDK) format is supported (i.e., no Floppy Disk or CD formats).
- Network Adapters: Up to 10 network adapters are supported.
- Sizes of CPU, RAM and Disk: Capacities should not exceed the CloudShare hardware quota specified for your account.
- CPUID Mask: The mask set for your VM should not use an AMD processor.
Tips for a Smooth VM Import
Reviewing these tips before you start your VM import can help achieve a smoother import process. For
VMDK configuration issues, avoid the following OVF mismatches:
- Fewer VMDK files uploaded. Ensure that the number of VMDK files listed in the OVF is correct. Uploading fewer files than listed will cause the process to fail.
- Incorrect VMDK filename. Ensure that the names contained in the OVF are exactly identical to the VMDK file names. A name mismatch will cause the process to fail.
Virtual serial ports are not supported. Remove any virtual serial ports on the local machine before starting the import. If found, a virtual serial port will cause the process to fail. If needed, virtual serial ports can be added again to the local machine following the import. For details and assistance, contact CloudShare Support.
Do not import entire vApp packages. Importing a VMware vApp package will cause the process to fail. Instead, you need to import the individual VMs - which are contained in the vApp package. To do this, during your preparation, do not export the vApp VM. Instead, open the vApp package and export each one of its VMs.