Become a fan of Slashdot on Facebook


Forgot your password?
AMD Hardware

AMD Demos Live Migration Across Three Opterons 25

bigwophh writes "Advanced Micro Devices has just revealed to the public the first video and images demonstrating live migration across three generations of AMD Opteron processors on VMware ESX 3.5, including the six-core AMD Opteron processor, often referred to as 'Istanbul.' For those unaware of the strains in a server environment, live migration of virtual machines across physical servers is crucial to providing flexibility for managing data centers. AMD is also taking this opportunity to highlight its continued, cooperative development efforts with Microsoft as evidenced in Windows Server 2008 R2 Hyper-V, which just also happens to be available today in beta form, that adds support for AMD-V technology with Rapid Virtualization Indexing."
This discussion has been archived. No new comments can be posted.

AMD Demos Live Migration Across Three Opterons

Comments Filter:
  • Yay? (Score:4, Interesting)

    by eln ( 21727 ) on Wednesday March 25, 2009 @04:11PM (#27334505)

    They can call me when they've demonstrated seamless live migration between Intel and AMD chips, not just generations of their own hardware. Nobody wants to build a large-scale cloud if they're going to be locked to one vendor forever once they get started.

  • Re:Nothing new? (Score:2, Interesting)

    by Anonymous Coward on Wednesday March 25, 2009 @04:36PM (#27334813)

    No, the CPU features (the CPUID bits) are masked out with ESX, your can fine-tune this in the settings of every VM.

  • by Chris Burke ( 6130 ) on Wednesday March 25, 2009 @05:21PM (#27335353) Homepage

    I was curious how they migrate active network connections though. Does the old host act as a proxy/router? Can anyone shed some light?

    Its been around 9 years since I did the project in college, but it is possible to transfer active network connection state from one computer to another. It was a "connection-aware seamless backup server", where our hacked linux kernels would exchange state about an active TCP/IP connection at regular intervals, and when the primary dropped (in our demo we yanked the ethernet cable out of the hub in the middle of streaming an mp3), the other would take over, pretending to be the same IP and picking up where the other left off. The best part was that TCP/IP already deals with redundant, missing, or out of order packets so anything sent or received since the last update to the backup would be handled automagically.

    That was just as stupid semester project on a 3-computer ethernet LAN, but I imagine the big boys have figured out how to make it work. Besides, they're literally transfering the memory image of the guest OS over to the other machine so all the state update is already done. The hard part is probably making the IP migrate along with, but I'm sure they've figured that out too.

  • by cowbutt ( 21077 ) on Wednesday March 25, 2009 @06:18PM (#27335943) Journal

    That was just as stupid semester project on a 3-computer ethernet LAN, but I imagine the big boys have figured out how to make it work

    Checkpoint's Firewall-1 product has been able to transfer the current firewall state to a backup firewall for quite some time (at least 1998 or so), but it originally required the use of RIP to implement failover which introduced delays. In about 1999, Stonesoft produced an add-on product, Stonebeat, which added ARP spoofing, so the failover was virtually instantaneous. These days, the failover is done using VSRP.

MESSAGE ACKNOWLEDGED -- The Pershing II missiles have been launched.