VMware Horizon Community
kcmount
Contributor
Contributor
Jump to solution

vGPU/ESXi 6.0 "Hardware GPU is required but not available"

Hi there,

I'm having problems powering up a VM that is configured with hardware 3D rendering. It throws an error "Hardware GPU is required but not available. The virtual machine will not start until GPU resources are available or the virtual machine is configured to allow software rendering". I've upped the VM hardware version from 9 to 11 just to see if it made any difference.

I've looked around and various folks have had different issues but the good people here ask for the same info so hopefully providing it below will help.

[root@localhost:~] nvidia-smi

Sat Apr 25 15:45:04 2015      

+------------------------------------------------------+                      

| NVIDIA-SMI 346.42     Driver Version: 346.42         |                      

|-------------------------------+----------------------+----------------------+

| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |

| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |

|===============================+======================+======================|

|   0  GRID K1             On   | 0000:04:00.0     Off |                  N/A |

| N/A   39C    P8    10W /  31W |     10MiB /  4095MiB |      0%      Default |

+-------------------------------+----------------------+----------------------+

|   1  GRID K1             On   | 0000:05:00.0     Off |                  N/A |

| N/A   40C    P8    10W /  31W |     10MiB /  4095MiB |      0%      Default |

+-------------------------------+----------------------+----------------------+

|   2  GRID K1             On   | 0000:06:00.0     Off |                  N/A |

| N/A   33C    P8    10W /  31W |     10MiB /  4095MiB |      0%      Default |

+-------------------------------+----------------------+----------------------+

|   3  GRID K1             On   | 0000:07:00.0     Off |                  N/A |

| N/A   34C    P8    10W /  31W |     10MiB /  4095MiB |      0%      Default |

+-------------------------------+----------------------+----------------------+

                                                                              

+-----------------------------------------------------------------------------+

| Processes:                                                       GPU Memory |

|  GPU       PID  Type  Process name                               Usage      |

|=============================================================================|

|  No running processes found                                                 |

+-----------------------------------------------------------------------------+

[root@localhost:~] gpuvm

Xserver unix:0, PCI ID 0:4:0:0, vGPU: Not set, GPU maximum memory 4183620KB

    GPU memory left 4183620KB.

Xserver unix:1, PCI ID 0:5:0:0, vGPU: Not set, GPU maximum memory 4183620KB

    GPU memory left 4183620KB.

Xserver unix:2, PCI ID 0:6:0:0, vGPU: Not set, GPU maximum memory 4183620KB

    GPU memory left 4183620KB.

Xserver unix:3, PCI ID 0:7:0:0, vGPU: Not set, GPU maximum memory 4183620KB

    GPU memory left 4183620KB.

[root@localhost:~] cat /var/log/vmkernel.log  | grep nvidia

2015-04-25T15:15:14.942Z cpu1:33338)Loading module nvidia ...

2015-04-25T15:15:14.947Z cpu1:33338)Elf: 1865: module nvidia has license NVIDIA

2015-04-25T15:15:15.017Z cpu1:33338)CpuSched: 592: user latency of 33339 tq:nvidia_timer_queue 0 changed by 33338 vmkeventd -6

2015-04-25T15:15:15.269Z cpu1:33338)Device: 191: Registered driver 'nvidia' from 19

2015-04-25T15:15:15.269Z cpu1:33338)Mod: 4942: Initialization of nvidia succeeded with module ID 19.

2015-04-25T15:15:15.269Z cpu1:33338)nvidia loaded successfully.

2015-04-25T15:15:15.503Z cpu15:33337)Device: 326: Found driver nvidia for device 0x281c4302a6589365

2015-04-25T15:15:15.541Z cpu15:33337)Device: 326: Found driver nvidia for device 0x4eaa4302a65895fc

2015-04-25T15:15:15.579Z cpu15:33337)Device: 326: Found driver nvidia for device 0x7c044302a65898cd

2015-04-25T15:15:15.616Z cpu15:33337)Device: 326: Found driver nvidia for device 0x2dfe4302a6589b17

NVRM: nvidia_associate vmgfx0

NVRM: nvidia_associate vmgfx1

NVRM: nvidia_associate vmgfx2

NVRM: nvidia_associate vmgfx3

2015-04-25T15:15:50.363Z cpu11:35362)IntrCookie: 1852: cookie 0x3a moduleID 19 <nvidia> exclusive, flags 0x1d

2015-04-25T15:15:51.041Z cpu11:35362)IntrCookie: 1852: cookie 0x3b moduleID 19 <nvidia> exclusive, flags 0x1d

2015-04-25T15:15:51.693Z cpu11:35362)IntrCookie: 1852: cookie 0x3c moduleID 19 <nvidia> exclusive, flags 0x1d

