Help using a NVIDIA Quadro M5000 with ESXi 5.1

[vandreytrindade]

Hi,

I`ve readed a lot of material about that since yesterday.

My scenario is the following:

• Server: HP ProLiant ML350 Gen9
• Graphic card:NVIDIA Quadro M5000
• vSphere version:5.1.0 build 2323236

Downloaded this driver from NVIDIA download center:

• NVD.NVIDIA_bootbank_NVIDIA-VMware_304.76-1OEM.510.0.0.802205-999851.zip

And installed this way:

• Enter maintenance mode
• Uncompressed the zip file and uploaded the vib file to the ESXi host.
• Accessed the server using SSH and ran this command: esxcli software vib install -v /vmfs/volumes/L20/NVIDIA-VMware-304.76-1OEM.510.0.0.802205.x86_64.vib

Then I configured the xorg service to start with the host and rebooted it.

Created a new VM using Windows Server 2012 R2 x64 media and configured it to use 3D support (128MB).

When I try to install the NVIDIA driver on Windows, it tolds me that no compatible hardware was found.

So I started troubleshooting and ran this commands on a SSH session:

When I go to the passthrough configuration, it shows Unkown VGA compatible controller:

On the iLO, it shows the correct model of the graphic card:

Can it be an ESXi version problem?

If I upgrade to ESXi 5.5 after installing the ESXi 5.1 NVIDIA driver, it will continue working?

I've started reading this document: http://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-horizon-view-graph...

And the VT-d is enabled on BIOS.

Any help will be appreciated =]

[vandreytrindade]

Hi again,

I'm trying to upgrade the ESXi host to the latest 5.5 version.

I'm using this command:

• esxcli software profile update -p <profile image> -d /vmfs/volumes/<datastore>/<offline bundle file>.zip

But everytime I try to do that, the server reboots with the new version but no access to the local datastore.

When I reboot it again, it returns to the old configuration.........

[vandreytrindade · Accepted solution]

Hi,

I've updated the ESXi 5.5 and configured the graphic card as passthrough and installed the driver on the guest VM with Windows Server 2012 R2.

It seems to be working pretty nice.

Thanks!