Import VM Images

Need to migrate from your current solution to Antsle? No problem!

You can drag & drop your existing VM files to antman, and they will be imported as a template. That means you can create as many antlets from it as you want.

Whether you're migrating from VirtualBox, VMware or Hyper-V, we can import many formats:

• .raw

• .bochs

• .cloop

• .cow

• .dmg

• .iso

• .qcow

• .qcow2

• .qed

• .vmdk

• .vpc

• .img

• .vhd

• .vhdx

A .vdi image (VirtualBox native format) must be converted to a raw .img format first by running the following command on the machine that hosts VirtualBox.

VBoxManage clonemedium abc.vdi abc.img --format RAW

replace 'abc' with the name of your .vdi image.

If you want to import OVA or OVF files, please convert them to qcow2 before importing. Information on how to do the conversion is readily available on the web, e.g. here.

Import VM Image

Select 'Templates' and the 'Import' tab

From here you can either drag and drop your VM file or select 'Path' from the Image Source field. If you select 'Path' you must supply a path to the VM file. The pop-out in the image below shows a path to an external USB drive connected to the Antsle which contains the VM image file.

Prior to antMan v2.x

1. Click 'Manage Templates' in Antman

2. In the Templates dialog click 'Import KVM/QEMU image' button

3. Drag your image file into the Import Image dialog

Importing Virtual Drives

In case you have virtual drives attached to your VM being imported, and you want to import these virtual drives as well, here’s how to do it.

Let’s assume your drives are named alice.vmdk and bob.vmdk, and you want to attach them to antlet Chris.

Then just copy the virtual drive files to your Antsle.

On your Mac or Linux workstation, you can issue these commands:

ssh [email protected] mkdir -p /antlets/Chris/antsle:volumes/
scp alice.vmdk bob.vmdk [email protected]:/antlets/Chris/antsle:volumes/

On Windows, you can use PuTTY and WinSCP instead. Or use Filezilla with SFTP

Then just edit the XML of your antlet Chris. See NOTE below before running the 'virsh edit' command. While logged in to the Antsle, for KVM antlets, run:

virsh edit Chris

if it’s an LXC antlet use the '-c lxc:///' option.

virsh -c lxc:/// edit Chris

NOTE: This will start a vim editor. If you are not familiar with vim, prefix the command with 'EDITOR=nano' to launch the nano text editor:

EDITOR=nano virsh edit Chris

Then find the <devices> section in the XML. KVM antlets will have at least one <disk> section inside the <devices> section. LXC antlets by default do not have a <disk> section.

Add a <disk> block nested inside the <devices> block for each virtual disk you are importing. Example:

<disk type='file' device='disk'>
      <source file='/antlets/Chris/antsle:volumes/alice.vmdk'/>
      <target dev='hda' bus='ide'/>
</disk>
<disk type='file' device='disk'>
      <source file='/antlets/Chris/antsle:volumes/bob.vmdk'/>
      <target dev='hdb' bus='ide'/>
</disk>

You might have to change the names hda and hdb so that there is no conflict with other drives.

Save the XML, restart your antlet and you’re ready to go!