Archive for January, 2011

64bit Guest on VMware ESX 4.1 running on a HP DL380 G5

January 20, 2011 5 comments

I recently saw this error

Virtual Machine Message:
msg.cpuid.noLongmodeQuestionFmt: This Virtual Machine is configured for 64-bit guest operating systems. However, 64-bit operation is not possible.
This host is VT-capable, but VT is disabled.
VT might be disabled if it has been disabled in the BIOS settings or the host has not been power-cycled since changing this setting.
(1) Verify that the BIOS settings enable VT and disable 'trusted execution'
(2) Power-cycle the host if either of these BIOS settings have been changed.
(3) Power-cycle the host if you have not done so since installing VMware ESX.
(4) Update the host's BIOS to the latest version.
For more detailed information, see
Continue without 64-bit support?

and this related error from VMware vCenter Converter Standalone:

The destination does not support 64 bit guest operating systems.

These errors were produced when I was trying to move a 64bit machine onto VMware ESX 4.1 server running on a DL380 G5 with two Intel 5160 Xeon’s. I know they are 64bit because Intel confirms this on the Xeon 5160 Spec page. Also I previously installed Windows 2008 Standard R2 64bit on that box. That is after updating every bloody bit of firmware under the sun.

Eventhough the CPUs support 64bit, VMware ESX 4.1 won’t load a 64bit guest unless you’ve enabled Intel’s Visualization Technology in the BIOS.

Here’s the settings I ended up using.

Advanced Options

    Processor Options

    • HW Prefetcher: Enabled
    • Adjacent Sector Prefetch: Enabled
    • No-Execute Memory Protection: Enabled
    • Intel (R) Virtualization Technology: Enabled
    • Expansion Card Caching Optimization: Disabled
    • Low Power Halt State (Intel C1E): Enabled
    • Intel Core C3 State: Enabled
    • Processor Core Disable: All Processor Cores Enabled

For those of you who like screenshots:


This also applies to:
Dell 2950 – Thanks Scott Bishop

Categories: ESX, Hardware, HP, VMware, Windows 7

HP iLO Shared Network Port

HP iLO (Integrated Lights Out board for HP servers – remote control et la)

Starting at firmware version 1.60 (after 30 Jul 2008) and on supported hardware:
DL360 G4, ML350 G5, ML370 G4, and DL380 G4 and G5

There’s a feature called “iLO Shared Network Port”

Which means you don’t need to cable up a separate iLO network! You can even set the iLO to use a different VLAN tag. This will come in very handy if your Colo charges for extra Ethernet ports (most do)

iLO 2 shared network port

But with everything computer related… there are potential issues,

Some things to watch out for:

  • Set the iLO NIC to Auto-Negotiate to avoid it falling off the network when the server is powered down. Ref: HP Advisory: Integrated Lights-Out 2 (iLO 2) – Shared Network Port Set at 1000Mb May Not Respond When Server is Powered Off
  • VMware ESX server + iLO pass through
    There’s some chat in this forum that ESX server doesn’t support pass through of the iLO. I wouldn’t think the OS even comes into play here. Surely iLO pass through is done at the hardware level and the OS isn’t even aware of it. And beside I’m using a HP DL380 G5 running ESX 4.1 with the iLO set to Shared Network Port and it’s working fine. *knock* *knock* on wood.

    AH! “Pass Through” is a Windows Service called iLO Pass-through Service which allows the iLO console to be connected to a console Terminal Services Session and I gather from the terminology it means that it uses RDP all the way back to the client. Where as iLO Shared Network Port is a hardware based Ethernet port sharing feature.

Categories: Hardware, HP