The XenCenter OVF Appliance Import, Export, and Disk Image Import wizards have proven to be very useful tools for many folks using and migrating to XenServer since their introduction with the XenServer 5.6 release.
For those ITPros using the wizards, understanding errors is important. I am going to cover a few of the most common errors in detail.
Note: The following error messages can only be found in the XenCenter log.
The log can be accessed by clicking “Help” in the XenCenter menu, then selecting “View Application Log Files” to open the folder. Then open the file “XenCenter.log”.
Cannot start XenAppliance Wizard
This error most frequently happens when the TransferVM component is missing from a XenServer 5.6 host, or when using XenCenter 5.6 to manage releases of XenServer prior to 5.6.
This can be caused by a number of issues including: custom installations, no “Local storage” storage repository, and others.
The TransferVM can be installed by one of the following:
- At the command prompt mount the installation media
- switch to the folder /opt/xensource/packages/files/transfer-vm
- execute the ./install-transfer-vm.sh script
If that does not work try the following:
- Mount original 5.6 ISO on XenServer
- mount /dev/cdrom /mnt
- cd /mnt/packages.transfer-vm/
- rpm -ivh xenserver-transfer-vm-5.6.0-31188p.noarch.rpm (this RPM may rename with different releases)
If you are installing from the network using HTTP, FTP, or NFS be sure to include the folder “packages.transfer-vm” when copying “packages.main” and “packages.Linux” (the Linux Supplimental Pack) to the path of your share point.
If this is done then try something like the following example:
“rpm -ivh http://mirror/XenServer_5.6.0/packages.transfer-vm/xenserver-transfer-vm-5.6.0-31188p.noarch.rpm“
iSCSI could not start the XenServer TransferVM XENAPI_PLUGIN_EXCEPTION
This most commonly happens when DHCP is not available on the XenServer management network. The TransferVM transport is started but is unable to reply with the IP address assigned from DHCP. The current requirement is that DHCP must be running on the same network that the XenServer management interface is connected to.
iSCSI initialization failure. An attempt was made to access a socket in a way forbidden by its access permissions
DHCP is available on the XenServer management network but iSCSI communication between the client machine and the XenServer is blocked. Check that the iSCSI port (3260) is open between the XenServer and the client machine performing the import.
Import.Process failed: NO_HOSTS_AVAILABLE
This error has been seen when the Fixup process attempts to boot the virtual machine and there are not enough free system resources for the VM to run. This is most commonly when there is not enough free RAM and all other requirements are met.
The appliance has been successfully imported, import does not need to be repeated.
Manually recovering the imported virtual machine has been documented in the following article: http://support.citrix.com/article/CTX125120
Could not create VDI on XenServer, SR_BACKEND_FAILURE_78 – VDI Creation failed [opterr=could not create file: “/var/run/sr-mount/<GUID>/<GUID>.img
If the file name being referenced ends in “.img” then this error is associated with the Fixup process. In this case the Fixup process was chosen but the ISO Storage Repository is not Read / Write. Thus when the wizard attempts to copy the fixup ISO to the Storage Repository it is denied.
The workaround for this is to:
- Copy the xenserver-linuxfixup-disk.iso to the ISO Storage Repository.
The ISO can be found on the XenCenter client machine in the following location:
C:\Program Files (x86)\Citrix\XenCenter\Plugins\Citrix\XenAppliance\External Tools
- The ISO Storage Repository should refresh and list the ISO in XenCenter.
- Repeat the import and this ISO should be used by the fixup option.