第9章


9.1.

9.1.1.

Expand
   

注記

  1. This option does not affect `PCPU` inventory, which cannot be
    overcommitted.
    Copy to Clipboard Toggle word wrap
  2. If this option is set to something *other than* `None` or `0.0`, the
    allocation ratio will be overwritten by the value of this option, otherwise,
    the allocation ratio will not change. Once set to a non-default value, it is
    not possible to "unset" the config to get back to the default behavior. If
    you want to reset back to the initial value, explicitly specify it to the
    value of `initial_cpu_allocation_ratio`.
    Copy to Clipboard Toggle word wrap

  1. If the value is set to `>1`, we recommend keeping track of the free disk
    space, as the value approaching `0` may result in the incorrect
    functioning of instances using it at the moment.
    Copy to Clipboard Toggle word wrap
  2. If this option is set to something *other than* `None` or `0.0`, the
    allocation ratio will be overwritten by the value of this option, otherwise,
    the allocation ratio will not change. Once set to a non-default value, it is
    not possible to "unset" the config to get back to the default behavior. If
    you want to reset back to the initial value, explicitly specify it to the
    value of `initial_disk_allocation_ratio`.
    Copy to Clipboard Toggle word wrap

https://cloudinit.readthedocs.io/en/latest/topics/datasources.html
Copy to Clipboard Toggle word wrap

  1. The following image properties are *never* inherited regardless of
    whether they are listed in this configuration option or not:
    Copy to Clipboard Toggle word wrap

  1. If this option is set to something *other than* `None` or `0.0`, the
    allocation ratio will be overwritten by the value of this option, otherwise,
    the allocation ratio will not change. Once set to a non-default value, it is
    not possible to "unset" the config to get back to the default behavior. If
    you want to reset back to the initial value, explicitly specify it to the
    value of `initial_ram_allocation_ratio`.
    Copy to Clipboard Toggle word wrap

  • In this example we are reserving on NUMA node 0 64 pages of 2MiB
    and on NUMA node 1 1 page of 1GiB.
    Copy to Clipboard Toggle word wrap

9.1.2.

Expand
表9.1
   

9.1.3.

Expand
表9.2
   

9.1.4.

Expand
表9.3
   

9.1.5.

Expand
表9.4
   

9.1.6.

Expand
表9.5
   

9.1.7.

Expand
表9.6
   

  1. The compute service cannot reliably determine which types of virtual
    interfaces (`port.binding:vif_type`) will send `network-vif-plugged`
    events without an accompanying port `binding:host_id` change.
    Open vSwitch and linuxbridge should be OK, but OpenDaylight is at least
    one known backend that will not currently work in this case, see bug
    https://launchpad.net/bugs/1755890 for more details.
    Copy to Clipboard Toggle word wrap

https://docs.openstack.org/nova/latest/admin/managing-resource-providers.html
Copy to Clipboard Toggle word wrap

9.1.8.

Expand
表9.7
   

9.1.9.

Expand
表9.8
   

ssl_ciphers = "kEECDH+aECDSA+AES:kEECDH+AES+aRSA:kEDH+aRSA+AES"
Copy to Clipboard Toggle word wrap

https://www.openssl.org/docs/man1.1.0/man1/ciphers.html
Copy to Clipboard Toggle word wrap

9.1.10.

Expand
表9.9
   

9.1.11.

Expand
表9.10
   

9.1.12.

Expand
表9.11
   

9.1.13.

Expand
表9.12
   

9.1.14.

Expand
表9.13
   

[vgpu_nvidia-35]
device_addresses = 0000:84:00.0,0000:85:00.0
Copy to Clipboard Toggle word wrap
[vgpu_nvidia-36]
device_addresses = 0000:86:00.0
Copy to Clipboard Toggle word wrap

9.1.15.

Expand
表9.14
   

9.1.16.

Expand
表9.15
   

    1. [filter_scheduler]
      hypervisor_version_weight_multiplier=-1000
      Copy to Clipboard Toggle word wrap
    1. [filter_scheduler]
      hypervisor_version_weight_multiplier=2.5
      Copy to Clipboard Toggle word wrap
    1. [filter_scheduler]
      hypervisor_version_weight_multiplier=0
      Copy to Clipboard Toggle word wrap

  1. In a multi-cell (v2) setup where the cell MQ is separated from the
    top-level, computes cannot directly communicate with the scheduler. Thus,
    this option cannot be enabled in that scenario. See also the
    `[workarounds] disable_group_policy_check_upcall` option.
    Copy to Clipboard Toggle word wrap

9.1.17.

Expand
表9.16
   

注記

9.1.18.

Expand
表9.17
   

9.1.19.

Expand
表9.18
   

9.1.20.

Expand
表9.19
   

64, 128, 256, 512, 1024
Copy to Clipboard Toggle word wrap

9.1.21.

Expand
表9.20
   

9.1.22.

Expand
表9.21
   

9.1.23.

Expand
表9.22
   

9.1.24.

Expand
表9.23
   

9.1.25.

Expand
表9.24
   

9.1.26.

Expand
表9.25
   

  • This is only necessary if the URI differs to the commonly known URIs
    for the chosen virtualization type.
    Copy to Clipboard Toggle word wrap

[libvirt]
cpu_mode = custom
cpu_models = Cascadelake-Server
cpu_model_extra_flags = -hle, -rtm, +ssbd, mtrr
Copy to Clipboard Toggle word wrap

