VMware customers are getting a bit more freedom in the way they can transfer virtual machines from one Intel-based server to another, but they shouldn't hold their breath waiting for a bridge between Intel and AMD-based systems, an Intel executive said Tuesday.

With its line of Xeon 7400 processors released this week, Intel is enabling customers using VMware's vMotion technology to move virtual machines between two servers even when they are based on different families of Intel chips.

VMotion is VMware's technology for moving running virtual machines onto a different physical server. It's used by some customers for load balancing or for building fault tolerance into applications.

Before the 7400 series, also known as Dunnington, the two servers had to use the same family of Intel chips for vMotion to work, said Doug Fisher, vice president with Intel's Software Solutions group, at the VMworld conference in Las Vegas. With the 7400 and future chip families, that restriction is lifted.

VMware CEO Paul Maritz mentioned the development in his speech at the start of VMworld Tuesday. "Now you'll be able to buy hardware essentially independent of your vMotion strategy," he said.

The compatibility goes back only to the previous processor family, the 7300 "Tigerton" series, and will extend to the next generation, known as Nehalem. "We'll always give at least three generations of compatibility," Fisher said.

Intel made a big deal about the news, but AMD said its Opteron processors have had a similar capability for years. AMD doesn't change the microarchitecture of its processors as frequently as Intel, so compatibility between different Opteron lines is not an issue, said Margaret Lewis, AMD director of commercial solutions.

Customers looking to move virtual workloads between AMD- and Intel-based servers are out of luck, however, at least for the foreseeable future, according to Fisher.

"It's not going to happen," he said on the sidelines after his speech. The companies' chip architectures, while both x86, are too different and change too frequently to be made compatible. "We'd have to slow the pace of innovation to make it happen," he said.

Lewis suggested it was only Intel, not AMD, that changes its architecture frequently. "We'd need to sit down with Intel and VMware and discuss how to make it happen, and we would welcome that discussion," she said.

The IDG News Service is a Network World affiliate.