Migrating VMs
Overview
KorGrid offers flexible options for importing workloads from other systems, including tools for bulk migrations and comprehensive support for import from media images (VMDK / VHD / VHDX, OVF / OVA, VMX, QCOW2, etc.). Virtual machines can be transferred directly into the environment, allowing upload and configuration manually or through automated tools. This versatility makes it easy to transition from other platforms while maintaining control and continuity.
Migration Methods
VMware Connector
Recommended for: Small to large VMware production environments
A full backup of source virtual machines into your tenant is performed using the VMware connector. Incremental backups are then performed to capture only the changes, leveraging VMware's Change Block Tracking (CBT) for efficient transfer. Once the incremental backup duration stabilizes, indicating minimal ongoing data churn, the system is considered ready for cutover with minimal downtime.
Key Features:
- Live migration from running VMware environments
- Incremental backup support leveraging VMware CBT
- Batch import capabilities for multiple VMs
- Hardware-independent data access
- Minimal cutover downtime
Additional Resources: - VMware DR Backup
Uploaded Files
Recommended for: Individual VMs and mixed virtualization environments.
Upload VM configuration and disk files (VMX, VMDK, OVF, VHD, QCOW2, etc.) to the vSAN and import them individually. This method provides maximum compatibility across different source platforms.
Key Features:
- Supports 12+ file formats including VMware, Hyper-V, VirtualBox, and QEMU
- Ideal for importing VMs from shut-down environments
- Complete control over import process and timing
- Works with any virtualization platform that can export standard formats
Clone Utility
Recommended for: Physical-to-virtual (P2V) and cross-platform migrations
Block-level migration utility for importing physical machines and VMs from various platforms directly into KorGrid with minimal downtime.
Key Features:
- Physical-to-virtual (P2V) migration support
- Virtual-to-virtual (V2V) migration from any platform
- Block-level data transfer for efficiency
Supported File Formats
KorGrid supports a wide range of VM file formats:
Format | Source Platform | Description |
|---|---|---|
VMX, VMDK | VMware | VMware configuration and disk files |
OVF, OVA | VMware, VirtualBox | Open virtualization standard |
VHD, VHDX | Hyper-V | Microsoft virtualization formats |
QCOW, QCOW2 | QEMU, KVM | QEMU copy-on-write formats |
VDI | VirtualBox | VirtualBox disk images |
IMG, RAW | Various | Raw disk image formats |
Migration Planning
Pre-Migration Checklist
Source Environment Preparation
Document VM specifications (CPU, RAM, disk sizes, network settings, etc.)
Remove hypervisor-specific tools (VMware Tools, etc.)
Ensure VMs are in a clean shutdown state, ready for offline imports
Verify network connectivity between source and KorGrid environment
KorGrid Environment Preparation
Verify sufficient storage capacity within the vSAN
Configure network segments to match source enviroment VLANs
Plan IP address assignments and DNS configurations
Review Guest OS Compatibility
Choosing the Right Method
Use VMware Connector when:
- Source is a production VMware environment
- Need to minimize downtime during migration
- Importing multiple VMs simultaneously
- Source VMs must remain operational during data migration
- Want to leverage VMware CBT for efficient transfers
Use Media Images Import when:
- Migrating from non-VMware platforms (Hyper-V, VirtualBox, KVM, Nutanix)
- Source VMs can be shut down for export
- Working with mixed virtualization environments
- Need maximum control over individual VM imports
Use Clone Utility when:
- Migrating physical machines to virtual (P2V)
- Converting VMs from non-VMware platforms (V2V)
- Need block-level migration efficiency
- Working with individual machines that aren't downtime sensitive
Post-Import Optimization
Install VirtIO Drivers
- Windows - Install Virtio-win guest tools for optimal performance.
- Linux - Most distributions include native VirtIO support.
Network Configuration
- Verify network connectivity and IP assignments
- Update DNS and DHCP reservations as needed
- Test inter-VM communication
Storage Optimization
- Migrate disks to appropriate storage tiers if needed
- Consider enabling disk compression for space efficiency
Security and Monitoring
- Enable QEMU Guest Agent for enhanced monitoring
- Configure backup policies using snapshots
- Update guest OS and applications to latest versions
Best Practices & Tips
Performance Optimization
- Use VirtIO interfaces whenever possible for best performance
- Start with SATA/IDE interfaces if experiencing boot issues, then migrate to VirtIO after driver installation
- Preserve MAC addresses during import to avoid network reconfiguration
Troubleshooting Common Issues
Boot Problems
- Try changing disk interface from VirtIO-SCSI to SATA or IDE
- Install VirtIO drivers, then switch back to VirtIO-SCSI
- Verify EFI/BIOS settings match source VM configuration
Network Issues
- Check if VirtIO network drivers are installed
- Verify VLAN and network segment configurations
- Confirm MAC address preservation settings
Performance Issues
- Ensure VirtIO drivers are installed and updated
- Verify adequate resource allocation (CPU, RAM)
- Consider storage optimizations for disk-intensive workloads