Artificial Intelligence Computing Leadership from NVIDIA
Documentation for vGPU configs
New vGPU [b]plugin parameters[/b] for vGPU SW 8.0 (hypervisor driver 418.66) from vGPU SW 7.2: [code]swizzid zcull_buffer_invalidation_enabled[/code] Some funny [b]registry DWords[/b]: [code]RmEnableKvmVgpuMigration (RMEnableVoltaMigration was deleted) RMSetVGPUVersionMax RMSetVGPUVersionMin RMSetSriovMode (SR-IOV finally coming ?) RMSriovVFFeatureMask RmSriovVgpuFbScheme RMIllumFeatureDisable (maybe https://en.wikipedia.org/wiki/Illuminati ) RMNvTelemetryCollection (the most requested feature) [/code]
New vGPU plugin parameters for vGPU SW 8.0 (hypervisor driver 418.66) from vGPU SW 7.2:
swizzid
zcull_buffer_invalidation_enabled

Some funny registry DWords:
RmEnableKvmVgpuMigration (RMEnableVoltaMigration was deleted)
RMSetVGPUVersionMax
RMSetVGPUVersionMin

RMSetSriovMode (SR-IOV finally coming ?)
RMSriovVFFeatureMask
RmSriovVgpuFbScheme

RMIllumFeatureDisable (maybe https://en.wikipedia.org/wiki/Illuminati )
RMNvTelemetryCollection (the most requested feature)

#16
Posted 04/17/2019 06:42 PM   
New vGPU [b]plugin parameters[/b] for vGPU SW 9.0 (hypervisor driver 430.27) from vGPU SW 8.0: [code]disable_p2p vgpu_uuid[/code] Some new [b]registry DWords[/b]: [code]RmEnableKvmDoorbellEmulation RMGuestECCState RMvGpuAllowPageRetirement[/code] [i]PS: NVidia QA fails again. All profiles *C (vComputeServer) are missing in XenServer package. nvlddmkm.sys is still buggy and crashing whole Windows (7,10) (Bug Check 0x0000003B: SYSTEM_SERVICE_EXCEPTION / 0xC0000005: STATUS_ACCESS_VIOLATION or Bug Check 0x0000000A: IRQL_NOT_LESS_OR_EQUAL with null pointer dereference (for example nvlddmkm calls KeWaitForSingleObject() with null pointer)). NVidia drivers also allocate data structures (for example display structure) on kernel limited stack and do not check bounds (this corrupts stack and crashes Windows too). Few bugs are repaired (in minor release updates) from many many many - [url]https://nvidia.custhelp.com/app/answers/detail/a_id/4772[/url], [url]https://nvidia.custhelp.com/app/answers/detail/a_id/4841[/url] and [url]https://nvidia.custhelp.com/app/answers/detail/a_id/4907[/url]! [/i]
New vGPU plugin parameters for vGPU SW 9.0 (hypervisor driver 430.27) from vGPU SW 8.0:
disable_p2p
vgpu_uuid

Some new registry DWords:
RmEnableKvmDoorbellEmulation
RMGuestECCState
RMvGpuAllowPageRetirement

PS: NVidia QA fails again. All profiles *C (vComputeServer) are missing in XenServer package. nvlddmkm.sys is still buggy and crashing whole Windows (7,10) (Bug Check 0x0000003B: SYSTEM_SERVICE_EXCEPTION / 0xC0000005: STATUS_ACCESS_VIOLATION or Bug Check 0x0000000A: IRQL_NOT_LESS_OR_EQUAL with null pointer dereference (for example nvlddmkm calls KeWaitForSingleObject() with null pointer)). NVidia drivers also allocate data structures (for example display structure) on kernel limited stack and do not check bounds (this corrupts stack and crashes Windows too). Few bugs are repaired (in minor release updates) from many many many - https://nvidia.custhelp.com/app/answers/detail/a_id/4772, https://nvidia.custhelp.com/app/answers/detail/a_id/4841 and https://nvidia.custhelp.com/app/answers/detail/a_id/4907!

#17
Posted 06/22/2019 11:21 AM   
New vGPU [b]plugin parameters[/b] for vGPU SW 10.0 (hypervisor driver 440.43) from vGPU SW 9.x: [code]gr_idx increase_rsvd_memory_size[/code] Some new [b]registry DWords[/b]: [code]RmDisableHwFaultBuffer RmDisableVblankMscg RMDumpNvLog RmEnableWDDMInterleaving RmFbReserveConsole RmFeatureStretchVblank RMSchMicroSched [/code] There is also new resolution limiting feature - total pixels per all heads (see [b]"maxPixels" in vgpuConfig.xml[/b]) (see [url]https://docs.nvidia.com/grid/10.0/grid-vgpu-user-guide/index.html#virtual-gpu-display-resolution-handling[/url]). Examples of resolution: [code] name WxH pixels SXGA 1280*1024 1310720 FHD 1920*1080 2073600 4k 3840*2160 8294400 5k 5120*2880 14745600 8k 7680*4320 33177600[/code] There are seven different "NVIDIA engeenered" pixels limits: [code] profile numHeads maxPixels maximum examples *A 1 1310720 1xSXGA only *-0B, *-0Q 2 8192000 2xFHD (4k impossible - 102400 pixels missing) *-1B* 4 16384000 1x5k or 1x4k+3xFHD (two 4k impossible - 204800 pixels missing) *-2B*, *-1Q 4 17694720 1x5k or 2x4k M*-2Q,M*-4Q,M*-8Q 4 35389440 2x5k or 4x4k (8k blocked by maximum width/height for M*) *-2Q,*-3Q 4 35389440 1x8k *-4Q 4 58982400 1x8k+3x4k (two 8k impossible - 7372800 pixels missing) >=*-8Q 4 66355200 2x8k [/code] FYI: New drivers NVenc parameter defaults have terribly impact for VDI low-latency decoding pipeline [url]https://devtalk.nvidia.com/default/topic/1056834/#5415872[/url] (new explicit parameter settings and recompilation of NVenc-based encoders are needed) !
New vGPU plugin parameters for vGPU SW 10.0 (hypervisor driver 440.43) from vGPU SW 9.x:
gr_idx
increase_rsvd_memory_size

Some new registry DWords:
RmDisableHwFaultBuffer
RmDisableVblankMscg
RMDumpNvLog
RmEnableWDDMInterleaving
RmFbReserveConsole
RmFeatureStretchVblank
RMSchMicroSched

There is also new resolution limiting feature - total pixels per all heads (see "maxPixels" in vgpuConfig.xml) (see https://docs.nvidia.com/grid/10.0/grid-vgpu-user-guide/index.html#virtual-gpu-display-resolution-handling). Examples of resolution:
name  WxH        pixels
SXGA 1280*1024 1310720
FHD 1920*1080 2073600
4k 3840*2160 8294400
5k 5120*2880 14745600
8k 7680*4320 33177600

There are seven different "NVIDIA engeenered" pixels limits:
profile               numHeads    maxPixels    maximum examples
*A 1 1310720 1xSXGA only
*-0B, *-0Q 2 8192000 2xFHD (4k impossible - 102400 pixels missing)
*-1B* 4 16384000 1x5k or 1x4k+3xFHD (two 4k impossible - 204800 pixels missing)
*-2B*, *-1Q 4 17694720 1x5k or 2x4k
M*-2Q,M*-4Q,M*-8Q 4 35389440 2x5k or 4x4k (8k blocked by maximum width/height for M*)
*-2Q,*-3Q 4 35389440 1x8k
*-4Q 4 58982400 1x8k+3x4k (two 8k impossible - 7372800 pixels missing)
>=*-8Q 4 66355200 2x8k

FYI: New drivers NVenc parameter defaults have terribly impact for VDI low-latency decoding pipeline https://devtalk.nvidia.com/default/topic/1056834/#5415872 (new explicit parameter settings and recompilation of NVenc-based encoders are needed) !

#18
Posted 12/22/2019 10:14 AM   
Scroll To Top

Add Reply