Page Comparison

...

Import and capture of individual VMs is only available in private cloud. To capture resources from public cloud regions, onboard them as part of regions or virtual datacenters. See Manage virtual datacenters#Onboardfrompubliccloud

What does Abiquo import?

To import VMs (also called retrieve VMs), the physical machine must be in an Abiquo private cloud datacenter, or in the process of being added to one. You do not need to enable a datastore to import VMs that are running on the datastore.

What does Abiquo capture?

Abiquo captures the following VM configuration:

• CPU and RAM including hardware profiles

• Remote access configuration for VNC, including the password. But if there is no password, the platform disables remote access

  • If a user later releases a VM, the changes made in the platform will remain in the VM

• MAC addresses of compatible NICs and their VLAN tags and network details. Abiquo recommends that your VMs should have at least one NIC

  • Exception: Abiquo does not capture NICs on IPv6 networks

  • You can configure Abiquo to capture the DHCP configuration, see Abiquo configuration properties#capturedhcp

• Hard disks in compatible formats on the hypervisor datastores. See Template compatibility table

  • For ESXI, the platform will capture DVDs without a defined position in the boot order as ISO disks in the last position in the VM's boot sequence

When you capture a VM from NSX-T, you must add the VM to a VDC with the same network as the VM network. The platform will match the network by provider ID, not by VLAN tag as in the NSX-V integration.

During capture the platform will skip incompatible VMs and incompatible virtual hardware components.

• The platform does not add the virtual datacenter's default firewall policy to a VM as part of the capture process

• The boot disk must always be a "hard disk" on the hypervisor datastore

...