Vmware unsupported cpu detected ошибка
VMware vSphere 7.0 and ESXi 7.0 raised the requirements when it comes to CPU and CPU compatibility. As with any major version of ESXi, there are new CPUs that are supported as well as old CPUs that are reaching the end of support.
Vladan Seget is an independent consultant, professional blogger, vExpert 2009-2021, VCAP-DCA/DCD and MCSA. He has been working for over 20 years as a system engineer.
- How to use VMware vSAN ReadyNode Configurator - Fri, Dec 17 2021
- VMware Tanzu Kubernetes Toolkit version 1.3 new features - Fri, Dec 10 2021
- Disaster recovery strategies for vCenter Server appliance VM - Fri, Nov 26 2021
This basically means that if you have an older system that has an older CPU, you should check whether this system will be supported with ESXi 7.0. Today's article is focused on vSphere 7.0 and unsupported CPUs.
Before upgrading your ESXi to 7.0, you have to upgrade your vCenter Server. Here is our detailed article: How to Upgrade to vCenter 7.0
When you try to install ESXi 7.0 on a server with an unsupported CPU, you'll see a message like this.
VMware ESXi unsupported CPU message
However, there is also a workaround that allows you to bypass the ESXi unsupported CPU check. We'll talk about this later because the workaround is unsupported by VMware.
ESXi 7.0 hardware requirements ^
- CPU details: VMware ESXi0 basically needs a CPU with at least two CPU cores, which is the majority of CPUs today.
- BIOS Settings: NX/XD bit to be enabled for the CPU in the BIOS.
- 4 Gb of RAM: This is the bare minimum, but as virtualization needs memory for your VMs, the more you have, the better.
- Modern Guest OS: If you want to run 64-bit VMs, you'll need support for Intel VT-x or AMD RVI, which must be enabled on x64 CPUs within the BIOS.
- Boot Device: 8 GB for USB or SD devices, and 32 GB for other device types such as HDD, SSD, or NVMe.
- Storage: SCSI, SATA via supported storage controller.
Note: Due to changes in the partitioning scheme, you can no longer revert to the previous version of ESXi (via SHIFT-R). This was always the case with VMware ESXi; however, now, you'd have to create a backup of the boot device before the upgrade.
Subscribe to 4sysops newsletter!
ESXi 7.0 unsupported CPUs ^
There are two family models that are no longer compatible and won't work under ESXi 7.0. Those CPUs were basically made during the 2010 era, so it's about time for them to retire.
- Intel Family 6, Model = 2C (Westmere-EP)
- Intel Family 6, Model = 2F (Westmere-EX)
The Westmere-EP architecture was based on two- to six-core CPUs, while Westmere-EX was a ten-core CPU model. This was Intel's CPU architecture right after Nehalem (my first lab). It was about 10 years ago, yes.
Now you might wonder how to easily check whether the CPU is compatible and supported or not.
Workarounds ^
Are there workarounds? Yes, of course. The first is advice to someone who is looking to run VMware virtualization software on older hardware. If your hardware is 4–5 years old, you might hit the limit of compatibility (or you will soon), but for now, you should still be able to run ESXi 7.0.
If your system is not listed on the VMware compatibility page, you can still run your ESXi 7.0 on it, but don't expect Support to help you out if you hit some hard problem.
You can still run some less critical production workloads or your company monitoring solution on that hardware, but most likely, you'd want to sell this hardware and purchase newer equipment.
If you still want to run an ESXi 7.0 and you know that your CPU is not supported and your installation gets you to the page with an error message, there is a solution.
Disclaimer: Note that I have not personally tested this solution as I don't have an old CPU to perform the tests. The solution was described in VMware forums and on a few blogs. So, take it or leave it.
You'll have to be directly at the server console or remotely via ILO, DRAC, or IPMI. When you run the installer, use this shortcut:
Shift + O
(Note: this is the letter "O," not the zero "0").
Enter Shift plus O
That changes the screen to the one below and allows you to enter a special parameter that enables you to bypass the validation during the installation/upgrade.
Allow Legacy CPU value
Remember that this is not supported by VMware.
Note that the parameter you entered to bypass the installer will be lost after reboot. If you want to keep this value, you have to edit the boot.cfg file, which is located on the media you're booting from. You may be booting from a local SATA drive, USB stick, or other media, so it depends on your configuration.
Basically, you have to edit the boot.cfg file located in two places on the boot media. You can find this file in /bootbank/boot.cfg and in /altbootbank/boot.cfg.
There is a "kernelopt" section where you can append this parameter.
Allow Legacy CPU via SSH
This is not advice to proceed or not to proceed. It's a tip, and you can use it if you want. Personally, as I said, I would not use it to "force" a run on a production system, but this can be a perfect fit on test or home lab systems that still work and that can be used for learning or running test scenarios.
Check the CPU model in the VMware Compatibility Guide ^
You can check the CPU by going to the compatibility page at VMware.
From the list selection, you can select the ESXi model and CPU series. Then hit the Update and View Results button.
Select ESXi 7.0 and your CPU model
The page will refresh and show you the results of the server model with the CPU and supported ESXi 7.0 version.
If you don't see any results, your CPU is not supported. Try with a newer CPU if you think you're having issues.
Server device and model information
Conclusion ^
As you can see, checking the hardware for compatibility on the VMware site isn't difficult. It might also be interesting to check for network interface cards (NICs), as with ESXi 7.0, many legacy Linux drivers have been phased out. As those drivers were necessary to run, for example, many Realtek-based NICs, it seems those will no longer work under ESXi 7.0. But you can still upgrade your NICs to supported ones or seek another workaround if there is one. Good luck.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- VMware Technology Network
- :
- Desktop Hypervisor
- :
- VMware Workstation
- :
- VMware Workstation Pro Discussions
- :
- unsuported cpu detected
Douhal32
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
HI I just downloaded VMware workstation and to upgraded it and I pop-up window came up and said unsupported CPU detected. Is there any solution to fixing this problem
daphnissov
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Yes, upgrade your CPU or downgrade the version of VMware Workstation.
scott28tt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Moderator: Please post questions into the appropriate product area when possible, thread moved to Workstation Pro.
Although I am a VMware employee I contribute to VMTN voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
daphnissov's answer is the only one possible.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
To add a bit of background info to what the others already have said.
Starting with VMware Workstation 14 additional CPU requirements are needed.
At the time when Workstation 14 came out the installer would not test for that and it confused a lot of people.
Especially as you cannot check for this feature on the Intel technical specification page about their CPUs.
The current Workstation installer however gives you a timely error, the one you saw. So at least you don't end up burning a lot of time.
While "upgrade your CPU" sounds nice, normally you can't upgrade the CPU of your machine to one that will work, without replacing the machine, as intel does not keep their CPU sockets compatible between CPU revisions. So it is more a "upgrade your computer" kind of thing.
An alternative approach is to install either an older VMware Workstation product (Workstation 12 or older) or another virtualisation product that does not have these requirements.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- VMware Technology Network
- :
- Desktop Hypervisor
- :
- VMware Workstation
- :
- VMware Workstation Pro Discussions
- :
- VMware Workstation Pro 14 - Fails To Start Due To .
jvenuto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Just installed VMware Workstation Pro 14. It fails to start guest (either 32 or 64 bit Kali distro). Attempted on Windows 10 Enterprise and Ubunutu 17.04.
No prior issues with same using any prior version.
Pop Up Box Error:
This host does not support "Intel EPT" hardware assisted MMU virtualization.
This host does not support virtualizing real mode. The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor.
Module 'CPUIDEarly' power on failed.
Failed to start the virtual machine.
TracyHuang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Thanks for the posting!
What's your CPU type?
It seems the issue is due to your OLD CPU. Some old CPUs are deprecated in Workstation 14, System Requirements of Workstation 14 can be found in releasenotes -- VMware Workstation 14 Pro Release Notes
jvenuto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Processor: Intel Xeon X5460
wice22
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Same issue here
Intel Xeon CPU W3530
so going back to old version .
gnietom
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Edit: found it. Add monitor.allowLegacyCPU = "true" to the config ini
Over: C:\ProgramData\VMware\VMware Workstation
VM_Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
This doesn't work: Add monitor.allowLegacyCPU = "true"
continuum
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Hi
I found the tweak
more or less accidentaly by looking at the WS-binaries. It helped for my XEON cpu but may not help with other types.
Watch this post
@VMware Workstation Product manager : please publish the necessary vmx-file hacks that are required .
If a lot of folks complain we may be able to persuade the engineers to publish better hacks.
Ulli
________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time .
corsafr
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I have the same issue on my laptop.
I test Workstation 14 but I think I will not buy this version.
I don't understand why Workstation 14 requires only new CPU.
No workarround for it ?
No patch from VMware to solve it ?
busdriver99
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I have the same problem. Downloaded Version 12 Demoversion and everything what I wanted to do worked perfectly!
So I bought VMware Workstation but in the meantime Version 14 was out and I received Version 14. But now I get this error and the here suggested workaround doesn't work.
I don't want to replace my computer :smileyangry:
I hope for a solution!
drueter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Same problem here.
Add monitor.allowLegacyCPU = "true" in C:\ProgramData\VMware\VMware Workstation\config.ini DID "work" in that it bypassed the error, but the VM's would not start (no error, but just painfully slow through POST. never made it to boot).
I do intensive software development and data processing, all day, every day, and most of that in multiple VM's running concurrently in VM Workstation 12. My hardware keeps up just fine.
Workstation 14 really should have a switch to allow it to run like Workstation 12 without using EPT if it is not available. Ditching stable useful hardware doesn't seem worthwhile, when the performance gains from EPT may not contribute much to overall performance experienced by users.
I uninstalled Workstation 14, and re-installed Workstation 12. and now I am back in business.
Intel Core i7 920 @ 2.67 GHz / 18 GB RAM, Windows 10 x64 host.
Wanderer0123
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
This is insane! What kind of a bonehead move is this. I have a Core i7 and now cant run this software? Seriously? Did a group of you actually sit down and discuss this and say "This is a great idea".
Clive_Thorne
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I have just encountered this myself. Was really looking forward to having USB3 support at last,
This just defies comprehension because the VmWare team/management have really shot themslves in the foot with this one. The fix in the config file 'works', but as someone said makes it ridiculously slow to boot (over 2 minutes). Someone at VMware should be loosing their job over this.
I shall be reverting to V12 and recommending anyone I know not to touch V14.
Are you listening VMware people?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Was really looking forward to having USB3 support at last,
What do you mean?
USB3 support for a Windows 7 guest OS perhaps?
If so then that is available on Workstation 12, but you have to install a driver from intel and I don't think that has changed for Workstation 14.
More modern OS's should have USB3 support out of the box already when using Workstation 12.x,
Clive_Thorne
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Yes that's exactly what I meant, so thanks for pointing out that it can already be done. Fortunately my laptop also has USB 2 ports.
I am only a 'casual' VMware user and had assumed that because because WIn 7 supports USB3 on the native PC (it does on mine at least) that the problem lay with the VMware.
Even less reason to move to V14 now!
Just followed that link that you gave me and the instructions say to chnage the USB compatibility in the VM settings to 3.0. However my VM only shows options for 1.1 and 2.0. Perhaps this is where I originally got the idea that 3.0 wasn't supported.
Note that this particular VM originates from Vmware V6.5 - would that have anything to do with it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Note that this particular VM originates from Vmware V6.5 - would that have anything to do with it?
Yes, most likely. In order to take advantage of newer features of Workstation, the virtual hardware of the VM must be 'upgraded' to a newer version. If it is still on Workstation 6.5x compatibility, then it will not have access to any features added since then. You can upgrade the virtual hardware in the VM - with the guest powered off, open the VM settings, and you should be able to modify the version compatibility. I forget the exact setting/location.
SirWobbyTheFirs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I've got the same issue, I had the issue during the Tech Preview (Hi Continuum) where my quad-core i7 950 isn't able to be used with Workstation 14, I figured at the time, it was an issue with the tech preview and simply uninstalled and went back to 12. I did try Continuum's idea of adding the monitor.allowLegacyCPU = "TRUE" entry to the VMware config file and found that whilst UEFI based virtual machines would boot, BIOS-based machines wouldn't, in addition, the POST and overall operation of the virtual machine would be tremendously sluggish, I figured it was a beta thing so I uninstalled and went back to 12.
Today, however, I've installed Workstation 14 because I wanted to skip having to manually add the extra entries to the VMX file for the VCSA and upon booting up a UEFI based Windows DNS and DHCP Server that works fine in Workstation 12, I am greeted with the "VMX Unrestricted Guest" error message, I enabled the monitor.allowLegacyCPU = "TRUE" entry to the VMware config file again and tried booting my VM and whilst it starts, again the UEFI POST is sluggish, for curiosity sake, I started up a BIOS-based pfSense virtual machine AND! it took 3 minutes to display the VMware logo during post, going into the BIOS setup, I watched as the screen was drawn line by line incredibly slowly like 1 line per second.
And it continued like that navigating through the BIOS setup menus, going to boot pfSense up, the boot menu that pfSense shows prior to startup was again drawn on screen 1 line per second until the point where it was supposed to display the text for choosing whether I wanted to boot up in Multi-User or Single-User at which point it stopped booting altogether. And again for curiosity sake, I created a fresh pair of VMs, one set to boot up using BIOS and the other set to boot using UEFI, both took incredibly long to progress through their POST and whilst the UEFI machine continued to boot up Windows Server 2012 R2 Setup, the BIOS stalled prior to when the Windows Boot Logo would show up.
VMware, to say you have fluxed up hella bad, is an understatement, the way I see it, if my CPU is good enough to run Windows 10's latest iteration as well as Hyper-V standalone and VirtualBox on an Ubuntu Server installation, then it is clearly good enough to run Workstation.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- VMware Technology Network
- :
- Desktop Hypervisor
- :
- VMware Workstation
- :
- VMware Workstation Pro Discussions
- :
- Version 14.1.2 - unsupported CPU detected on a Del.
rileyb76
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Guys,
We have some brand new Dell Precision 5820's that we're trying to load 14.1.2 on but we keep getting this error. Our host OS is RHEL 7.5.
Is there a workaround? Thanks
bluefirestorm
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
It looks like Precision 5820 uses the Skylake-W Xeon CPU.
Does clicking on "Ignore" not let you proceed to install?
My guess is this current version installation checks for CPU family/model/stepping. With the 14.0.0, PCs with unsupported Intel CPUs (CPUs from Nehalem generation or older) which did not have the VMX unrestricted guest feature, could install but not able to power up any VM. You could try downloading an earlier 14.x version such as the original 14.0.0 if clicking on ignore does not let you proceed. And then do an update to 14.1.2 after the install.
As for actual issues you might face if indeed the Skylake-W family/model/stepping is not recognised by Workstation 14.1.2, a telltale sign is the codename in the vmware.log will likely appear as Pentium (for Intel CPUs).
vmx| I125: hostCPUID codename: Pentium Core -- Unknown codename
If any of your VMs require virtualised performance counters to be enabled it will fail to power up. I have seen this with Workstation 12.5.x and Fusion 8.x encountering this problem with Kaby Lake CPUs. Another problem spotted is Oracle Enterprise Linux VM fails to boot as it tries to load DTrace modules (presumably somewhat related to the virtualised performance counters) and the DTrace module had to be uninstalled from the VM.
But other than this, in general, it appears the host CPU capabilities looks to be are recognised/identified (e.g. AVX2 instruction set) and initialised (e.g. EPT) by Workstation properly.
If you are able to run a VM on this Precision 5820, it will be interesting to see if it Workstation 14.1.2 identifies the AVX512 instruction set. But I think in general, instruction set does not require special setup by the hypervisor to be exposed to the VM; unlike advanced virtualisation features like EPT, unrestricted guest, virtualised performance counters requires extra work on the part of the hypervisor.
I have Intel CPU i7 930. I tried to install VMWare workstation pro 15 and it said " Unsupported CPU detected." and I couldn't install it.
How can I fix this problem without buying new cpu? Is there a work around ?
Your help will be much appreciated.
That's a really old chip, and most likely doesn't have the necessary VTX-d extensions.
You can check the normal things like enabling virtualization in your BIOS and verifying VTX or VTX-d are enabled, but past that it may be time to put that one out to pasture.
That CPU is a Nehalem based chip and will not work with esxi 6.7 you can use esxi 6.5. The only compatable LGA 1366 chips are the Gulftown / Westmere-EP. I upgraded my i7 920 to a Xeon X5680 from eBay for cheap and it works great in my LGA 1366 motherboard.
Edit: My bad i didn't read you're using Workstation
I have VMware station pro 12 but performance is slow. That's the reason I want to use VMwork station pro 15.
Can some tech person guide me work around this issue or solve the problem please?
To solve the problem you will need a new CPU or stay on version 12
Realistically, I think you need a newer computer. That's a 10 year old processor.
Well yeah, you have a pretty old CPU at this point. If you're not using an SSD already, you can try that. The extra IOPS will help a little.
Upgrade your underlying storage that you store the VMDK files on. I have Workstation 12 on an old i7-860 desktop, but the VMs are running against NVMe storage. Host has 16GB of RAM, VMs get 2-4GB depending.
Otherwise, you need a new system.
This community caters to VMware professionals using VMware products in enterprise computing environments. Posts regarding hobbyist and personal use are welcome, but are held to a high standard of quality. Always read the rules before posting. PLEASE state the product name and version when posting! VMware is a company, not a product!
Читайте также: