Mastering Business Migration to Virtualized Environments: Strategies and Tips

Introduction

This article, compiled from the "Efficient Operations" series, presents the author’s long‑term virtualization project experience and focuses on how to migrate existing services to a virtualized environment.

Guest Introduction

Xiao Li , senior KVM expert with 15 years of operations experience, currently a system operations manager at Kingsoft West Mountain Residence, previously at Shanda Games, and author of "Deep Practice KVM".

Column Overview

The column emphasizes practical lessons from extensive virtualization projects and details how to transition business workloads into a virtualized setting.

Main Content

The migration is divided into four parts:

Virtualization project implementation method and business pressure model construction: experience and process of virtualization projects, how to build a business pressure model, and how to select hardware/software based on that model.

Virtualization technology selection and practice: hands‑on experience with KVM virtualization.

Monitoring, alarm, emergency response, and disaster‑recovery methods for virtualization projects.

Business migration to public cloud: public‑cloud selection and migration methods, treating cloud migration as another form of business virtualization.

Below are key considerations when starting a virtualization project:

Which specific service to begin with?

How to select hardware and software?

How to determine the technical solution?

What to do if problems arise?

How to ensure service stability during migration?

Virtualization ultimately brings two major benefits to enterprises:

Cost savings

Rapid deployment

(1) Cost Savings

Example: a game previously running on 500+ physical servers was consolidated into 70+ host machines using a 1:7 virtualization ratio, dramatically reducing costs and restoring profitability.

(2) Rapid Deployment

Creating a new virtual machine is essentially copying an image file, which takes minutes, whereas provisioning a physical server can take over an hour.

Persuading Management

Two tactics: "painting the cake" (showing tangible cost‑benefit numbers) and "digging a pit" (preparing contingency plans for potential issues). Demonstrating that a 1:2 virtualization ratio could cut server count by 50% helps secure executive support.

Persuading Colleagues

Showcase a stable, successful pilot on the virtualization platform to win peer backing.

Choosing the First Virtualization Project

Ideal candidates share these characteristics:

Single‑process workloads that can be consolidated on multi‑core CPUs.

Consistently low CPU utilization (often below 20%).

Frequently changing services that benefit from rapid provisioning.

Non‑core services, to minimize risk during the initial rollout.

Conversely, workloads with extremely high pressure (CPU utilization above 80% on physical machines) are not suitable for virtualization.

(Excerpt from the book "Deep Practice KVM")