Citrix Systems 5.6 Server User Manual


 
44
incompatibilities, host memory constraints, or ISO SR issues. Likewise, issues with the TransferVM
template, a template specifically designed to facilitate importing and exporting VMs, may cause problems.
To check to see if the TransferVM template is installed
In XenCenter, select View > Hidden Objects. Make sure a check mark appears beside the Hidden
Objects menu item.
If present, the template appears under the host in the XenCenter tree.
Wizard does not start
The following error appears: "Cannot start XenAppliance wizard, no valid session information provided."
If you receive this message, check the XenCenter log for more details and see the description of the entry
in the table that follows:
XenCenter log entry Suggestions
"iSCSI initialization failure. A connection attempt
failed because the connected party did not
properly respond after a period of time, or
established connection failed because connected
host has failed to respond."
Make sure DHCP is running on the network
where the XenServer management interface is
connected. The transfer mechanism used by
the OVF Appliance Wizard is dependent upon
obtaining an IP address through DHCP. If DHCP
is not the issue, often trying to rerun the import or
export wizards will generally result in success.
"TransferVM Missing." The TransferVM is template only included in
XenServer 5.6 and higher. If you have verified that
you are running XenServer 5.6 or higher and the
problem still persists, the TransferVM template
may have been deleted. It can only be restored by
re-installing the XenServer. The template cannot
be installed on hosts not using local storage.
Errors after completing the wizard
The XenServer OVF Appliance Wizard writes most errors that occur during import to the XenCenter log.
Consequently, the XenCenter log is a good place to begin troubleshooting.
The following errors may occur when exporting VMs and importing appliance packages or disk images:
Issue Possible Causes Corrective Action
OVF file is not understood When this type of error appears,
it can indicate that the wizard
encountered something in the
package that is non-compliant
with the OVF standard.
If importing, consider importing
the individual disk image files in
the OVF package using the Disk
Image Import wizard.