[libvirt]
cpu_mode = custom
cpu_models = Haswell-noTSX-IBRS
cpu_model_extra_flags = -PDPE1GB, +VMX, pcid
Copy to Clipboard Toggle word wrap

[libvirt]
enabled_perf_events = cpu_clock, cache_misses
Copy to Clipboard Toggle word wrap

  1. It is recommended to read :ref:`the deployment documentation's
    section on this option <num_memory_encrypted_guests>` before
    deciding whether to configure this setting or leave it at the
    default.
    Copy to Clipboard Toggle word wrap

"$LABEL:$NSNAME[&verbar;$NSNAME][,$LABEL:$NSNAME[&verbar;$NSNAME]]"
Copy to Clipboard Toggle word wrap

9.1.27.

Expand
表9.26
   

`name1=1.0, name2=-1.3`
Copy to Clipboard Toggle word wrap

`(name1.value * 1.0) + (name2.value * -1.3)`
Copy to Clipboard Toggle word wrap

9.1.28.

Expand
表9.27
   

9.1.29.

Expand
表9.28
   

[neutron]
physnets = foo, bar
Copy to Clipboard Toggle word wrap
[neutron_physnet_foo]
numa_nodes = 0
Copy to Clipboard Toggle word wrap
[neutron_physnet_bar]
numa_nodes = 0,1
Copy to Clipboard Toggle word wrap

[neutron_tunnel]
numa_nodes = 1
Copy to Clipboard Toggle word wrap

9.1.30.

Expand
表9.29
   

9.1.31.

Expand
表9.30
   

9.1.32.

Expand
表9.31
   

9.1.33.

Expand
表9.32
   

9.1.34.

Expand
表9.33
   

9.1.35.

Expand
表9.34
   

9.1.36.

Expand
表9.35
   

9.1.37.

Expand
表9.36
   

9.1.38.

Expand
表9.37
   

  • alias = {
      "name": "QuickAssist",
      "product_id": "0443",
      "vendor_id": "8086",
      "device_type": "type-PCI",
      "numa_policy": "required"
    }
    Copy to Clipboard Toggle word wrap
    This defines an alias for the Intel QuickAssist card. (multi valued). Valid
    key values are :
    Copy to Clipboard Toggle word wrap
    `name`
      Name of the PCI alias.
    Copy to Clipboard Toggle word wrap
    `product_id`
      Product ID of the device in hexadecimal.
    Copy to Clipboard Toggle word wrap
    `vendor_id`
      Vendor ID of the device in hexadecimal.
    Copy to Clipboard Toggle word wrap
    `device_type`
      Type of PCI device. Valid values are: `type-PCI`, `type-PF` and
      `type-VF`. Note that `"device_type": "type-PF"` **must** be specified
      if you wish to passthrough a device that supports SR-IOV in its entirety.
    Copy to Clipboard Toggle word wrap
    `numa_policy`
      Required NUMA affinity of device. Valid values are: `legacy`,
      `preferred` and `required`.
    Copy to Clipboard Toggle word wrap

  • Where `[` indicates zero or one occurrences, `{` indicates zero or
    multiple occurrences, and `&verbar;` mutually exclusive options. Note that any
    missing fields are automatically wildcarded.
    Copy to Clipboard Toggle word wrap
    Valid key values are :
    Copy to Clipboard Toggle word wrap
    `vendor_id`
      Vendor ID of the device in hexadecimal.
    Copy to Clipboard Toggle word wrap
    `product_id`
      Product ID of the device in hexadecimal.
    Copy to Clipboard Toggle word wrap
    `address`
      PCI address of the device. Both traditional glob style and regular
      expression syntax is supported. Please note that the address fields are
      restricted to the following maximum values:
    Copy to Clipboard Toggle word wrap
  • `devname`
      Device name of the device (for e.g. interface name). Not all PCI devices
      have a name.
    Copy to Clipboard Toggle word wrap
    `<tag>`
      Additional `<tag>` and `<tag_value>` used for matching PCI devices.
      Supported `<tag>` values are :
    Copy to Clipboard Toggle word wrap

9.1.39.

Expand
表9.38
   

9.1.40.

Expand
表9.39
   

9.1.41.

Expand
表9.40
   

9.1.42.

Expand
表9.41
   

9.1.43.

Expand
表9.42
   

9.1.44.

Expand
表9.43
   

  • The scheme must be identical to the scheme configured for the RDP HTML5
    console proxy service. It is `http` or `https`.
    Copy to Clipboard Toggle word wrap
    The IP address must be identical to the address on which the RDP HTML5
    console proxy service is listening.
    Copy to Clipboard Toggle word wrap
    The port must be identical to the port on which the RDP HTML5 console proxy
    service is listening.
    Copy to Clipboard Toggle word wrap

9.1.45.

Expand
表9.44
   

9.1.46.

Expand
表9.45
   

9.1.47.

Expand
表9.46
   

9.1.48.

Expand
表9.47
   

9.1.49.

Expand
表9.48
   

9.1.50.

Expand
表9.49
   

9.1.51.

Expand
表9.50
   

9.1.52.

Expand
表9.51
   

9.1.53.

Expand
表9.52
   

注記

9.1.54.

Expand
表9.53
   

9.1.55.

Expand
表9.54
   

https://bugs.launchpad.net/nova/+bug/1334398
Copy to Clipboard Toggle word wrap

https://bugs.launchpad.net/nova/+bug/1415106
Copy to Clipboard Toggle word wrap

9.1.56.

Expand
表9.55
   

警告

9.1.57.

Expand
表9.56
   

トップに戻る
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2025 Red Hat