Shell Commands › Utilities › image2class: Virtual Machine Image Import Utility › image2class: Virtual Machine Image Import Utility - Limitations

image2class: Virtual Machine Image Import Utility - Limitations

Managed Appliances

To create a managed CA 3Tera AppLogic appliance from the specified virtual machine image, the image must conform to the following requirements (or else the import will fail):

• openssh-server or similar should be installed and operational; it needs to be automatically started on boot and configured to allow for root public key authentication.
• The iproute2 utility should be installed and operational.
• The dhclient utility should be installed and operational.
• The wget utility should be installed and operational.
• For Ubuntu appliances, NetworkManager should be disabled/removed.
• For 64-bit Linux-based appliances, the libc6-i386 package should be installed.

General limitations of image2class

• When using the --managed option, only Debian and Redhat based Linux distros are supported
• When using the --unmanaged option, Linux, Windows 2003 and 2008 are supported. If you need to make a windows appliance managed, you need to install the windows server msi, provided with CA 3Tera AppLogic as described in the Windows Installation section of the Appliance Developer Guide.
• User interaction is required when creating a managed appliance.
• Upon conversion to a managed appliance, user logins are disabled. Access to a managed appliance is typically done by using SSH public key authentication.
• When importing an OVA image, image2class currently supports files containing a definition of a single virtual machine. OVA files which specify multiple virtual machines are not supported.
• An imported image may have a maximum number of 4 volumes.
• Managed appliances will have a '/dev/hdaX' device schema and their fstab will be updated to that schema while importing. Unmanaged appliances will use a 'hda|hdb|hdc|hdd' device schema; they will have to be manually changed to use that schema (if they use something else).

Notes:

Image2class does not support vmdk files of type streamOptimized. This is the default disk type when exporting from an ESX server. If you need to export an OVA image from an ESX server, you need to use the ovfexport.sh utility which is provided as part of the AppLogic release (located in the download folder for the release on your Backbone Fabric Controller server). To use ovfexport.sh:

ovfexport.sh <source> <target>

Where <source> is the source URL locator to an OVF package, VMX file, or virtual machine in vCenter or on ESX Server and <target> is the local file that will be created

Example:

ovfexport.sh vi://localhost/my_vm my_vm