View API
|
| Local Properties | ||
| Service Types | Data Object Types | All Properties | All Methods |
Data Object - DesktopPCoIPDisplaySettings
- Class
- VMware.Hv.PCoIPDisplaySettings
- Property of
- DesktopDisplayProtocolSettings
- Since
- Horizon View 6.0
Data Object Description
PCoIP or BLAST protocol settings.Data Object Properties
Properties
| Name | Type | Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| renderer3D | xsd:string |
3D rendering is supported on Windows 7 or later guests running on VMs
with virtual hardware version 8 or later. The default protocol must
be PCoIP and users must not be allowed to choose their own protocol
to enable 3D rendering. For instant clone source desktop 3D rendering
always mapped to MANAGE_BY_VSPHERE_CLIENT
|
||||||||||||
| enableGRIDvGPUs | xsd:boolean |
When 3D rendering is managed by the vSphere Client, this enables
support for NVIDIA GRID vGPUs. This must be false if 3D rendering is
not managed by the vSphere Client. If this is true, the host or
cluster associated with the desktop must support NVIDIA GRID and vGPU
types required by the desktop's VirtualMachines, VmTemplate, or
BaseImageSnapshot. If this is false, the desktop's VirtualMachines,
VmTemplate, or BaseImageSnapshot must not support NVIDIA GRID vGPUs.
Since suspending VMs with passthrough devices such as vGPUs is not
possible, powerPolicy cannot be set to SUSPEND
if this is enabled.
Since Horizon View 6.1
|
||||||||||||
| vGPUGridProfile | xsd:string |
NVIDIA GRID vGPUs might have multiple profiles and any one of the available profiles
can be applied to newly created instant clone desktop. The profile specified in this field
will be used in the newly created instant clone desktop.
Since Horizon 7.1
|
||||||||||||
| vRamSizeMB | xsd:int |
VRAM size for View managed 3D rendering. More VRAM can improve 3D
performance. Size is in MB. On ESXi 5.0 hosts, the renderer allows a
maximum VRAM size of 128MB. On ESXi 5.1 and later hosts, the maximum
VRAM size is 512MB.
For Instant Clones, this value is inherited from snapshot of Master VM.
|
||||||||||||
| vRamSizeKB | xsd:long |
VRAM size in KB for Instant Clone desktops. This field is populated
after reading VRAM size from snapshot of MasterVM in the backend. It
is applicable only when 3D is disabled.
Since Horizon 7.2
|
||||||||||||
| maxNumberOfMonitors | xsd:int |
When 3D is disabled, the 'Max number of monitors' and 'Max resolution
of any one monitor' settings determine the amount of vRAM assigned to
machines in this desktop. The greater these values are, the more memory
will be consumed on the associated ESX hosts. Existing virtual machines
must be powered off and subsequently powered on for the change to take
effect. A restart will not cause the changes to take effect. If 3D is
enabled and managed by View, the maximum number of monitors must be 1
or 2.
For Instant Clones, this value is inherited from snapshot of Master VM.
|
||||||||||||
| maxResolutionOfAnyOneMonitor | xsd:string |
If 3D rendering is enabled and managed by View, this must be set to the
default value. When 3D rendering is disabled, the 'Max number of
monitors' and 'Max resolution of any one monitor' settings determine
the amount of vRAM assigned to machines in this desktop. The greater
these values are, the more memory will be consumed on the associated
ESX hosts. This setting is only relevant on managed machines. Existing
virtual machines must be powered off and subsequently powered on for
the change to take effect. A restart will not cause the changes to take
effect.
For Instant Clones, this value is inherited from snapshot of Master VM
|
| Top of page | Local Properties | ||
| Service Types | Data Object Types | All Properties | All Methods |