Compatibility issues using VMWare on AMD based processors

Posted on 2009-12-17
Last Modified: 2013-12-10
Hello Experts

I have heard that VMWare does not work properly on AMD based processors than on Intel based processors. Can anyone validate this rummer? Does anyone has AMD processor PC and running VMWare experienced any problems?
Question by:marmoor99
    LVL 3

    Accepted Solution

    I never heard of this before. It is known that there was a bug with the latest generation of cpu's. But it was for both companies and is solved with the latest patches.
    LVL 69

    Assisted Solution

    If that were true, AMD would not be in the server business.  AMD calls their virtualization support AMD-V, while Intel calls theirs VT-x:  Not all processors from both companies have this support.

    You can read about VMWare usage from the community:;jsessionid=FB8305577EBC84ED54F51F2B5F00EA7B
    LVL 42

    Assisted Solution

    VMWare works well on Intel and AMD processors.  In fact some customers prefer AMD processors with AMD-V since it does not require and modifications on the BIOS to turn on as required by Intel VT technology.
    LVL 40

    Assisted Solution

    Agree as above. Here is VMware's CPU compatibility matrix which covers both Intel AND AMD:  

    LVL 32

    Assisted Solution

    I currently use an AMDx2 processor in my lab and it runs great.
    LVL 21

    Assisted Solution

    AMD is not incompatible. It works. Though currently, from an operational point of view though it makes sense to stick to a specific CPU vendor.
    It makes building and configuring ESX clusters (with DRS/HA/vMotion) much easier. If you do decide to have servers with a mix of both Intel and AMD chips, you would need to build two seperate ESX clusters for each CPU vendor  as vMotion/DRS/HA/FT does not work across them.
    What I mean is if you have a guest running on an ESX server with AMD processors, you will not be able to vMotion it off to a server running Intel chips - while the VM is running and vice versa. The only way to do that would be to power off the VM and then vMotion it. So that could be the incompatibilty you talking about ... but thats just an operational thing at the moment. Both Intel, AMD and VMware are working to see if they can get rid of this issue.

    Featured Post

    Looking for New Ways to Advertise?

    Engage with tech pros in our community with native advertising, as a Vendor Expert, and more.

    Join & Write a Comment

    In this article, I am going to expose some of the hidden, undocumented, unsupported features and functions of the VMware vSphere Hypervisor (ESXi). VMware vSphere ESXi 4.x, and ESXi 5.0 does not officially support Raw Disk Mapping of Local Stora…
    I have purchased two new systems and both are now Universal Extensible Firmware Interface (UEFI) based. UEFI is replacing BIOS for the desktop PC. It is a Linux based firmware with enough robustness it can communicate with a website without loading …
    Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
    This video shows you how to use a vSphere client to connect to your ESX host as the root user. Demonstrates the basic connection of bypassing certification set up. Demonstrates how to access the traditional view to begin managing your virtual mac…

    745 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    16 Experts available now in Live!

    Get 1:1 Help Now