- Built off of QEMU, an open-source emulator which interoperates with KVM at near native performance
- Windows, Linux, and BSD operating systems support
- QEMU Guest Agent support allowing for quiesced snapshots and reporting additional information such as OS and kernel versions to the vm dashboard.
- Q35 machine type for modern motherboard emulation and i440FX for older system support
- Console access through VNC (native), Spice Client, or Serial Console
- Virtio paravirtualization device support for disks and network interface cards
- Hotplug support for disk drives and network interface cards
- Host processor and GPU passthrough support
Currently only NVIDIA GPU architecture is supported. See the GPU wiki page for more information.
- Cloud-init support allowing guest level automation on new deployments. See the recipes wiki for more information.
- Live migration with no downtime allowing physical host maintenance without interrupting workloads
Live migration is only possible when a physical device is not passed through to the vm.
- Automatic balancing on vm startup
When a vm is started the VergeIO appserver will look for the node with the most available compute resources in the cluster the vm is assigned to and start it on the determined node.
Virtual machines use the .raw format for virtual drives. When a vm is imported it is converted from the imported drive type to the .raw format automatically. Virtual machines can be imported into VergeIO in 4 ways.
- The VMware backup service
- The VergeIO NAS service
- Using the VergeIO clone utility (only accessible by downloading from your environment)
- Uploading the vm drives and configuration files directly to the media images section of your environment
The following type of files are supported when using media images for import
- IMG (Raw Disk Image)
- RAW (Binary Disk Image)
- QCOW (Legacy QEMU)
- QCOW2 (QEMU, Xen)
- VDI (VirtualBox)
- VHD/VPC (Legacy Hyper-V)
- VHDX (Hyper-V)
- OVA (VMWare, VirtualBox)
- OVF (VMWare, VirtualBox)
- VMDK (VMWare)
- VMX (VMWare)