Show
Turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Did you mean:
Options
I am trying to install ESXi v5 in VMware Workstation v8. When the virtual machine is booting, I get a warning message saying: Virtualized Intel VT-x/EPT is disabled for this ESX VM. You will only be able to run 32-bit nested VMs. This
is my computer’s processor: What must I do to make the warning go away? Thanks
34 Replies
Thanks, Jim. I am going to follow the instruction in the links you provided here and will post an update. By the way when i checked my ESXi VMs (Summary Tab) they say vmotion, ECV and Fault Tolerance as N/A. That's how i came to the conclusion that they were not supported unless you have VT-x/EPT. Again it was my pet peeve against Intel where you have to be very careful on the CPUs you buy as against AMD. All AMD CPUs support AMD-V with RVI.
These are among the many reasons that ESXi in a VM is only supported under Workstation "for educational and demonstration purposes only." However, you can get these things to work with some effort.
That's not quite fair. Early AMD64 parts supported neither. Then there were AMD64 parts that only supported AMD-V, but not RVI...and the AMD-V support had a serious design flaw. Only since Barcelona have all AMD64 parts supported AMD-V and RVI. Your Xeon pre-dates Intel support for EPT. Since Nehalem, all Intel CPUs with VT-x support also support EPT. Having said that, it is true that some Intel skus do not have VT-x support at all.
As per jmattson i have to take back some points i wrote earlier. 1. vmotion and storage vmotion works flawlessly even when you have nested ESxi 2. I was uanble to get Fault Tolerance working - My ESXi hosts are in cluster with Vsphere HA enabled - I have a centralized NFS data store which stores fileset of VMs - I received the following message which clearly points to an unsupported CPU 3. I tried to install vcenter server appliance in OVF format and failed. It points to cpu incompatibility as well. All said I can live without Fault Tolerance. Thanks for your help j.
I m also facing the same issue as mention above. I m using Intel Core2Duo processor. I checked in log file EPT is disable for my host. Please see the attached log file suggest. Thanks Manish Thanks Manish Raj
All,
I had this same problem today but it turned out that since all my VM's were created in Vmware workstation 7, HPET wasn't enabled and was the reason for this. So, while most of the comments here provide some of the correct steps to take, dont think any of them include all the steps required (assuming that your nested hypervisor VM's were NOT freshly created in Workstation 8 with the HPET support turned on (if this is on, when you go to settings and select processors, on the bottom right, you'd see 2 check boxes and the one that says "Virtualise Intel VT-x/EPT or AMD-V/RVI" should be available.) So, if you power the VM off, select it in the left hand pane within the workstation, you will see on the right to "Upgrade this virtual machine" select that, select the Hardware compatibility to Workstation 8 to enable HPET, select Alter this VM and when you click next, you'll see the changes to apply include Adding: HPET. Once thats done, go to the settings of the VM (while powered off) and select the processors on the left and make sure the checkbox "Virtualise Intel VT-x/EPT or AMD-V/RVI" is checked. And also make sure the guest OS is selected as ESXi 5 under options. Thats all you need to do. if this is to be done through editing the vmx file. amongst the following is the key hpet0.present = "TRUE" If the VM was freshly created on Workstation 8, this would be there by default (provided that you used the ESXi5 installation CD during the creation time) Hope this makes sense. (& dont forget to award points) ChanEK
Actually, the HPET doesn't have to be present, but the virtual hardware version does have to be 8. New virtual CPU features are typically tied to a new virtual hardware version. In the case of virtualized VT-x/EPT or AMD-V/RVI, we didn't quite make the cut-off for virtual hardware version 8, which first appeared in ESXi 5.0, but we decided to release the feature in Workstation 8 anyway. That's what the warning is about. Future products will probably tie virtualized VT-x/EPT or AMD-V/RVI to hardware version 9. (It is possible that hardware version 8 VMs with the feature will be grandfathered in, but you won't be able to add the feature to a hardware version 8 VM that doesn't already have it.)
Hello everyone, I have a question similar to the original post. Sorry I am am unclear on some virtualization concepts so I will try to be as clear as I can with my case. I wanted to evaluate vCenter and I setup a vmware environment on my laptop in order to play around with vCenter and spin out some test VMs using an ESXi5 host as a datastore for this vCenter On my physical laptop (Dell latitude e6500 - in the BIOS, virtualization is enabled on this physical laptop), I am running VM Workstation 8 I am running 2 VMs, 1st is a Win2008 R2 x64 server with the vCenter client and vCenter server installed. The 2nd is a ESXi5 hypervisor (host/datastore). When I try to spin out a new 64 bit VM (nested VM) in the vCenter client, and then power it on, I get the following error:
on the ESXi host/datastore for the vCenter (virtual), I have VT-x/EPT enabled:
I tried to check the BIOS of the ESXi, but there are no options to enable the virtualization
I also updated the /etc/vmware/config (on the ESXi server) to set the vhv values to TRUE
but running the esxcfg-info| grep "HV Support" I am getting a '0'
So what I am unclear about is 1) how do I enable virtualization on teh ESXi 5 host, when after checking of the VM > Settings > Processors > enable Virtualize Intel VT-x.. and updating the config file I am still getting a '0' for HV Support and 2) should I enable any other setting on the vCenter server (win2008 R2 x64), or is this related to the ESXi server only? I am not sure where the error to run the 64bit VMs is coming from, is it only from the ESXi host or is it also from the vCenter server? I hope I explained this clearly.. Thanks!
I had a lot of trouble runing 64 bit VMs on with Workstation 7 installed Server 2008 R2 some time ago. Initially I bought a 1st Gen Core i5. Then I found out I needed both a CPU and Motherbaord/Chipset that supported Intel VT-d to run 64bit VMs. A New CPU and carefully selected motherboard later all was fine! I'm now running workstation 8 and looking to upgrade my host machines and landed on this thread looking for info on VT-x/EPT.
There's also a page on Intel Motehrbaords listing INTEL Desktop motherbaords/Chipsets that are compatible with VT and VT-d. http://www.intel.com/support/motherboards/desktop/sb/CS-030922.htm I can't seem to find anything similar for VT-x/EPT. This may now be included under the Intel "VT" umbrella.... but I'm not sure. But my tip for folks is the CPU feature support is only part of the puzzle. Both your Chipset AND BIOS needs to support the Intel virtualisation features and it can be very tricky trying to find out before you buy!
Actually, Workstation makes no use of VT-d.
Unfortunately, this web site is notoriously wrong about which CPUs have EPT support. Currently, only the "products formerly" Nehalem, Westmere, Sandy Bridge and Ivy Bridge have EPT support.
The Xeon X3220 does not support EPT. It was released well before EPT was available.
There is no official confirmation, but you can either read the MSRs yourself or trust the dump of the MSRs in the vmware.log file, where they are decoded for human readability. You are looking for the line that says: Enable EPT { 0 } or Enable EPT {0,1} The latter implies EPT support; the former does not. You can still install ESXi under Workstation 9, but you will only be able to run 32-bit nested VMs using binary translation.
Which of the following are the essential system requirements to enable nested virtualization on HyperWhich of the following are the essential system requirements to enable nested virtualization on Hyper-V? [Choose all that apply]. The Configuration Version of the guest virtual machine must be 8.0, Hyper-V feature must be installed, & Windows Server 2016 Data Center must be the operating system on the Hyper-V host.
Which of the following must be true if Theodore did not use the Sudo command during the second round of administrative changes?Which of the following must be true if Theodore did not use the sudo command during the second round of administrative changes? Theodore used the sudo passwd root command.
What is the advantage of using production checkpoints over standard checkpoints?One benefit for Production checkpoints is that they are smaller for running virtual machines than Standard checkpoints. Production virtual machines don't need memory state, so they don't save a copy of it.
What is the use of the new ADReplicationSite Windows PowerShell cmdlet quizlet?What is the use of the New-ADReplicationSite Windows PowerShell cmdlet? It can be used to create a new site object.
|