Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
indent20px
styledisc

Glossary

GPU - Graphics Processing Unit

...

DB Schema changes:

New tables

  • op_host_gpu_groups (id, group_name, host_id, update_time) :  This table contains the mapping between host and available pci_devices in that host.

    Field

    Type

    NULL

    Key

    Default

    Comments

    id

    bigint(20) unsigned

    NO

    PRI

    NULL

    auto_increment

    group_id

    varchar(40)

    NO

     

    NULL

    GPU group name

    host_id

    bigint(20) unsigned

    NO

     

    NULL

     

  • vgpu_types (id, vgpu_type, gpu_group_id, remaining_vm_capacity) :  This table contains the record of available vgpu profiles.

    Field

    Type

    NULL

    Key

    Default

    Comments

    id

    bigint(20) unsigned

    NO

    PRI

    NULL

    auto_increment

    gpu_group_id

    bigint(20) unsigned

    NO

     

    NULL

    "id" in the op_host_gpu_groups table

    vgpu_type

    varchar(40)

    NO

     

    NULL

    Name label of the vgpu type.

    remaining_vm_capacity

    bigint(20) unsigned

     

     

    NULL

    remaining no. of vgpu the given gpu group with given vgpuType can create.

...

         e.g.: To create a service offering with GPU Passthrough support:
                http://localhost:8080/client/api?command=createServiceOffering&serviceofferingdetails\[0\].key=pciDevice&serviceofferingdetails\[0\].value=gpuPassthrough&response=json&.........

                To create a service offering with vGPU support:
                http://localhost:8080/client/api?command=createServiceOffering&serviceofferingdetails\[01\].key=pciDevice=vGPU&serviceofferingdetails\[1\].value=VGPU&serviceofferingdetails\[2\].key=vgpuType&serviceofferingdetails\[12\].vGPUTypevalue=GRID_200GRID%20K260Q&response=json........

  • listHosts : If the host is GPU enabled, then this API will also list the following GPU related information:
    • What are the GPU cards managed by this host.
    • Used Capacity
    • Available capacity

...

  • Supports XenServer 6.2 or later with required hotfixes [4].
  • HVM template is required to create a VM with GPU/VGPU support.
  • NVIDIA GRID K1 AND K2 cards supports homogeneous virtual GPUs i.e. at any given time, the vGPUs resident on a single physical GPU must be all of the same type. However, this restriction doesn't extend across physical GPUs on the same card. Each physical GPU on a K1 or K2 may host different types of virtual GPU at the same time. For example, a GRID K2 card has two physical GPUs, and supports three types of virtual GPU; GRID K200, GRID K240Q, AND GRID K260Q [3].

    GRID

    Profile Name

    No. of Physical GPUs

    Video Ram per vGPU

    Max Resolution

    vGPUs per GPU

    No. of vGPUs per Card

    KI

    GRID K100

    4

    256 MB

    1920 x 1200

    8

    32

    K1

    GRID K140Q

    4

    1 GB

    2560 x 1600

    4

    16

    K2

    GRID K200

    2

    256 MB

    1920 x 1200

    8

    16

    K2

    GRID K240Q

    2

    1 GB

    2560 x 1600

    4

    8

    K2

    GRID K260Q

    2

    2 GB

    2560 x 1600

    2

    4

Logging and debugging

  • All the VM activities involving GPU would be logged at different log levels (INFO, ERROR, DEBUG) in management server log file.

...