Skip to main content

AMD pushes Virtualization vendors to broaden migration and interoperability


To loosen the live-migration constraints, Sunnyvale, Calif.-based AMD released a white paper disclosing details about AMD-V Extended Migration, a feature dating back to the first-generation Opteron processor that enables virtual machines to migrate between different versions of AMD processors.
The need for migration ease
"Our customers are very interested in doing live migration because of the flexibility it provides," said Margaret Lewis, director of commercial solutions at AMD. "[AMD-V Extended Migration] is where the rubber meets the road. We've made this interface on the hardware end, but it is up to software to implement it."

AMD-V Extended Migration masks the differences between CPU generations, facilitating the safe live migration of virtual machines between servers running different generations of AMD processors. This includes existing single- and dual-core processors and all future AMD processor revisions, including the upcoming Barcelona quad-core AMD Opteron processor that is expected to be released Sept. 10.
This is really a good thing, we are moving (rather) fast to a phase where the hardware vendors like Intel and AMD will be standing long before at the finish line with array of solutions for virtualization vendors. Some like VMware, with an obvious lead are already working hard to stay and keep up the pace with the hardware vendors, others have to wuickly adapt to the change ecosystem and develop their products accordingly. Either ways, customers and end-users will have loads of choice.

And you know how comfortable the consumers are with "loads of choices", right? Anyways here's the coverage. Take a look at the whitepaper too!
Labels:

Comments

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus
Post a Comment
Read more

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op
Post a Comment
Read more