Processor architecture influences workload mobility in VMware® environments and the operational flexibility available to infrastructure teams. Testing by Prowess Consulting found that VMware® vMotion® remained available between current and legacy Intel® Xeon® processor–based servers when VMware Enhanced vMotion Compatibility (EVC) was configured appropriately, allowing live virtual machine (VM) migration with no downtime. By contrast, migrating workloads between Intel processor-based servers and AMD EPYC™ processor–based servers required cold migration, resulting in 2 minutes 31 seconds of downtime with shared storage and 7 minutes 37 seconds with direct-attached storage (DAS). The study argues that mixed-vendor CPU environments effectively create separate migration domains, increasing outage planning and operational complexity. It also evaluates encrypted vMotion and finds that Intel® QuickAssist Technology (Intel® QAT) can reduce encryption overhead while keeping migration times close to those of unencrypted migration. Organizations can preserve workload mobility, simplify infrastructure refresh planning, and reduce operational disruption by maintaining processor consistency while using Intel QAT to support security-focused migration strategies.
TL;DR
Workload mobility in VMware environments depends on processor architecture. Prowess Consulting found that a consistent Intel processor architecture enables VMware vMotion across current and legacy Intel Xeon processor–based servers with no observed application downtime when VMware Enhanced vMotion Compatibility (EVC) is configured appropriately. By contrast, moving workloads between Intel-based servers and AMD EPYC processor–based servers requires cold migration, resulting in up to 2 minutes 31 seconds of downtime with shared storage and up to 7 minutes 37 seconds with DAS. The testing also showed that Intel QAT can reduce encrypted vMotion overhead, allowing encrypted migration to remain close to unencrypted migration performance while helping reduce CPU demand during encryption processing. The research concludes that processor consistency helps preserve workload mobility, reduce operational disruption, and simplify infrastructure refresh and expansion planning.
Evidence: See Executive Summary, Tables 1–3, “What the Results Mean for Your Organization,” and Conclusion.
FAQ
Q: Who is this paper for?
A: This paper is intended for IT infrastructure leaders, virtualization administrators, data center operations teams, cloud architects, security and compliance stakeholders, and procurement or strategy teams evaluating processor architecture decisions, workload mobility, infrastructure refresh planning, and virtualization platform consistency.
Q: What is the main conclusion of the study?
A: The study concludes that workload mobility depends on processor architecture. Intel-based environments support VMware vMotion across current and legacy Intel Xeon processor–based servers when VMware EVC is configured appropriately. Moving workloads between Intel- and AMD-based systems requires cold migration, introducing downtime and additional operational complexity.
Q: How much downtime occurred during Intel-to-AMD migration?
A: Intel-to-AMD migration requires cold migration. Testing measured 2 minutes 31 seconds of downtime when shared storage was used and 7 minutes 37 seconds when compute-and-storage migration used DAS. These outages occurred because vMotion is not supported across vendor architectures.
Q: How did Intel QAT affect encrypted migration?
A: Intel QAT encryption reduced encrypted migration times compared with software encryption. Compute-only encrypted migration improved from 8 seconds to 7 seconds, while compute-and-storage migration improved from 4 minutes 37 seconds to 3 minutes 55 seconds, reducing encryption overhead substantially.
Q: Why does processor consistency matter for virtualization operations?
A: Consistent processor architecture helps maintain workload mobility, reduces maintenance-related disruption, minimizes outage planning, and avoids creating separate migration domains. This allows organizations to refresh hardware, rebalance capacity, and perform routine infrastructure changes with less operational complexity.
Q: What business impact can mixed-vendor CPU environments create?
A: Mixed-vendor environments can split infrastructure into separate mobility domains. Although workloads can still move, each migration might require outage scheduling, approvals, coordination, and recovery planning. As VM counts increase, these operational burdens can accumulate and affect infrastructure flexibility.
Q: What role did VMware Enhanced vMotion Compatibility (EVC) play in the testing?
A: VMware EVC enables live migration between legacy and current Intel Xeon processor–based servers by presenting a compatible CPU feature baseline across hosts. In the testing, EVC allowed workloads to move between different Intel processor generations without application downtime, helping preserve workload mobility during hardware refresh and expansion projects.
Q: Why is workload mobility important in a VMware environment?
A: Workload mobility affects how organizations perform maintenance, expand capacity, refresh hardware, and rebalance workloads across infrastructure. Live migration helps administrators move virtual machines without interrupting applications, while cold migration introduces downtime and additional operational planning. The study finds that processor architecture directly influences which migration model is available.
