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 http://vmware.com/info?id=152.
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:

Update:

This also applies to:
Dell 2950 – Thanks Scott Bishop

Advertisements
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

BTjunkie.org – taken down – but now back up

Update: BTJunkie.org back online after Domain Transfer kungfoo – Nice one.

Sadly it would appear that btjunkie.org has been taken down. ūüė¶

A whois report for the domain btjunkie.org shows no valid name servers and the status is INACTIVE.

Domain Name:BTJUNKIE.ORG
Created On:10-Jun-2005 07:35:14 UTC
Last Updated On:18-Aug-2010 09:10:30 UTC
Expiration Date:10-Jun-2019 07:35:14 UTC
Sponsoring Registrar:Key-Systems GmbH (R51-LROR)
Status:CLIENT TRANSFER PROHIBITED
Status:INACTIVE
[…]
Name Server:
Name Server:
Name Server:

However if you still want to use BTjunkie.org in it’s final few days add these to your hosts file:

93.158.65.207 btjunkie.org
93.158.65.211 btjunkie.org
93.158.65.201 dl.btjunkie.org

Categories: News, P2P Tags: , , ,

Wikipedia Down

March 24, 2010 18:00 GMT: http://www.Wikipedia.org has been inaccessible for about 30 minutes now.

dig A http://www.wikipedia.org
http://www.wikipedia.org.      514     IN      CNAME   rr.wikimedia.org.

dig ANY http://www.wikimedia.org
http://www.wikimedia.org.      3600    IN      CNAME   rr.wikimedia.org.

dig ANY rr.wikimedia.org
there’s no entry for rr.wikimedia.org being published..

Also looks like ns2.wikimedia.org has fallen of the face of the earth and isn’t answering DNS queries.

ns2.wikimedia.org.      3600    IN      A       91.198.174.4

#nslookup http://www.wikimedia.org ns0.wikimedia.org

Server:         ns0.wikimedia.org
Address:        208.80.152.130#53

http://www.wikimedia.org       canonical name = rr.wikimedia.org.
rr.wikimedia.org        canonical name = rr.pmtpa.wikimedia.org.
Name:   rr.pmtpa.wikimedia.org
Address: 208.80.152.2

Update 18:30 GMT: In a tweet, Wikipedia confirmed and apologized for the site’s outage:

@Wikipedia; Sorry, everyone! English Wikipedia should be back in about an hour. Our tech team explains what happened: http://techblog.wikimedia.org/2010/03/global-outage-cooling-failure-and-dns/

Due to an overheating problem in our European data center many of our servers turned off to protect themselves. As this impacted all Wikipedia and other projects access from European users, we were forced to move all user traffic to our Florida cluster, for which we have a standard quick failover procedure in place, that changes our DNS entries.

However, shortly after we did this failover switch, it turned out that this failover mechanism was now broken, causing the DNS resolution of Wikimedia sites to stop working globally. This problem was quickly resolved, but unfortunately it may take up to an hour before access is restored for everyone, due to caching effects.

We apologize for the inconvenience this has caused.

Categories: News Tags: , ,

Moved to Word Press

Just moved over to Word Press because blogger is getting left in the dust. Word Press has a much better interface and content actually gets indexed by Google. Not like my blog at http://waynewrighttechtips.blogspot.com/

Categories: News Tags:

Broadcast: HD Video Ingest

I recently saw this application at a customer’s site and had the chance to take it for a test drive. Pretty sweet if you ask me.

So if you find yourself in a production broadcast environment and you need to ingest some content off digibeta using your £20,000 Sony VTR but instead of also occupying an Avid Editing suite or forking out £20,000+ for an Amberfin iCR have a look at Miura from BlueLucy Media.

Their slick application makes use of the¬†Decklink HD Extreme PCIe Capture Card to ingest (capture) HD video to a variety of formats (MPEG2, MPEG4, MXF OP1a, IMX50). The great thing about this app is that it can also create a low resolution proxy version at the same time (WMV, Flash, H.264, etc…).

Software and bundled Decklink HD capture card costs ¬£4700 – an amazing price considering the alternatives. They recommend a medium to high spec quad core Xeon HP workstation for capturing HD content which they estimate at costing another ¬£2000-3000 (but I believe at today’s prices – Dec 2009 – you could pick up a good workstation to do the job for under ¬£1000.)

Windows: Burn .iso to CD/DVD/Bluray

An easy and very useful free utility called ImgBurn that burns .iso images to physical disks is available from the nice people at Digital Digest.

www.imgburn.com