461: The Execute Disable/No Execute CPU feature is not enabled for this machine. vSphere Host Upgrade 3.5U4 > vSphere

[jreininger]

x - resolved.

[AndreTheGiant · Accepted solution]

You need to upgrade the BIOS.

CPU support NX from several years.

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

[IMSADMIN]

We have the same issue but there is no bios update from HP available. We are using HP Proliant BL640c G1 with the bios version from 2008.11.02

Thanks for any ideas.

Regards,

RC

[maxel]

What's the resolution for that?

[jreininger]

In my case, I just had to enable it in the bios. Pretty much why I tried to delete the posting but somebody already responded so I could not.

NX goes pretty far back so even if you dont have support for VT you should have NX support, be sure to check all the sub-menus on the bios, it might be in a 'secuirty' tab as I think l it was used as a method to not all virus to run at a low level on the CPU.

Recenlty, and more in the re: to VT support, I see people are hacking the bios chip to add VT support when vendors dont make this avil via bios upgrades. Of course, that is not something you would want to do on any sort of production hardware, so there might be a similar hack for NX support (???).

Its also looks pretty dang hardcore (first google search got me this):

[samansalehi]

Dear Friends

this problem may occur for HP servers, you have to Update Bios, then go to BIOS by pressing F9 and then Advanced Options-> Processor Options-> No-Excecute Page-Protection and make it Enable

[AngelC2]

I can't get into my BIOS to make this change, although I see the F9 option it doesn't take me to the BIOS.  I also read that F2 takes you into BIOS but that's not even an option on my BIOS screen.

I have other identical servers running ESX and I've enabled this on those servers because I knew it was needed when using them in a EVC cluster.  Now, I'm creating my first 64-bit VM running on a non-clustered host that requires this setting and when I reboot it, I can't get into the BIOS to make the change.

It's like the keyboard isn't recognizing when I'm pressing the keys yet this is the same keyboard/console that I use for the other ESX servers that I've enabled this on.

I'm running an HP Proliant DL360 G5 with a P58 BIOS dated 1/24/2008.

I'm going to try switching out the keyboard to see if that's the problem, but does anyone know of another way to get into the HP BIOS?

[AngelC2]

Ok, I just confirmed that it's not the keyboard.  I can go to any of my other identical HP servers and press the Alt-F1 to get into the console and then press Alt-F11 to get back to the main screen.

The only server giving me this problem where I can't even use the Alt-F1 or F11 because it doesn't respond is the server that has the VT disabled in the BIOS and the one with the red message on the screen that's the subject of this thread.

So, lost as to how am I going to be able to reboot this server and press F9 in order to edit the BIOS when it's not allowing me to do this because it doesn't recognize the keyboard 

[dvdbot]

its  No-Excecute Memory-Protection instead of No-Excecute Page-Protection most times you don't have to update.