64-bit guest OS

[nicvw]

I have a Dell 2950 with Xeon E5430 CPUs running ESX 3.5 U1 but I am unable to run 64-bit guest OS. If I create a bootable CD with the CPUID ISO and boot it in my server it shows that it supports 64-bit VMware and Longmode and it shows my supported EVC modes. However if i boot a VM with the ISO it shows 64-bit VMware as unsupported and it shows no supported EVC modes. This means I cannot run 64-bit guest OS at all which is a requirement in my environment... Does anyone have any ideas on how to get this working?

[Rubeck]

Is VT enabled in the BIOS? (If this exist in the BIOS at all... I have no experience with Dell equipment)

/Rubeck

[nicvw]

Yes, VT is enabled in the BIOS. Like I said the server itself supports all necessary extensions as per the ouput when booting off the CPUID CD. Guest OS does not. Attached is the output from a guest set as Solaris 64-bit when booting with CPUID image.

When I boot the physical server with the image 64-bit VMware is YES and there are supported EVC modes.

[prashantprahlad]

The CPUID iso is meant to run natively (on your serve). You should be able to run 64-bit guest OSes if your physical server shows 64-bit support through the CPUID iso.

The screenshot you have is from running CPUID iso as a guest OS, correct Don't use any information from that output, since it doesn't tell you anything about your real hardware.

[gguntz]

" *

Requirements for 64-Bit Guest Operating Systems

*

To install and run a 64‐bit guest operating system, you must have a supported CPU in the host computer and

you must be running a VMware product that supports 64‐bit guests. For details, see the documentation for

your VMware product.

*

Running 64-Bit Guest Operating Systems

*

To run a 64‐bit guest operating system on 32‐bit Intel hardware with VT support, you must enable VT on the

host machine BIOS.

*

64-Bit Linux Guests and Execute Disable Functionality

*

When running a 64‐bit Linux guest operating system on EM64T hardware, make sure that you have Execute

Disable functionality enabled in the host BIOS. This helps to ensure that the Linux guest operating system will run without

interruption."

This is from http://[www.vmware.com/pdf/GuestOS_guide.pdf|http://www.vmware.com/pdf/GuestOS_guide.pdf]

HTH

G

[mike_laspina]

Looks Ok,

Are you refering to the Solaris install process showing 32 bit on install. That's normal it will go to 64 after it installs.

[nicvw]

Hi, I am referring to booting up Solaris after the install. With paravirtualisation disabled on the VM's configuration it tries to boot 64-bit and then the VM just powers down. With paravirtualisation enabled in the VM it just boots in 32-bit mode.

[nicvw]

I will reboot one of the servers this morning and check whether Execute Disable is enabled in the BIOS. Thank you very much for the info

[nicvw]

Execute disable is enabled in my hosts' BIOSes. I have also logged a support call with Dell regarding this issue... hopefully I get some useful feedback from them soon

[mike_laspina]

What info is in the vmware.log file when it powers up?

[nicvw]

I have attached the vmware.log file. There is also a coredump if anyone is interested.

[mike_laspina · Accepted solution]

It looks like an SMP issue. There were some issues with SMP in 3.0.2 on solaris 64 VMs. There is a knowledge base article on it. This is definitely an engineering level problem, I would suggest opening a call ticket for this one.

Your running build=build-98103 option=BETA

I would suggest you bring this to update 2 if possible or at least install ESX350-200805501-BG if not already done.

[desh_thomson]

Check this link:

http://www.dell.com/downloads/global/solutions/vmotion_compatiblity_matix.pdf

Check your hardware and processor type in the matrix and see if it has 64 Bit guest support

[nicvw]

I was holding off going to Update 2 after the licensing fiasco but things seem fine after they re-released it. I will update this weekend and see whether it resolves this issue. I am a bit puzzled by the BETA in that output as I only ever installed updates from Update Manager... Weird

[nicvw]

Upgrading to Update 2 and using the latest release of Solaris 10 resolved the issue. Thanks for the suggestion