-
Exploring the XenCenter workspace
-
-
-
-
Importing and Exporting VMs
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Importing and Exporting VMs
You can import VMs from OVF/OVA packages, from disk images, and from XenServer XVA files. VMs can be exported as OVF/OVA packages and as XenServer XVA files. Import and export VMs in XenCenter using the Import and Export wizards.
You can import or export a UEFI-enabled VM created on a XenServer® server as an OVA, OVF, or an XVA file. Importing a UEFI-enabled VM from other hypervisors is not supported.
Notes:
It is not guaranteed that you can import a VM that was exported from a more up-to-date system onto a less up-to-date system. For example, if you export a VM from a host that is at the latest level on the Early Access update channel, you might not be able to import this VM into a host that is at the latest level on the Normal update channel straight away. Before you can import the VM in to that host, the host on the Normal channel must reach the same level of updates as the Early Access channel had when the VM was exported.
This behavior is caused by additional metadata that might be added in later updates, which earlier versions do not understand.
VM group settings are not retained when a VM is exported.
Supported import and export formats
| Format | Description |
|---|---|
| Open Virtualization Format (OVF and OVA) | OVF is an open standard for packaging and distributing a virtual appliance consisting of one or more VMs. For more information about XenCenter support for OVF and OVA file formats, see Open Virtualization Format. |
| Disk image formats | Virtual Hard Disk (VHD) and Virtual Machine Disk (VMDK) format disk image files can be imported using the Import wizard. You might want to import a disk image when only a virtual disk image is available, but there is no OVF metadata associated with it. For more information about supported disk image formats, see Disk Image Formats (VHD and VMDK). |
| XenServer XVA format | XVA is a format specific to Xen-based hypervisors for packaging a single VM as a single file archive of a descriptor and disk images. Its file name extension is .xva. |
Which format to Use?
Use OVF/OVA to:
- Share XenServer vApps and VMs with other hypervisors that support OVF.
- Save more than one VM.
- Secure a vApp or VM from corruption and tampering.
- Include a license agreement.
- Simplify vApp distribution by storing an OVF package in an OVA.
Use XVA to:
- Import and export VMs from a script with a command line interface (CLI).
(Windows VMs only) Installing XenServer VM Tools for Windows
If the pool contains Conversion Manager version 8.5.0 or later, after Windows VMs are created successfully from an imported file, a fixup process begins. The fixup process uninstalls VMware Tools, if they are present. If you selected this option, it also installs the XenServer VM Tools.
(Linux VMs only) Operating System Fixup
For imports of Linux VMs that were created on another hypervisor, XenCenter® includes an advanced hypervisor interoperability feature Operating System Fixup. This feature aims to ensure a basic level of interoperability for some Linux VMs created on hypervisors other than XenServer.
Operating System Fixup is supplied as an automatically booting ISO image that is attached to the imported VM’s DVD drive. It performs the necessary configuration changes when the Linux VM is first started, and then shuts down the VM. The next time the new Linux VM is started, the boot device is reset, and the VM starts normally.
Note:
Operating System Fixup does not convert the guest operating system from one hypervisor to another.
The Operating System Fixup ISO is located in your XenCenter installation in the directory C:\Program Files (x86)\XenServer\XenCenter\External Tools.
To use Operating System Fixup on imported disk images and OVF/OVA packages, you enable the feature on the OS Fixup Settings page of the XenCenter Import wizard. Specify a location to copy the Fixup ISO to so that XenServer can use it.
Operating System Fixup requirements
Operating System Fixup requires an ISO SR with 40 MB of free space and 256 MB of virtual memory.
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.