Hi
sorry for my english i'm italian.
I have free vsphere 4 on intel server motheboard S500psl with 2 processor ( E5345
SL9YL) and from specific of processor have
Intel® EM64T
(http://processorfinder.intel.com/details.aspx?sSpec=SL9YL)
why can't install virtual machine 2008 r2? windows tell me i haven't 64 bit processor.
bye
It is possible that your BIOS is buggy. Who is your system vendor?
If you get a chance, can you please boot from the ISO attached to this document: . The results may be enlightening.
i Have Intel S5000PSL with last bios
!file:///C:/Users/silviod/AppData/Local/Temp/moz-screenshot-4.png!this is the report of the iso
problem??
You need to boot the physical machine from that ISO image. It does not work in a VM.
Are you installing ESX 4 on the physical machine, or are you installing it in a VM?
"You need to boot the physical machine from that ISO image. It does not
work in a VM."
I newer run 64bit vm on host? why if is compatible?can forse it?
ESX4 run direct install on host.
The vt.iso image will not work in a VM because we do not virtualize VT-x. It needs to run on the physical CPU to determine whether or not VT is enabled on the host. Please burn vt.iso to a CD and use it to boot the physical machine.
I solved
Remove ESX 4 and reinstal esx infrastructure 3.5 upgrade 5
enable hv.enableIfUnlocked = TRUE on /etc/vmware/config
now i instal windows server 2008
this is a mystery
The configuration option, "hv.enableIfUnlocked," shouldn't have any effect for ESX.
Did you power off your system in the process of reverting to ESX 3.5? Have you powered off your system since enabling VT in the BIOS? As a previous poster pointed out, it is necessary to power off the system for changes to the VT settings in the BIOS to take effect.
I suspect that you can now go back to ESX 4.0, and everything will be fine.
i have power off and on, enable an disable bios and not work.
i have try many combination.
now with esx 3.5 i have 2008r2 64 bit
boh???
I just ran into this same issue with Windows Server 2008 R2 Datacenter, and ESXi 5.0.
All the troubleshooting in the world couldn't help.
Turns out it was a bad ISO, redownloaded from MS.. and we are back in business.