@kubevirt-ui/kubevirt-api
    Preparing search index...

    Interface V1CPU

    CPU allows specifying the CPU topology.

    interface V1CPU {
        cores?: number;
        dedicatedCpuPlacement?: boolean;
        features?: V1CPUFeature[];
        isolateEmulatorThread?: boolean;
        maxSockets?: number;
        model?: string;
        numa?: V1NUMA;
        realtime?: V1Realtime;
        sockets?: number;
        threads?: number;
    }
    Index

    Properties

    cores?: number

    Cores specifies the number of cores inside the vmi. Must be a value greater or equal 1.

    int64

    dedicatedCpuPlacement?: boolean

    DedicatedCPUPlacement requests the scheduler to place the VirtualMachineInstance on a node with enough dedicated pCPUs and pin the vCPUs to it.

    features?: V1CPUFeature[]

    Features specifies the CPU features list inside the VMI.

    isolateEmulatorThread?: boolean

    IsolateEmulatorThread requests one more dedicated pCPU to be allocated for the VMI to place the emulator thread on it.

    maxSockets?: number

    MaxSockets specifies the maximum amount of sockets that can be hotplugged

    int64

    model?: string

    Model specifies the CPU model inside the VMI. List of available models https://github.com/libvirt/libvirt/tree/master/src/cpu_map. It is possible to specify special cases like "host-passthrough" to get the same CPU as the node and "host-model" to get CPU closest to the node one. Defaults to host-model.

    numa?: V1NUMA

    NUMA allows specifying settings for the guest NUMA topology

    realtime?: V1Realtime

    Realtime instructs the virt-launcher to tune the VMI for lower latency, optional for real time workloads

    sockets?: number

    Sockets specifies the number of sockets inside the vmi. Must be a value greater or equal 1.

    int64

    threads?: number

    Threads specifies the number of threads inside the vmi. Must be a value greater or equal 1.

    int64