- 06 Sep 2024
- 2 Minutes to read
- Print
VM Import
- Updated on 06 Sep 2024
- 2 Minutes to read
- Print
Skillable has both VMware ESX and Windows Hyper-V available for lab hosting. When sending Virtual Machine (VMs) to be imported into the system via a Lab Services request, we support multiple formats and versions depending on the platform. The table below describes what VM sources we can import from. A full import means we can import both the Virtual Hard Disk and any VM configuration information. A virtual disk import means we can import the disks, but VM configuration is manual and information including CPU and RAM settings needs to be sent alongside the VMs to import.
Hyper-V on Windows 11 or Server 2022 has different VM Configuration Versions depending on the OS version. Windows 11 22H2 or later support up to VM Configuration Version 12.0 Server 2022 supports and defaults to configuration version 10. VM configuration above 10.0 is not compatible with a full import.
Platform | Source | Versions Supported1 | Import Notes2 |
---|---|---|---|
Hyper-V | Hyper-V | VM Configuration Version up to 10.0 | For a full import, please send a full VM export. Otherwise, import is virtual disks only. |
VM Configuration Version 10+ | Virtual disks only, compatibility not guaranteed. | ||
ESXi | ESXi | 5.0-7.0 Update 3 Hardware Version 19 | For a full import, please export VM as OVA/OVF. Otherwise, import is virtual disks only |
VMware Workstation | 12-16.2 | For a full import, please export VM as OVA/OVF. Otherwise, import is disks only. | |
Both | Virtual Box | 5.0-7.0 | Hyper-V import is disks only, please use VHD disk type. ESXi import is full when exported as OVA/OVF. Otherwise, import is disk only. |
1 To ensure the best compatibility, we recommend using the latest editions of software. Successful import of VMs from earlier editions is not guaranteed.
2 This applies to VMs uploaded to FTP or shipped via drive. For VMs uploaded through the Skillable Studio web interface, disk-only is the only supported method, and the disks must be in the correct format (.vhd/.vhdx for Hyper-V, ESXi format .vmdk for ESX).
If you have VM in a format not listed, from a hypervisor not listed, or have any questions please contact support.