gitee.com/leisunstar/runtime@v0.0.0-20200521203717-5cef3e7b53f9/cli/config/configuration-clh.toml.in (about) 1 # Copyright (c) 2019 Ericsson Eurolab Deutschland GmbH 2 # 3 # SPDX-License-Identifier: Apache-2.0 4 # 5 6 # XXX: WARNING: this file is auto-generated. 7 # XXX: 8 # XXX: Source file: "@CONFIG_CLH_IN@" 9 # XXX: Project: 10 # XXX: Name: @PROJECT_NAME@ 11 # XXX: Type: @PROJECT_TYPE@ 12 13 [hypervisor.clh] 14 path = "@CLHPATH@" 15 kernel = "@KERNELPATH_CLH@" 16 image = "@IMAGEPATH@" 17 18 # Optional space-separated list of options to pass to the guest kernel. 19 # For example, use `kernel_params = "vsyscall=emulate"` if you are having 20 # trouble running pre-2.15 glibc. 21 # 22 # WARNING: - any parameter specified here will take priority over the default 23 # parameter value of the same name used to start the virtual machine. 24 # Do not set values here unless you understand the impact of doing so as you 25 # may stop the virtual machine from booting. 26 # To see the list of default parameters, enable hypervisor debug, create a 27 # container and look for 'default-kernel-parameters' log entries. 28 kernel_params = "@KERNELPARAMS@" 29 30 # Default number of vCPUs per SB/VM: 31 # unspecified or 0 --> will be set to @DEFVCPUS@ 32 # < 0 --> will be set to the actual number of physical cores 33 # > 0 <= number of physical cores --> will be set to the specified number 34 # > number of physical cores --> will be set to the actual number of physical cores 35 default_vcpus = 1 36 37 # Default maximum number of vCPUs per SB/VM: 38 # unspecified or == 0 --> will be set to the actual number of physical cores or to the maximum number 39 # of vCPUs supported by KVM if that number is exceeded 40 # > 0 <= number of physical cores --> will be set to the specified number 41 # > number of physical cores --> will be set to the actual number of physical cores or to the maximum number 42 # of vCPUs supported by KVM if that number is exceeded 43 # WARNING: Depending of the architecture, the maximum number of vCPUs supported by KVM is used when 44 # the actual number of physical cores is greater than it. 45 # WARNING: Be aware that this value impacts the virtual machine's memory footprint and CPU 46 # the hotplug functionality. For example, `default_maxvcpus = 240` specifies that until 240 vCPUs 47 # can be added to a SB/VM, but the memory footprint will be big. Another example, with 48 # `default_maxvcpus = 8` the memory footprint will be small, but 8 will be the maximum number of 49 # vCPUs supported by the SB/VM. In general, we recommend that you do not edit this variable, 50 # unless you know what are you doing. 51 default_maxvcpus = @DEFMAXVCPUS@ 52 53 # Default memory size in MiB for SB/VM. 54 # If unspecified then it will be set @DEFMEMSZ@ MiB. 55 default_memory = @DEFMEMSZ@ 56 57 # Default memory slots per SB/VM. 58 # If unspecified then it will be set @DEFMEMSLOTS@. 59 # This is will determine the times that memory will be hotadded to sandbox/VM. 60 #memory_slots = @DEFMEMSLOTS@ 61 62 # Path to vhost-user-fs daemon. 63 virtio_fs_daemon = "@DEFVIRTIOFSDAEMON@" 64 65 # Default size of DAX cache in MiB 66 virtio_fs_cache_size = @DEFVIRTIOFSCACHESIZE@ 67 68 # cloud-hypervisor prefers virtiofs caching (dax) for performance reasons 69 virtio_fs_cache = "always" 70 71 # Block storage driver to be used for the hypervisor in case the container 72 # rootfs is backed by a block device. This is virtio-scsi, virtio-blk 73 # or nvdimm. 74 block_device_driver = "virtio-blk" 75 76 # This option changes the default hypervisor and kernel parameters 77 # to enable debug output where available. This extra output is added 78 # to the proxy logs, but only when proxy debug is also enabled. 79 # 80 # Default false 81 #enable_debug = true 82 83 [proxy.@PROJECT_TYPE@] 84 path = "@PROXYPATH@" 85 86 # If enabled, proxy messages will be sent to the system log 87 # (default: disabled) 88 #enable_debug = true 89 90 [shim.@PROJECT_TYPE@] 91 path = "@SHIMPATH@" 92 93 # If enabled, shim messages will be sent to the system log 94 # (default: disabled) 95 #enable_debug = true 96 97 # If enabled, the shim will create opentracing.io traces and spans. 98 # (See https://www.jaegertracing.io/docs/getting-started). 99 # 100 # Note: By default, the shim runs in a separate network namespace. Therefore, 101 # to allow it to send trace details to the Jaeger agent running on the host, 102 # it is necessary to set 'disable_new_netns=true' so that it runs in the host 103 # network namespace. 104 # 105 # (default: disabled) 106 #enable_tracing = true 107 108 109 [agent.@PROJECT_TYPE@] 110 # If enabled, make the agent display debug-level messages. 111 # (default: disabled) 112 #enable_debug = true 113 114 # Enable agent tracing. 115 # 116 # If enabled, the default trace mode is "dynamic" and the 117 # default trace type is "isolated". The trace mode and type are set 118 # explicity with the `trace_type=` and `trace_mode=` options. 119 # 120 # Notes: 121 # 122 # - Tracing is ONLY enabled when `enable_tracing` is set: explicitly 123 # setting `trace_mode=` and/or `trace_type=` without setting `enable_tracing` 124 # will NOT activate agent tracing. 125 # 126 # - See https://github.com/kata-containers/agent/blob/master/TRACING.md for 127 # full details. 128 # 129 # (default: disabled) 130 #enable_tracing = true 131 # 132 #trace_mode = "dynamic" 133 #trace_type = "isolated" 134 135 136 [netmon] 137 # If enabled, the network monitoring process gets started when the 138 # sandbox is created. This allows for the detection of some additional 139 # network being added to the existing network namespace, after the 140 # sandbox has been created. 141 # (default: disabled) 142 #enable_netmon = true 143 144 # Specify the path to the netmon binary. 145 path = "@NETMONPATH@" 146 147 # If enabled, netmon messages will be sent to the system log 148 # (default: disabled) 149 #enable_debug = true 150 151 152 [runtime] 153 # If enabled, the runtime will log additional debug messages to the 154 # system log 155 # (default: disabled) 156 #enable_debug = true 157 # 158 # Internetworking model 159 # Determines how the VM should be connected to the 160 # the container network interface 161 # Options: 162 # 163 # - bridged (Deprecated) 164 # Uses a linux bridge to interconnect the container interface to 165 # the VM. Works for most cases except macvlan and ipvlan. 166 # ***NOTE: This feature has been deprecated with plans to remove this 167 # feature in the future. Please use other network models listed below. 168 # 169 # 170 # - macvtap 171 # Used when the Container network interface can be bridged using 172 # macvtap. 173 # 174 # - none 175 # Used when customize network. Only creates a tap device. No veth pair. 176 # 177 # - tcfilter 178 # Uses tc filter rules to redirect traffic from the network interface 179 # provided by plugin to a tap interface connected to the VM. 180 # 181 internetworking_model="@DEFNETWORKMODEL_CLH@" 182 183 # disable guest seccomp 184 # Determines whether container seccomp profiles are passed to the virtual 185 # machine and applied by the kata agent. If set to true, seccomp is not applied 186 # within the guest 187 # (default: true) 188 disable_guest_seccomp=@DEFDISABLEGUESTSECCOMP@ 189 190 # If enabled, the runtime will create opentracing.io traces and spans. 191 # (See https://www.jaegertracing.io/docs/getting-started). 192 # (default: disabled) 193 #enable_tracing = true 194 195 # If enabled, the runtime will not create a network namespace for shim and hypervisor processes. 196 # This option may have some potential impacts to your host. It should only be used when you know what you're doing. 197 # `disable_new_netns` conflicts with `enable_netmon` 198 # `disable_new_netns` conflicts with `internetworking_model=bridged` and `internetworking_model=macvtap`. It works only 199 # with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge 200 # (like OVS) directly. 201 # If you are using docker, `disable_new_netns` only works with `docker run --net=none` 202 # (default: false) 203 #disable_new_netns = true 204 205 # if enabled, the runtime will add all the kata processes inside one dedicated cgroup. 206 # The container cgroups in the host are not created, just one single cgroup per sandbox. 207 # The runtime caller is free to restrict or collect cgroup stats of the overall Kata sandbox. 208 # The sandbox cgroup path is the parent cgroup of a container with the PodSandbox annotation. 209 # The sandbox cgroup is constrained if there is no container type annotation. 210 # See: https://godoc.org/github.com/kata-containers/runtime/virtcontainers#ContainerType 211 sandbox_cgroup_only=@DEFSANDBOXCGROUPONLY@ 212 213 # Enabled experimental feature list, format: ["a", "b"]. 214 # Experimental features are features not stable enough for production, 215 # they may break compatibility, and are prepared for a big version bump. 216 # Supported experimental features: 217 # (default: []) 218 experimental=@DEFAULTEXPFEATURES@