2015-04-25T15:15:52.385Z cpu11:35362)IntrCookie: 1852: cookie 0x3d moduleID 19 <nvidia> exclusive, flags 0x1d

2015-04-25T15:15:54.655Z cpu7:35676)IntrCookie: 1852: cookie 0x3e moduleID 19 <nvidia> exclusive, flags 0x1d

2015-04-25T15:15:54.871Z cpu7:35676)IntrCookie: 1852: cookie 0x3f moduleID 19 <nvidia> exclusive, flags 0x1d

2015-04-25T15:15:55.084Z cpu7:35676)IntrCookie: 1852: cookie 0x40 moduleID 19 <nvidia> exclusive, flags 0x1d

2015-04-25T15:15:55.302Z cpu7:35676)IntrCookie: 1852: cookie 0x41 moduleID 19 <nvidia> exclusive, flags 0x1d

2015-04-25T15:15:56.431Z cpu24:35841)IntrCookie: 1852: cookie 0x42 moduleID 19 <nvidia> exclusive, flags 0x1d

2015-04-25T15:15:56.667Z cpu24:35841)IntrCookie: 1852: cookie 0x43 moduleID 19 <nvidia> exclusive, flags 0x1d

2015-04-25T15:15:56.897Z cpu24:35841)IntrCookie: 1852: cookie 0x44 moduleID 19 <nvidia> exclusive, flags 0x1d

2015-04-25T15:15:57.125Z cpu24:35841)IntrCookie: 1852: cookie 0x45 moduleID 19 <nvidia> exclusive, flags 0x1d

2015-04-25T15:15:58.255Z cpu6:36015)IntrCookie: 1852: cookie 0x46 moduleID 19 <nvidia> exclusive, flags 0x1d

2015-04-25T15:15:58.478Z cpu6:36015)IntrCookie: 1852: cookie 0x47 moduleID 19 <nvidia> exclusive, flags 0x1d

2015-04-25T15:15:58.695Z cpu6:36015)IntrCookie: 1852: cookie 0x48 moduleID 19 <nvidia> exclusive, flags 0x1d

2015-04-25T15:15:58.914Z cpu6:36015)IntrCookie: 1852: cookie 0x49 moduleID 19 <nvidia> exclusive, flags 0x1d

[root@localhost:~] esxcli software vib list | grep -i nvidia

NVIDIA-vgx-VMware_ESXi_6.0_Host_Driver  346.42-1OEM.600.0.0.2159203           NVIDIA    VMwareAccepted    2015-04-25 

Appreciate any thoughts anyone may have!

Thank you!

Kim

Reply
0 Kudos
1 Solution

Accepted Solutions
Linjo
Leadership
Leadership
Jump to solution

Aha, ok.

"hardware" in the VM configuration means vSGA, that might not be obvious but thats the way it is.

To use vGPU you need to add a new device to the virtual machine and select the vGPU profile you want to assign, you should set the graphics to "software"

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".

View solution in original post

Reply
0 Kudos
6 Replies
Linjo
Leadership
Leadership
Jump to solution

Looks like you have configured the pool for vSGA but installed the driver for vGPU.

If you want to use vGPU then you need to configure that on the pool settings.

You also need to use Horizon View 6.1.

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
Reply
0 Kudos
kcmount
Contributor
Contributor
Jump to solution

Hey Linjo,

Many thanks for your reply.

Maybe I'm going about this completely the wrong way but I've not even reached the View stage yet, literally just trying to boot the template up to install the Nvidia drivers etc on the host.

I did install the vSGA vib first in error (then removed it) before installing the vGPU one thereafter (though both the host was rebooted and xorg restarted after).

From the outputs above does the host look OK in your experience?

Thanks again for your thoughts.

Kim

Reply
0 Kudos
Linjo
Leadership
Leadership
Jump to solution

Aha, ok.

"hardware" in the VM configuration means vSGA, that might not be obvious but thats the way it is.

To use vGPU you need to add a new device to the virtual machine and select the vGPU profile you want to assign, you should set the graphics to "software"

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
Reply
0 Kudos
kcmount
Contributor
Contributor
Jump to solution

Hi there,

Many thanks for this, that worked a treat.

Cheers,

Kim

Reply
0 Kudos
iforbes
Hot Shot
Hot Shot
Jump to solution

Hi Linjo,

Why is it that for vGPU the 3D Renderer has to be set to software? That seems odd. I realize that Hardware is for vSGA. Wy wouldn't it be set to Automatic?

Thanks

Reply
0 Kudos
Linjo
Leadership
Leadership
Jump to solution

So the reason is not to dedicate resources that are not used, if you set it to "Software" it will never use "vSGA" resources and that is what you want since you are using vGPU instead.

The 2 features are not aware of each other (yet) and you could end up in a situation where it allocates both vSGA and vGPU but do only use one of them.

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
Reply
0 Kudos