Hugepages are not allocated when pod is deployed with k8s using kata-runtime

Description of problem
Now it is trying to allocate hugepage the pod deployed in k8s using kata-runtime.
The yaml file used to distribute the pod is shown below.
apiVersion: v1
kind: Pod
metadata:
  name: testpod-dpdk
  annotations:
    io.kubernetes.cri.untrusted-workload: "true"
spec:
  containers:
  - name: dpdk-test
    image: parkhi/dpdk-event-pipeline
    imagePullPolicy: IfNotPresent
    command: [ "/bin/bash", "-c", "--" ]
    args: [ "while true; do sleep 300000; done;" ]
    volumeMounts:
    - mountPath: /dev/hugepages
      name: hugepage
      readOnly: False
    - mountPath: /var/proc
      name: memproc
      readOnly: False
    resources:
      requests:
        cpu: "60"
        memory: "1Gi"
        hugepages-1Gi: "1Gi"
        intel.com/intel_sriov_dpdk_A: "1"
      limits:
        cpu: "60"
        memory: "1Gi"
        hugepages-1Gi: "1Gi"
        intel.com/intel_sriov_dpdk_A: "1"
    securityContext:
      capabilities:
        add:
          ["IPC_LOCK"]
      runAsUser: 0
      privileged: false
  volumes:
  - name: hugepage
    hostPath:
      path: /dev/hugepages
      type: Directory
  - name: memproc
    hostPath:
      path: /proc
      type: Directory

Currently hugepages of host status is
[HOST device - worker node]
$ cat /proc/meminfo | grep Huge

AnonHugePages:    151552 kB
HugePages_Total:      16
HugePages_Free:       16
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:    1048576 kB

kata-conatiner's configuration.toml info is
[HOST device - worker node]
$ cat configuration.toml | grep huge
# Enable huge pages for VM RAM, default false
# being allocated using huge pages.
enable_hugepages = true

when i deployed the pod with the yaml, and the pod describe info is
[master node]
$ kubectl describe pods testpod-dpdk

Name:         testpod-dpdk
Namespace:    default
Priority:     0
Node:         vran/<IP_ADDRESS>
Start Time:   Mon, 07 Oct 2019 10:55:54 +0900
Labels:       <none>
Annotations:  io.kubernetes.cri.untrusted-workload: true
              k8s.v1.cni.cncf.io/networks-status:
                [{
                    "name": "cbr0",
                    "ips": [
                        "<IP_ADDRESS>"
                    ],
                    "default": true,
                    "dns": {}
                }]
Status:       Running
IP:           <IP_ADDRESS>
Containers:
  dpdk-test:
    Container ID:  containerd://b2861aee23ad1e5077594bc3a907642e09afd2ac012fd581928f5a785131f5f7
    Image:         parkhi/dpdk-event-pipeline
    Image ID:      docker.io/parkhi/dpdk-event-pipeline@sha256:23c28171782f446f82a300029bbfcc71b049b5491f5020561d457254bdfac3d1
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/bash
      -c
      --
    Args:
      while true; do sleep 300000; done;
    State:          Running
      Started:      Mon, 07 Oct 2019 10:56:04 +0900
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:                           60
      hugepages-1Gi:                 1Gi
      intel.com/intel_sriov_dpdk_A:  1
      memory:                        1Gi
    Requests:
      cpu:                           60
      hugepages-1Gi:                 1Gi
      intel.com/intel_sriov_dpdk_A:  1
      memory:                        1Gi
    Environment:                     <none>
    Mounts:
      /dev/hugepages from hugepage (rw)
      /var/proc from memproc (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-vgb6d (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  hugepage:
    Type:          HostPath (bare host directory volume)
    Path:          /dev/hugepages
    HostPathType:  Directory
  memproc:
    Type:          HostPath (bare host directory volume)
    Path:          /proc
    HostPathType:  Directory
  default-token-vgb6d:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-vgb6d
    Optional:    false
QoS Class:       Guaranteed
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  88s   default-scheduler  Successfully assigned default/testpod-dpdk to vran
  Normal  Pulled     1s    kubelet, vran      Container image "parkhi/dpdk-event-pipeline" already present on machine
  Normal  Created    1s    kubelet, vran      Created container dpdk-test
  Normal  Started    0s    kubelet, vran      Started container dpdk-test

From the information in describe, there seems to be no problem with the deployment to k8s.
i can't find hugepages info in /proc/meminfo, when i join to pod's bin/bash which is deployed
[master node]
$ kubectl exec -it testpod-dpdk -- /bin/bash

[pod]
root@testpod-dpdk:~/dpdk/pktgen-dpdk# cat /proc/meminfo | grep Huge
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
Hugetlb:               0 kB

As you can see from the yaml file above, the proc information of the guest is bound to the pod when the pod is deployed so that the information on the guest's huge page can be checked.
[pod]
root@testpod-dpdk:/var/proc# cat meminfo | grep Huge
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
Hugetlb:               0 kB

You can see that hugepage is not allocated in the deployed guest and pod.
But on host you can see that hugepage is allocated.
[HOST device - worker node]
$ cat /proc/meminfo | grep Huge
AnonHugePages:    321536 kB
HugePages_Total:      16
HugePages_Free:       13
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:    1048576 kB

The reason why 1Gi hugepages * 3 are allocated here is 1*hugepage requested from the pod and 2048Mi default memory(2 * hugepage) allocated to qemu.
What's missing from the allocation of hugepages through kata-runtime?
Expected result
[pod]
root@testpod-dpdk:~/dpdk/pktgen-dpdk# cat /proc/meminfo | grep Huge
HugePages_Total:       1
HugePages_Free:        1
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       1048576 kB
Hugetlb:               0 kB

Actual result
[pod]
root@testpod-dpdk:~/dpdk/pktgen-dpdk# cat /proc/meminfo | grep Huge
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
Hugetlb:               0 kB

[kata.log]

Show kata-collect-data.sh details

Meta details
Running kata-collect-data.sh version 1.9.0-alpha2 (commit 264d7563b3b8cfee2c22272030f7a81914208005) at 2019-10-29.13:09:46.157783017+0900.

Runtime is /bin/kata-runtime.
kata-env
Output of "/bin/kata-runtime kata-env":
[Meta]
  Version = "1.0.23"

[Runtime]
  Debug = true
  Trace = false
  DisableGuestSeccomp = true
  DisableNewNetNs = false
  SandboxCgroupOnly = false
  Path = "/usr/bin/kata-runtime"
  [Runtime.Version]
    Semver = "1.9.0-alpha2"
    Commit = "264d7563b3b8cfee2c22272030f7a81914208005"
    OCI = "1.0.1-dev"
  [Runtime.Config]
    Path = "/etc/kata-containers/configuration.toml"

[Hypervisor]
  MachineType = "pc"
  Version = "QEMU emulator version 4.1.0\nCopyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers"
  Path = "/usr/bin/qemu-vanilla-system-x86_64"
  BlockDeviceDriver = "virtio-scsi"
  EntropySource = "/dev/urandom"
  Msize9p = 8192
  MemorySlots = 10
  Debug = true
  UseVSock = false
  SharedFS = "virtio-9p"

[Image]
  Path = "/usr/share/kata-containers/kata-containers-image_clearlinux_1.9.0-alpha2_agent_cfec1b64f4.img"

[Kernel]
  Path = "/usr/share/kata-containers/vmlinuz-<IP_ADDRESS>-54.1.container"
  Parameters = "systemd.unit=kata-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket agent.log=debug agent.log=debug initcall_debug"

[Initrd]
  Path = ""

[Proxy]
  Type = "kataProxy"
  Version = "kata-proxy version 1.9.0-alpha2-85504b8"
  Path = "/usr/libexec/kata-containers/kata-proxy"
  Debug = true

[Shim]
  Type = "kataShim"
  Version = "kata-shim version 1.9.0-alpha2-6bd5e6b"
  Path = "/usr/libexec/kata-containers/kata-shim"
  Debug = true

[Agent]
  Type = "kata"
  Debug = true
  Trace = false
  TraceMode = ""
  TraceType = ""

[Host]
  Kernel = "3.10.0-1062.1.2.el7.x86_64"
  Architecture = "amd64"
  VMContainerCapable = true
  SupportVSocks = true
  [Host.Distro]
    Name = "CentOS Linux"
    Version = "7"
  [Host.CPU]
    Vendor = "GenuineIntel"
    Model = "Intel(R) Xeon(R) Gold 6148 CPU @ 2.40GHz"

[Netmon]
  Version = "kata-netmon version 1.9.0-alpha2"
  Path = "/usr/libexec/kata-containers/kata-netmon"
  Debug = true
  Enable = false

Runtime config files
Runtime default config files
/etc/kata-containers/configuration.toml
/usr/share/defaults/kata-containers/configuration.toml

Runtime config file contents
Output of "cat "/etc/kata-containers/configuration.toml"":
# Copyright (c) 2017-2019 Intel Corporation
#
# SPDX-License-Identifier: Apache-2.0
#

# XXX: WARNING: this file is auto-generated.
# XXX:
# XXX: Source file: "cli/config/configuration-qemu.toml.in"
# XXX: Project:
# XXX:   Name: Kata Containers
# XXX:   Type: kata

[hypervisor.qemu]
path = "/usr/bin/qemu-vanilla-system-x86_64"
kernel = "/usr/share/kata-containers/vmlinuz.container"
image = "/usr/share/kata-containers/kata-containers.img"
machine_type = "pc"

# Optional space-separated list of options to pass to the guest kernel.
# For example, use `kernel_params = "vsyscall=emulate"` if you are having
# trouble running pre-2.15 glibc.
#
# WARNING: - any parameter specified here will take priority over the default
# parameter value of the same name used to start the virtual machine.
# Do not set values here unless you understand the impact of doing so as you
# may stop the virtual machine from booting.
# To see the list of default parameters, enable hypervisor debug, create a
# container and look for 'default-kernel-parameters' log entries.
kernel_params = " agent.log=debug initcall_debug"

# Path to the firmware.
# If you want that qemu uses the default firmware leave this option empty
firmware = ""

# Machine accelerators
# comma-separated list of machine accelerators to pass to the hypervisor.
# For example, `machine_accelerators = "nosmm,nosmbus,nosata,nopit,static-prt,nofw"`
machine_accelerators=""

# Default number of vCPUs per SB/VM:
# unspecified or 0                --> will be set to 1
# < 0                             --> will be set to the actual number of physical cores
# > 0 <= number of physical cores --> will be set to the specified number
# > number of physical cores      --> will be set to the actual number of physical cores
default_vcpus = 80

# Default maximum number of vCPUs per SB/VM:
# unspecified or == 0             --> will be set to the actual number of physical cores or to the maximum number
#                                     of vCPUs supported by KVM if that number is exceeded
# > 0 <= number of physical cores --> will be set to the specified number
# > number of physical cores      --> will be set to the actual number of physical cores or to the maximum number
#                                     of vCPUs supported by KVM if that number is exceeded
# WARNING: Depending of the architecture, the maximum number of vCPUs supported by KVM is used when
# the actual number of physical cores is greater than it.
# WARNING: Be aware that this value impacts the virtual machine's memory footprint and CPU
# the hotplug functionality. For example, `default_maxvcpus = 240` specifies that until 240 vCPUs
# can be added to a SB/VM, but the memory footprint will be big. Another example, with
# `default_maxvcpus = 8` the memory footprint will be small, but 8 will be the maximum number of
# vCPUs supported by the SB/VM. In general, we recommend that you do not edit this variable,
# unless you know what are you doing.
default_maxvcpus = 80

# Bridges can be used to hot plug devices.
# Limitations:
# * Currently only pci bridges are supported
# * Until 30 devices per bridge can be hot plugged.
# * Until 5 PCI bridges can be cold plugged per VM.
#   This limitation could be a bug in qemu or in the kernel
# Default number of bridges per SB/VM:
# unspecified or 0   --> will be set to 1
# > 1 <= 5           --> will be set to the specified number
# > 5                --> will be set to 5
default_bridges = 1

# Default memory size in MiB for SB/VM.
# If unspecified then it will be set 2048 MiB.
default_memory = 2048
#
# Default memory slots per SB/VM.
# If unspecified then it will be set 10.
# This is will determine the times that memory will be hotadded to sandbox/VM.
#memory_slots = 10

# The size in MiB will be plused to max memory of hypervisor.
# It is the memory address space for the NVDIMM devie.
# If set block storage driver (block_device_driver) to "nvdimm",
# should set memory_offset to the size of block device.
# Default 0
#memory_offset = 0

# Disable block device from being used for a container's rootfs.
# In case of a storage driver like devicemapper where a container's
# root file system is backed by a block device, the block device is passed
# directly to the hypervisor for performance reasons.
# This flag prevents the block device from being passed to the hypervisor,
# 9pfs is used instead to pass the rootfs.
disable_block_device_use = false

# Shared file system type:
#   - virtio-9p (default)
#   - virtio-fs
shared_fs = "virtio-9p"

# Path to vhost-user-fs daemon.
virtio_fs_daemon = "/usr/bin/virtiofsd-x86_64"

# Default size of DAX cache in MiB
virtio_fs_cache_size = 1024

# Extra args for virtiofsd daemon
#
# Format example:
#   ["-o", "arg1=xxx,arg2", "-o", "hello world", "--arg3=yyy"]
#
# see `virtiofsd -h` for possible options.
virtio_fs_extra_args = []

# Cache mode:
#
#  - none
#    Metadata, data, and pathname lookup are not cached in guest. They are
#    always fetched from host and any changes are immediately pushed to host.
#
#  - auto
#    Metadata and pathname lookup cache expires after a configured amount of
#    time (default is 1 second). Data is cached while the file is open (close
#    to open consistency).
#
#  - always
#    Metadata, data, and pathname lookup are cached in guest and never expire.
virtio_fs_cache = "always"

# Block storage driver to be used for the hypervisor in case the container
# rootfs is backed by a block device. This is virtio-scsi, virtio-blk
# or nvdimm.
block_device_driver = "virtio-scsi"

# Specifies cache-related options will be set to block devices or not.
# Default false
#block_device_cache_set = true

# Specifies cache-related options for block devices.
# Denotes whether use of O_DIRECT (bypass the host page cache) is enabled.
# Default false
#block_device_cache_direct = true

# Specifies cache-related options for block devices.
# Denotes whether flush requests for the device are ignored.
# Default false
#block_device_cache_noflush = true

# Enable iothreads (data-plane) to be used. This causes IO to be
# handled in a separate IO thread. This is currently only implemented
# for SCSI.
#
enable_iothreads = false

# Enable pre allocation of VM RAM, default false
# Enabling this will result in lower container density
# as all of the memory will be allocated and locked
# This is useful when you want to reserve all the memory
# upfront or in the cases where you want memory latencies
# to be very predictable
# Default false
enable_mem_prealloc = true

# Enable huge pages for VM RAM, default false
# Enabling this will result in the VM memory
# being allocated using huge pages.
# This is useful when you want to use vhost-user network
# stacks within the container. This will automatically
# result in memory pre allocation
# enable_hugepages = true

# Enable file based guest memory support. The default is an empty string which
# will disable this feature. In the case of virtio-fs, this is enabled
# automatically and '/dev/shm' is used as the backing folder.
# This option will be ignored if VM templating is enabled.
#file_mem_backend = ""

# Enable swap of vm memory. Default false.
# The behaviour is undefined if mem_prealloc is also set to true
#enable_swap = true

# This option changes the default hypervisor and kernel parameters
# to enable debug output where available. This extra output is added
# to the proxy logs, but only when proxy debug is also enabled.
#
# Default false
enable_debug = true

# Disable the customizations done in the runtime when it detects
# that it is running on top a VMM. This will result in the runtime
# behaving as it would when running on bare metal.
#
#disable_nesting_checks = true

# This is the msize used for 9p shares. It is the number of bytes
# used for 9p packet payload.
#msize_9p = 8192

# If true and vsocks are supported, use vsocks to communicate directly
# with the agent and no proxy is started, otherwise use unix
# sockets and start a proxy to communicate with the agent.
# Default false
#use_vsock = true

# VFIO devices are hotplugged on a bridge by default.
# Enable hotplugging on root bus. This may be required for devices with
# a large PCI bar, as this is a current limitation with hotplugging on
# a bridge. This value is valid for "pc" machine type.
# Default false
#hotplug_vfio_on_root_bus = true

# If host doesn't support vhost_net, set to true. Thus we won't create vhost fds for nics.
# Default false
#disable_vhost_net = true
#
# Default entropy source.
# The path to a host source of entropy (including a real hardware RNG)
# /dev/urandom and /dev/random are two main options.
# Be aware that /dev/random is a blocking source of entropy.  If the host
# runs out of entropy, the VMs boot time will increase leading to get startup
# timeouts.
# The source of entropy /dev/urandom is non-blocking and provides a
# generally acceptable source of entropy. It should work well for pretty much
# all practical purposes.
#entropy_source= "/dev/urandom"

# Path to OCI hook binaries in the *guest rootfs*.
# This does not affect host-side hooks which must instead be added to
# the OCI spec passed to the runtime.
#
# You can create a rootfs with hooks by customizing the osbuilder scripts:
# https://github.com/kata-containers/osbuilder
#
# Hooks must be stored in a subdirectory of guest_hook_path according to their
# hook type, i.e. "guest_hook_path/{prestart,postart,poststop}".
# The agent will scan these directories for executable files and add them, in
# lexicographical order, to the lifecycle of the guest container.
# Hooks are executed in the runtime namespace of the guest. See the official documentation:
# https://github.com/opencontainers/runtime-spec/blob/v1.0.1/config.md#posix-platform-hooks
# Warnings will be logged if any error is encountered will scanning for hooks,
# but it will not abort container execution.
#guest_hook_path = "/usr/share/oci/hooks"

[factory]
# VM templating support. Once enabled, new VMs are created from template
# using vm cloning. They will share the same initial kernel, initramfs and
# agent memory by mapping it readonly. It helps speeding up new container
# creation and saves a lot of memory if there are many kata containers running
# on the same host.
#
# When disabled, new VMs are created from scratch.
#
# Note: Requires "initrd=" to be set ("image=" is not supported).
#
# Default false
#enable_template = true

# Specifies the path of template.
#
# Default "/run/vc/vm/template"
#template_path = "/run/vc/vm/template"

# The number of caches of VMCache:
# unspecified or == 0   --> VMCache is disabled
# > 0                   --> will be set to the specified number
#
# VMCache is a function that creates VMs as caches before using it.
# It helps speed up new container creation.
# The function consists of a server and some clients communicating
# through Unix socket.  The protocol is gRPC in protocols/cache/cache.proto.
# The VMCache server will create some VMs and cache them by factory cache.
# It will convert the VM to gRPC format and transport it when gets
# requestion from clients.
# Factory grpccache is the VMCache client.  It will request gRPC format
# VM and convert it back to a VM.  If VMCache function is enabled,
# kata-runtime will request VM from factory grpccache when it creates
# a new sandbox.
#
# Default 0
#vm_cache_number = 0

# Specify the address of the Unix socket that is used by VMCache.
#
# Default /var/run/kata-containers/cache.sock
#vm_cache_endpoint = "/var/run/kata-containers/cache.sock"

[proxy.kata]
path = "/usr/libexec/kata-containers/kata-proxy"

# If enabled, proxy messages will be sent to the system log
# (default: disabled)
enable_debug = true

[shim.kata]
path = "/usr/libexec/kata-containers/kata-shim"

# If enabled, shim messages will be sent to the system log
# (default: disabled)
enable_debug = true

# If enabled, the shim will create opentracing.io traces and spans.
# (See https://www.jaegertracing.io/docs/getting-started).
#
# Note: By default, the shim runs in a separate network namespace. Therefore,
# to allow it to send trace details to the Jaeger agent running on the host,
# it is necessary to set 'disable_new_netns=true' so that it runs in the host
# network namespace.
#
# (default: disabled)
#enable_tracing = true

[agent.kata]
# If enabled, make the agent display debug-level messages.
# (default: disabled)
enable_debug = true

# Enable agent tracing.
#
# If enabled, the default trace mode is "dynamic" and the
# default trace type is "isolated". The trace mode and type are set
# explicity with the `trace_type=` and `trace_mode=` options.
#
# Notes:
#
# - Tracing is ONLY enabled when `enable_tracing` is set: explicitly
#   setting `trace_mode=` and/or `trace_type=` without setting `enable_tracing`
#   will NOT activate agent tracing.
#
# - See https://github.com/kata-containers/agent/blob/master/TRACING.md for
#   full details.
#
# (default: disabled)
#enable_tracing = true
#
#trace_mode = "dynamic"
#trace_type = "isolated"

# Comma separated list of kernel modules and their parameters.
# These modules will be loaded in the guest kernel using modprobe(8).
# The following example can be used to load two kernel modules with parameters
#  - kernel_modules=["e1000e InterruptThrottleRate=3000,3000,3000 EEE=1", "i915 enable_ppgtt=0"]
# The first word is considered as the module name and the rest as its parameters.
# Container will not be started when:
#  * A kernel module is specified and the modprobe command is not installed in the guest
#    or it fails loading the module.
#  * The module is not available in the guest or it doesn't met the guest kernel
#    requirements, like architecture and version.
#
kernel_modules=[]

[netmon]
# If enabled, the network monitoring process gets started when the
# sandbox is created. This allows for the detection of some additional
# network being added to the existing network namespace, after the
# sandbox has been created.
# (default: disabled)
#enable_netmon = true

# Specify the path to the netmon binary.
path = "/usr/libexec/kata-containers/kata-netmon"

# If enabled, netmon messages will be sent to the system log
# (default: disabled)
enable_debug = true

[runtime]
# If enabled, the runtime will log additional debug messages to the
# system log
# (default: disabled)
enable_debug = true
#
# Internetworking model
# Determines how the VM should be connected to the
# the container network interface
# Options:
#
#   - bridged (Deprecated)
#     Uses a linux bridge to interconnect the container interface to
#     the VM. Works for most cases except macvlan and ipvlan.
#     ***NOTE: This feature has been deprecated with plans to remove this
#     feature in the future. Please use other network models listed below.
#
#   - macvtap
#     Used when the Container network interface can be bridged using
#     macvtap.
#
#   - none
#     Used when customize network. Only creates a tap device. No veth pair.
#
#   - tcfilter
#     Uses tc filter rules to redirect traffic from the network interface
#     provided by plugin to a tap interface connected to the VM.
#
internetworking_model="tcfilter"

# disable guest seccomp
# Determines whether container seccomp profiles are passed to the virtual
# machine and applied by the kata agent. If set to true, seccomp is not applied
# within the guest
# (default: true)
disable_guest_seccomp=true

# If enabled, the runtime will create opentracing.io traces and spans.
# (See https://www.jaegertracing.io/docs/getting-started).
# (default: disabled)
#enable_tracing = true

# If enabled, the runtime will not create a network namespace for shim and hypervisor processes.
# This option may have some potential impacts to your host. It should only be used when you know what you're doing.
# `disable_new_netns` conflicts with `enable_netmon`
# `disable_new_netns` conflicts with `internetworking_model=bridged` and `internetworking_model=macvtap`. It works only
# with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge
# (like OVS) directly.
# If you are using docker, `disable_new_netns` only works with `docker run --net=none`
# (default: false)
#disable_new_netns = true

# if enabled, the runtime will add all the kata processes inside one dedicated cgroup.
# The container cgroups in the host are not created, just one single cgroup per sandbox.
# The sandbox cgroup is not constrained by the runtime
# The runtime caller is free to restrict or collect cgroup stats of the overall Kata sandbox.
# The sandbox cgroup path is the parent cgroup of a container with the PodSandbox annotation.
# See: https://godoc.org/github.com/kata-containers/runtime/virtcontainers#ContainerType
#sandbox_cgroup_only=true

# Enabled experimental feature list, format: ["a", "b"].
# Experimental features are features not stable enough for production,
# They may break compatibility, and are prepared for a big version bump.
# Supported experimental features:
# 1. "newstore": new persist storage driver which breaks backward compatibility,
#				expected to move out of experimental in 2.0.0.
# (default: [])
experimental=[]

Output of "cat "/usr/share/defaults/kata-containers/configuration.toml"":
# Copyright (c) 2017-2019 Intel Corporation
#
# SPDX-License-Identifier: Apache-2.0
#

# XXX: WARNING: this file is auto-generated.
# XXX:
# XXX: Source file: "cli/config/configuration-qemu.toml.in"
# XXX: Project:
# XXX:   Name: Kata Containers
# XXX:   Type: kata

[hypervisor.qemu]
path = "/usr/bin/qemu-vanilla-system-x86_64"
kernel = "/usr/share/kata-containers/vmlinuz.container"
image = "/usr/share/kata-containers/kata-containers.img"
machine_type = "pc"

# Optional space-separated list of options to pass to the guest kernel.
# For example, use `kernel_params = "vsyscall=emulate"` if you are having
# trouble running pre-2.15 glibc.
#
# WARNING: - any parameter specified here will take priority over the default
# parameter value of the same name used to start the virtual machine.
# Do not set values here unless you understand the impact of doing so as you
# may stop the virtual machine from booting.
# To see the list of default parameters, enable hypervisor debug, create a
# container and look for 'default-kernel-parameters' log entries.
kernel_params = ""

# Path to the firmware.
# If you want that qemu uses the default firmware leave this option empty
firmware = ""

# Machine accelerators
# comma-separated list of machine accelerators to pass to the hypervisor.
# For example, `machine_accelerators = "nosmm,nosmbus,nosata,nopit,static-prt,nofw"`
machine_accelerators=""

# Default number of vCPUs per SB/VM:
# unspecified or 0                --> will be set to 1
# < 0                             --> will be set to the actual number of physical cores
# > 0 <= number of physical cores --> will be set to the specified number
# > number of physical cores      --> will be set to the actual number of physical cores
default_vcpus = 80

# Default maximum number of vCPUs per SB/VM:
# unspecified or == 0             --> will be set to the actual number of physical cores or to the maximum number
#                                     of vCPUs supported by KVM if that number is exceeded
# > 0 <= number of physical cores --> will be set to the specified number
# > number of physical cores      --> will be set to the actual number of physical cores or to the maximum number
#                                     of vCPUs supported by KVM if that number is exceeded
# WARNING: Depending of the architecture, the maximum number of vCPUs supported by KVM is used when
# the actual number of physical cores is greater than it.
# WARNING: Be aware that this value impacts the virtual machine's memory footprint and CPU
# the hotplug functionality. For example, `default_maxvcpus = 240` specifies that until 240 vCPUs
# can be added to a SB/VM, but the memory footprint will be big. Another example, with
# `default_maxvcpus = 8` the memory footprint will be small, but 8 will be the maximum number of
# vCPUs supported by the SB/VM. In general, we recommend that you do not edit this variable,
# unless you know what are you doing.
default_maxvcpus = 80

# Bridges can be used to hot plug devices.
# Limitations:
# * Currently only pci bridges are supported
# * Until 30 devices per bridge can be hot plugged.
# * Until 5 PCI bridges can be cold plugged per VM.
#   This limitation could be a bug in qemu or in the kernel
# Default number of bridges per SB/VM:
# unspecified or 0   --> will be set to 1
# > 1 <= 5           --> will be set to the specified number
# > 5                --> will be set to 5
default_bridges = 1

# Default memory size in MiB for SB/VM.
# If unspecified then it will be set 2048 MiB.
default_memory = 2048
#
# Default memory slots per SB/VM.
# If unspecified then it will be set 10.
# This is will determine the times that memory will be hotadded to sandbox/VM.
#memory_slots = 10

# The size in MiB will be plused to max memory of hypervisor.
# It is the memory address space for the NVDIMM devie.
# If set block storage driver (block_device_driver) to "nvdimm",
# should set memory_offset to the size of block device.
# Default 0
#memory_offset = 0

# Disable block device from being used for a container's rootfs.
# In case of a storage driver like devicemapper where a container's
# root file system is backed by a block device, the block device is passed
# directly to the hypervisor for performance reasons.
# This flag prevents the block device from being passed to the hypervisor,
# 9pfs is used instead to pass the rootfs.
disable_block_device_use = false

# Shared file system type:
#   - virtio-9p (default)
#   - virtio-fs
shared_fs = "virtio-9p"

# Path to vhost-user-fs daemon.
virtio_fs_daemon = "/usr/bin/virtiofsd-x86_64"

# Default size of DAX cache in MiB
virtio_fs_cache_size = 1024

# Extra args for virtiofsd daemon
#
# Format example:
#   ["-o", "arg1=xxx,arg2", "-o", "hello world", "--arg3=yyy"]
#
# see `virtiofsd -h` for possible options.
virtio_fs_extra_args = []

# Cache mode:
#
#  - none
#    Metadata, data, and pathname lookup are not cached in guest. They are
#    always fetched from host and any changes are immediately pushed to host.
#
#  - auto
#    Metadata and pathname lookup cache expires after a configured amount of
#    time (default is 1 second). Data is cached while the file is open (close
#    to open consistency).
#
#  - always
#    Metadata, data, and pathname lookup are cached in guest and never expire.
virtio_fs_cache = "always"

# Block storage driver to be used for the hypervisor in case the container
# rootfs is backed by a block device. This is virtio-scsi, virtio-blk
# or nvdimm.
block_device_driver = "virtio-scsi"

# Specifies cache-related options will be set to block devices or not.
# Default false
#block_device_cache_set = true

# Specifies cache-related options for block devices.
# Denotes whether use of O_DIRECT (bypass the host page cache) is enabled.
# Default false
#block_device_cache_direct = true

# Specifies cache-related options for block devices.
# Denotes whether flush requests for the device are ignored.
# Default false
#block_device_cache_noflush = true

# Enable iothreads (data-plane) to be used. This causes IO to be
# handled in a separate IO thread. This is currently only implemented
# for SCSI.
#
enable_iothreads = false

# Enable pre allocation of VM RAM, default false
# Enabling this will result in lower container density
# as all of the memory will be allocated and locked
# This is useful when you want to reserve all the memory
# upfront or in the cases where you want memory latencies
# to be very predictable
# Default false
enable_mem_prealloc = true

# Enable huge pages for VM RAM, default false
# Enabling this will result in the VM memory
# being allocated using huge pages.
# This is useful when you want to use vhost-user network
# stacks within the container. This will automatically
# result in memory pre allocation
# enable_hugepages = true

# Enable file based guest memory support. The default is an empty string which
# will disable this feature. In the case of virtio-fs, this is enabled
# automatically and '/dev/shm' is used as the backing folder.
# This option will be ignored if VM templating is enabled.
#file_mem_backend = ""

# Enable swap of vm memory. Default false.
# The behaviour is undefined if mem_prealloc is also set to true
#enable_swap = true

# This option changes the default hypervisor and kernel parameters
# to enable debug output where available. This extra output is added
# to the proxy logs, but only when proxy debug is also enabled.
#
# Default false
enable_debug = true

# Disable the customizations done in the runtime when it detects
# that it is running on top a VMM. This will result in the runtime
# behaving as it would when running on bare metal.
#
#disable_nesting_checks = true

# This is the msize used for 9p shares. It is the number of bytes
# used for 9p packet payload.
#msize_9p = 8192

# If true and vsocks are supported, use vsocks to communicate directly
# with the agent and no proxy is started, otherwise use unix
# sockets and start a proxy to communicate with the agent.
# Default false
#use_vsock = true

# VFIO devices are hotplugged on a bridge by default.
# Enable hotplugging on root bus. This may be required for devices with
# a large PCI bar, as this is a current limitation with hotplugging on
# a bridge. This value is valid for "pc" machine type.
# Default false
#hotplug_vfio_on_root_bus = true

# If host doesn't support vhost_net, set to true. Thus we won't create vhost fds for nics.
# Default false
#disable_vhost_net = true
#
# Default entropy source.
# The path to a host source of entropy (including a real hardware RNG)
# /dev/urandom and /dev/random are two main options.
# Be aware that /dev/random is a blocking source of entropy.  If the host
# runs out of entropy, the VMs boot time will increase leading to get startup
# timeouts.
# The source of entropy /dev/urandom is non-blocking and provides a
# generally acceptable source of entropy. It should work well for pretty much
# all practical purposes.
#entropy_source= "/dev/urandom"

# Path to OCI hook binaries in the *guest rootfs*.
# This does not affect host-side hooks which must instead be added to
# the OCI spec passed to the runtime.
#
# You can create a rootfs with hooks by customizing the osbuilder scripts:
# https://github.com/kata-containers/osbuilder
#
# Hooks must be stored in a subdirectory of guest_hook_path according to their
# hook type, i.e. "guest_hook_path/{prestart,postart,poststop}".
# The agent will scan these directories for executable files and add them, in
# lexicographical order, to the lifecycle of the guest container.
# Hooks are executed in the runtime namespace of the guest. See the official documentation:
# https://github.com/opencontainers/runtime-spec/blob/v1.0.1/config.md#posix-platform-hooks
# Warnings will be logged if any error is encountered will scanning for hooks,
# but it will not abort container execution.
#guest_hook_path = "/usr/share/oci/hooks"

[factory]
# VM templating support. Once enabled, new VMs are created from template
# using vm cloning. They will share the same initial kernel, initramfs and
# agent memory by mapping it readonly. It helps speeding up new container
# creation and saves a lot of memory if there are many kata containers running
# on the same host.
#
# When disabled, new VMs are created from scratch.
#
# Note: Requires "initrd=" to be set ("image=" is not supported).
#
# Default false
#enable_template = true

# Specifies the path of template.
#
# Default "/run/vc/vm/template"
#template_path = "/run/vc/vm/template"

# The number of caches of VMCache:
# unspecified or == 0   --> VMCache is disabled
# > 0                   --> will be set to the specified number
#
# VMCache is a function that creates VMs as caches before using it.
# It helps speed up new container creation.
# The function consists of a server and some clients communicating
# through Unix socket.  The protocol is gRPC in protocols/cache/cache.proto.
# The VMCache server will create some VMs and cache them by factory cache.
# It will convert the VM to gRPC format and transport it when gets
# requestion from clients.
# Factory grpccache is the VMCache client.  It will request gRPC format
# VM and convert it back to a VM.  If VMCache function is enabled,
# kata-runtime will request VM from factory grpccache when it creates
# a new sandbox.
#
# Default 0
#vm_cache_number = 0

# Specify the address of the Unix socket that is used by VMCache.
#
# Default /var/run/kata-containers/cache.sock
#vm_cache_endpoint = "/var/run/kata-containers/cache.sock"

[proxy.kata]
path = "/usr/libexec/kata-containers/kata-proxy"

# If enabled, proxy messages will be sent to the system log
# (default: disabled)
#enable_debug = true

[shim.kata]
path = "/usr/libexec/kata-containers/kata-shim"

# If enabled, shim messages will be sent to the system log
# (default: disabled)
#enable_debug = true

# If enabled, the shim will create opentracing.io traces and spans.
# (See https://www.jaegertracing.io/docs/getting-started).
#
# Note: By default, the shim runs in a separate network namespace. Therefore,
# to allow it to send trace details to the Jaeger agent running on the host,
# it is necessary to set 'disable_new_netns=true' so that it runs in the host
# network namespace.
#
# (default: disabled)
#enable_tracing = true

[agent.kata]
# If enabled, make the agent display debug-level messages.
# (default: disabled)
#enable_debug = true

# Enable agent tracing.
#
# If enabled, the default trace mode is "dynamic" and the
# default trace type is "isolated". The trace mode and type are set
# explicity with the `trace_type=` and `trace_mode=` options.
#
# Notes:
#
# - Tracing is ONLY enabled when `enable_tracing` is set: explicitly
#   setting `trace_mode=` and/or `trace_type=` without setting `enable_tracing`
#   will NOT activate agent tracing.
#
# - See https://github.com/kata-containers/agent/blob/master/TRACING.md for
#   full details.
#
# (default: disabled)
#enable_tracing = true
#
#trace_mode = "dynamic"
#trace_type = "isolated"

# Comma separated list of kernel modules and their parameters.
# These modules will be loaded in the guest kernel using modprobe(8).
# The following example can be used to load two kernel modules with parameters
#  - kernel_modules=["e1000e InterruptThrottleRate=3000,3000,3000 EEE=1", "i915 enable_ppgtt=0"]
# The first word is considered as the module name and the rest as its parameters.
# Container will not be started when:
#  * A kernel module is specified and the modprobe command is not installed in the guest
#    or it fails loading the module.
#  * The module is not available in the guest or it doesn't met the guest kernel
#    requirements, like architecture and version.
#
kernel_modules=[]

[netmon]
# If enabled, the network monitoring process gets started when the
# sandbox is created. This allows for the detection of some additional
# network being added to the existing network namespace, after the
# sandbox has been created.
# (default: disabled)
#enable_netmon = true

# Specify the path to the netmon binary.
path = "/usr/libexec/kata-containers/kata-netmon"

# If enabled, netmon messages will be sent to the system log
# (default: disabled)
#enable_debug = true

[runtime]
# If enabled, the runtime will log additional debug messages to the
# system log
# (default: disabled)
#enable_debug = true
#
# Internetworking model
# Determines how the VM should be connected to the
# the container network interface
# Options:
#
#   - bridged (Deprecated)
#     Uses a linux bridge to interconnect the container interface to
#     the VM. Works for most cases except macvlan and ipvlan.
#     ***NOTE: This feature has been deprecated with plans to remove this
#     feature in the future. Please use other network models listed below.
#
#   - macvtap
#     Used when the Container network interface can be bridged using
#     macvtap.
#
#   - none
#     Used when customize network. Only creates a tap device. No veth pair.
#
#   - tcfilter
#     Uses tc filter rules to redirect traffic from the network interface
#     provided by plugin to a tap interface connected to the VM.
#
internetworking_model="tcfilter"

# disable guest seccomp
# Determines whether container seccomp profiles are passed to the virtual
# machine and applied by the kata agent. If set to true, seccomp is not applied
# within the guest
# (default: true)
disable_guest_seccomp=true

# If enabled, the runtime will create opentracing.io traces and spans.
# (See https://www.jaegertracing.io/docs/getting-started).
# (default: disabled)
#enable_tracing = true

# If enabled, the runtime will not create a network namespace for shim and hypervisor processes.
# This option may have some potential impacts to your host. It should only be used when you know what you're doing.
# `disable_new_netns` conflicts with `enable_netmon`
# `disable_new_netns` conflicts with `internetworking_model=bridged` and `internetworking_model=macvtap`. It works only
# with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge
# (like OVS) directly.
# If you are using docker, `disable_new_netns` only works with `docker run --net=none`
# (default: false)
#disable_new_netns = true

# if enabled, the runtime will add all the kata processes inside one dedicated cgroup.
# The container cgroups in the host are not created, just one single cgroup per sandbox.
# The sandbox cgroup is not constrained by the runtime
# The runtime caller is free to restrict or collect cgroup stats of the overall Kata sandbox.
# The sandbox cgroup path is the parent cgroup of a container with the PodSandbox annotation.
# See: https://godoc.org/github.com/kata-containers/runtime/virtcontainers#ContainerType
#sandbox_cgroup_only=true

# Enabled experimental feature list, format: ["a", "b"].
# Experimental features are features not stable enough for production,
# They may break compatibility, and are prepared for a big version bump.
# Supported experimental features:
# 1. "newstore": new persist storage driver which breaks backward compatibility,
#				expected to move out of experimental in 2.0.0.
# (default: [])
experimental=[]

KSM throttler
version
Output of "/usr/lib/systemd/system/kata-ksm-throttler.service --version":
./usr/bin/kata-collect-data.sh: line 178: /usr/lib/systemd/system/kata-ksm-throttler.service: 허가 거부

Output of "/usr/libexec/kata-ksm-throttler/kata-ksm-throttler --version":
kata-ksm-throttler version 1.9.0-alpha2-7254a7e

systemd service
Image details
---
osbuilder:
  url: "https://github.com/kata-containers/osbuilder"
  version: "unknown"
rootfs-creation-time: "2019-09-18T15:34:48.349388249+0000Z"
description: "osbuilder rootfs"
file-format-version: "0.0.2"
architecture: "x86_64"
base-distro:
  name: "Clear"
  version: "31040"
  packages:
    default:
      - "chrony"
      - "iptables-bin"
      - "kmod-bin"
      - "libudev0-shim"
      - "systemd"
      - "util-linux-bin"
    extra:

agent:
  url: "https://github.com/kata-containers/agent"
  name: "kata-agent"
  version: "1.9.0-alpha2-cfec1b64f4d32aeac92d70f87afb72d2b194a45d"
  agent-is-init-daemon: "no"

Initrd details
No initrd

Logfiles
Runtime logs
No recent runtime problems found in system journal.
Proxy logs
No recent proxy problems found in system journal.
Shim logs
No recent shim problems found in system journal.
Throttler logs
No recent throttler problems found in system journal.

Container manager details
Have docker
Docker
Output of "docker version":
Client: Docker Engine - Community
 Version:           19.03.2
 API version:       1.40
 Go version:        go1.12.8
 Git commit:        6a30dfc
 Built:             Thu Aug 29 05:28:55 2019
 OS/Arch:           linux/amd64
 Experimental:      false
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Output of "docker info":
Client:
 Debug Mode: false

Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info

Output of "systemctl show docker":
Type=notify
Restart=always
NotifyAccess=main
RestartUSec=2s
TimeoutStartUSec=0
TimeoutStopUSec=0
WatchdogUSec=0
WatchdogTimestampMonotonic=0
StartLimitInterval=60000000
StartLimitBurst=3
StartLimitAction=none
FailureAction=none
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=0
ControlPID=0
FileDescriptorStoreMax=0
StatusErrno=0
Result=success
ExecMainStartTimestampMonotonic=0
ExecMainExitTimestampMonotonic=0
ExecMainPID=0
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/bin/dockerd ; argv[]=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
ExecReload={ path=/bin/kill ; argv[]=/bin/kill -s HUP $MAINPID ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
Slice=system.slice
MemoryCurrent=18446744073709551615
TasksCurrent=18446744073709551615
Delegate=yes
CPUAccounting=no
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=infinity
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLimit=18446744073709551615
DevicePolicy=auto
TasksAccounting=no
TasksMax=18446744073709551615
UMask=0022
LimitCPU=18446744073709551615
LimitFSIZE=18446744073709551615
LimitDATA=18446744073709551615
LimitSTACK=18446744073709551615
LimitCORE=18446744073709551615
LimitRSS=18446744073709551615
LimitNOFILE=18446744073709551615
LimitAS=18446744073709551615
LimitNPROC=18446744073709551615
LimitMEMLOCK=65536
LimitLOCKS=18446744073709551615
LimitSIGPENDING=697748
LimitMSGQUEUE=819200
LimitNICE=0
LimitRTPRIO=0
LimitRTTIME=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SecureBits=0
CapabilityBoundingSet=18446744073709551615
AmbientCapabilities=0
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
PrivateDevices=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
KillMode=process
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=docker.service
Names=docker.service
Requires=system.slice docker.socket basic.target
Wants=network-online.target
BindsTo=containerd.service
ConsistsOf=docker.socket
Conflicts=shutdown.target
Before=shutdown.target
After=containerd.service firewalld.service docker.socket network-online.target basic.target system.slice systemd-journald.socket
TriggeredBy=docker.socket
Documentation=https://docs.docker.com
Description=Docker Application Container Engine
LoadState=loaded
ActiveState=inactive
SubState=dead
FragmentPath=/usr/lib/systemd/system/docker.service
UnitFileState=disabled
UnitFilePreset=disabled
InactiveExitTimestampMonotonic=0
ActiveEnterTimestampMonotonic=0
ActiveExitTimestampMonotonic=0
InactiveEnterTimestampMonotonic=0
CanStart=yes
CanStop=yes
CanReload=yes
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
IgnoreOnSnapshot=no
NeedDaemonReload=no
JobTimeoutUSec=0
JobTimeoutAction=none
ConditionResult=no
AssertResult=no
ConditionTimestampMonotonic=0
AssertTimestampMonotonic=0
Transient=no

Have kubectl
Kubernetes
Output of "kubectl version":
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.2", GitCommit:"f6278300bebbb750328ac16ee6dd3aa7d3549568", GitTreeState:"clean", BuildDate:"2019-08-05T09:23:26Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
The connection to the server localhost:8080 was refused - did you specify the right host or port?

Output of "kubectl config view":
apiVersion: v1
clusters: []
contexts: []
current-context: ""
kind: Config
preferences: {}
users: []

Output of "systemctl show kubelet":
Type=simple
Restart=always
NotifyAccess=none
RestartUSec=10s
TimeoutStartUSec=1min 30s
TimeoutStopUSec=1min 30s
WatchdogUSec=0
WatchdogTimestamp=수 2019-10-23 23:10:16 KST
WatchdogTimestampMonotonic=638397340
StartLimitInterval=0
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=8925
ControlPID=0
FileDescriptorStoreMax=0
StatusErrno=0
Result=success
ExecMainStartTimestamp=수 2019-10-23 23:10:16 KST
ExecMainStartTimestampMonotonic=638397234
ExecMainExitTimestampMonotonic=0
ExecMainPID=8925
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/bin/kubelet ; argv[]=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS $KUBELET_RUNTIME_ARGS ; ignore_errors=no ; start_time=[수 2019-10-23 23:10:16 KST] ; stop_time=[n/a] ; pid=8925 ; code=(null) ; status=0/0 }
Slice=system.slice
ControlGroup=/system.slice/kubelet.service
MemoryCurrent=81170432
TasksCurrent=71
Delegate=no
CPUAccounting=no
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=infinity
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLimit=18446744073709551615
DevicePolicy=auto
TasksAccounting=no
TasksMax=18446744073709551615
Environment=KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf KUBELET_CONFIG_ARGS=--config=/var/lib/kubelet/config.yaml KUBELET_RUNTIME_ARGS=--container-runtime=remote --runtime-request-timeout=15m --container-runtime-endpoint=unix:///run/containerd/containerd.sock KUBELET_EXTRA_ARGS=--fail-swap-on=false --cgroup-driver=systemd
EnvironmentFile=/var/lib/kubelet/kubeadm-flags.env (ignore_errors=yes)
EnvironmentFile=/etc/default/kubelet (ignore_errors=yes)
UMask=0022
LimitCPU=18446744073709551615
LimitFSIZE=18446744073709551615
LimitDATA=18446744073709551615
LimitSTACK=18446744073709551615
LimitCORE=18446744073709551615
LimitRSS=18446744073709551615
LimitNOFILE=4096
LimitAS=18446744073709551615
LimitNPROC=697748
LimitMEMLOCK=65536
LimitLOCKS=18446744073709551615
LimitSIGPENDING=697748
LimitMSGQUEUE=819200
LimitNICE=0
LimitRTPRIO=0
LimitRTTIME=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SecureBits=0
CapabilityBoundingSet=18446744073709551615
AmbientCapabilities=0
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
PrivateDevices=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
KillMode=control-group
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=kubelet.service
Names=kubelet.service
Requires=system.slice basic.target
WantedBy=multi-user.target
Conflicts=shutdown.target
Before=shutdown.target multi-user.target
After=system.slice systemd-journald.socket basic.target
Documentation=https://kubernetes.io/docs/
Description=kubelet: The Kubernetes Node Agent
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/usr/lib/systemd/system/kubelet.service
DropInPaths=/etc/systemd/system/kubelet.service.d/10-kubeadm.conf
UnitFileState=enabled
UnitFilePreset=disabled
InactiveExitTimestamp=수 2019-10-23 23:10:16 KST
InactiveExitTimestampMonotonic=638397390
ActiveEnterTimestamp=수 2019-10-23 23:10:16 KST
ActiveEnterTimestampMonotonic=638397390
ActiveExitTimestamp=수 2019-10-23 23:10:06 KST
ActiveExitTimestampMonotonic=628129744
InactiveEnterTimestamp=수 2019-10-23 23:10:16 KST
InactiveEnterTimestampMonotonic=638369304
CanStart=yes
CanStop=yes
CanReload=no
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
IgnoreOnSnapshot=no
NeedDaemonReload=no
JobTimeoutUSec=0
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=수 2019-10-23 23:10:16 KST
ConditionTimestampMonotonic=638378493
AssertTimestamp=수 2019-10-23 23:10:16 KST
AssertTimestampMonotonic=638378494
Transient=no

No crio
Have containerd
containerd
Output of "containerd --version":
containerd containerd.io 1.2.6 894b81a4b802e4eb2a91d1ce216b8817763c29fb

Output of "systemctl show containerd":
Type=simple
Restart=no
NotifyAccess=none
RestartUSec=100ms
TimeoutStartUSec=1min 30s
TimeoutStopUSec=1min 30s
WatchdogUSec=0
WatchdogTimestamp=수 2019-10-23 23:10:10 KST
WatchdogTimestampMonotonic=632209541
StartLimitInterval=10000000
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=8849
ControlPID=0
FileDescriptorStoreMax=0
StatusErrno=0
Result=success
ExecMainStartTimestamp=수 2019-10-23 23:10:10 KST
ExecMainStartTimestampMonotonic=632209475
ExecMainExitTimestampMonotonic=0
ExecMainPID=8849
ExecMainCode=0
ExecMainStatus=0
ExecStartPre={ path=/sbin/modprobe ; argv[]=/sbin/modprobe overlay ; ignore_errors=yes ; start_time=[수 2019-10-23 23:10:10 KST] ; stop_time=[수 2019-10-23 23:10:10 KST] ; pid=8846 ; code=exited ; status=0 }
ExecStart={ path=/usr/bin/containerd ; argv[]=/usr/bin/containerd ; ignore_errors=no ; start_time=[수 2019-10-23 23:10:10 KST] ; stop_time=[n/a] ; pid=8849 ; code=(null) ; status=0/0 }
Slice=system.slice
ControlGroup=/system.slice/containerd.service
MemoryCurrent=3808153600
TasksCurrent=318
Delegate=yes
CPUAccounting=no
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=infinity
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLimit=18446744073709551615
DevicePolicy=auto
TasksAccounting=no
TasksMax=18446744073709551615
UMask=0022
LimitCPU=18446744073709551615
LimitFSIZE=18446744073709551615
LimitDATA=18446744073709551615
LimitSTACK=18446744073709551615
LimitCORE=18446744073709551615
LimitRSS=18446744073709551615
LimitNOFILE=1048576
LimitAS=18446744073709551615
LimitNPROC=18446744073709551615
LimitMEMLOCK=65536
LimitLOCKS=18446744073709551615
LimitSIGPENDING=697748
LimitMSGQUEUE=819200
LimitNICE=0
LimitRTPRIO=0
LimitRTTIME=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SecureBits=0
CapabilityBoundingSet=18446744073709551615
AmbientCapabilities=0
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
PrivateDevices=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
KillMode=process
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=containerd.service
Names=containerd.service
Requires=system.slice basic.target
Conflicts=shutdown.target
Before=shutdown.target
After=system.slice systemd-journald.socket network.target basic.target
Documentation=https://containerd.io
Description=containerd container runtime
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/usr/lib/systemd/system/containerd.service
UnitFileState=disabled
UnitFilePreset=disabled
InactiveExitTimestamp=수 2019-10-23 23:10:10 KST
InactiveExitTimestampMonotonic=632176285
ActiveEnterTimestamp=수 2019-10-23 23:10:10 KST
ActiveEnterTimestampMonotonic=632209583
ActiveExitTimestampMonotonic=0
InactiveEnterTimestampMonotonic=0
CanStart=yes
CanStop=yes
CanReload=no
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
IgnoreOnSnapshot=no
NeedDaemonReload=no
JobTimeoutUSec=0
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=수 2019-10-23 23:10:10 KST
ConditionTimestampMonotonic=632161615
AssertTimestamp=수 2019-10-23 23:10:10 KST
AssertTimestampMonotonic=632161616
Transient=no

Output of "cat /etc/containerd/config.toml":
root = "/var/lib/containerd"
state = "/run/containerd"
oom_score = 0

[grpc]
  address = "/run/containerd/containerd.sock"
  uid = 0
  gid = 0
  max_recv_message_size = 16777216
  max_send_message_size = 16777216

[debug]
  address = ""
  uid = 0
  gid = 0
  level = ""

[metrics]
  address = ""
  grpc_histogram = false

[cgroup]
  path = ""

[plugins]
  [plugins.cgroups]
    no_prometheus = false
  [plugins.cri]
    stream_server_address = "<IP_ADDRESS>"
    stream_server_port = "0"
    enable_selinux = false
    sandbox_image = "k8s.gcr.io/pause:3.1"
    stats_collect_period = 10
    systemd_cgroup = true
    enable_tls_streaming = false
    max_container_log_line_size = 16384
    [plugins.cri.containerd]
      snapshotter = "overlayfs"
      no_pivot = false
      [plugins.cri.containerd.default_runtime]
        runtime_type = "io.containerd.runtime.v1.linux"
        runtime_engine = ""
        runtime_root = ""
      [plugins.cri.containerd.untrusted_workload_runtime]
        runtime_type = "io.containerd.kata.v2"
        runtime_engine = ""
        runtime_root = ""
    [plugins.cri.cni]
      bin_dir = "/opt/cni/bin"
      conf_dir = "/etc/cni/net.d"
      conf_template = ""
    [plugins.cri.registry]
      [plugins.cri.registry.mirrors]
        [plugins.cri.registry.mirrors."insecure.registry.io"]
          endpoint = ["https://<IP_ADDRESS>:5000"]
    [plugins.cri.x509_key_pair_streaming]
      tls_cert_file = ""
      tls_key_file = ""
  [plugins.diff-service]
    default = ["walking"]
  [plugins.linux]
    shim = "containerd-shim"
    runtime = "runc"
    runtime_root = ""
    no_shim = false
    shim_debug = false
  [plugins.opt]
    path = "/opt/containerd"
  [plugins.restart]
    interval = "10s"
  [plugins.scheduler]
    pause_threshold = 0.02
    deletion_threshold = 0
    mutation_threshold = 100
    schedule_delay = "0s"
    startup_delay = "100ms"

Packages
No dpkg
Have rpm
Output of "rpm -qa|egrep "(cc-oci-runtimecc-runtimerunv|kata-proxy|kata-runtime|kata-shim|kata-ksm-throttler|kata-containers-image|linux-container|qemu-)"":
qemu-user-2.0.0-1.el7.6.x86_64
kata-ksm-throttler-1.9.0~alpha2-42.1.x86_64
qemu-system-unicore32-2.0.0-1.el7.6.x86_64
qemu-system-s390x-2.0.0-1.el7.6.x86_64
qemu-system-arm-2.0.0-1.el7.6.x86_64
qemu-2.0.0-1.el7.6.x86_64
qemu-system-xtensa-2.0.0-1.el7.6.x86_64
qemu-system-microblaze-2.0.0-1.el7.6.x86_64
qemu-system-x86-2.0.0-1.el7.6.x86_64
libvirt-daemon-driver-qemu-4.5.0-23.el7_7.1.x86_64
qemu-lite-bin-2.11.0+git.87517afd72-41.1.x86_64
qemu-lite-2.11.0+git.87517afd72-41.1.x86_64
kata-containers-image-1.9.0~alpha2-37.1.x86_64
kata-linux-container-<IP_ADDRESS>-54.1.x86_64
qemu-system-sh4-2.0.0-1.el7.6.x86_64
qemu-system-lm32-2.0.0-1.el7.6.x86_64
qemu-lite-data-2.11.0+git.87517afd72-41.1.x86_64
qemu-kvm-common-1.5.3-167.el7_7.1.x86_64
kata-shim-1.9.0~alpha2-36.1.x86_64
qemu-system-mips-2.0.0-1.el7.6.x86_64
qemu-system-m68k-2.0.0-1.el7.6.x86_64
qemu-kvm-1.5.3-167.el7_7.1.x86_64
qemu-vanilla-data-4.1.0+git.9e06029aea-41.1.x86_64
qemu-common-2.0.0-1.el7.6.x86_64
qemu-guest-agent-2.12.0-3.el7.x86_64
qemu-img-1.5.3-167.el7_7.1.x86_64
qemu-system-moxie-2.0.0-1.el7.6.x86_64
qemu-vanilla-4.1.0+git.9e06029aea-41.1.x86_64
kata-runtime-1.9.0~alpha2-59.1.x86_64
qemu-system-alpha-2.0.0-1.el7.6.x86_64
kata-proxy-bin-1.9.0~alpha2-38.1.x86_64
kata-shim-bin-1.9.0~alpha2-36.1.x86_64
qemu-system-cris-2.0.0-1.el7.6.x86_64
ipxe-roms-qemu-20180825-2.git133f4c.el7.noarch
kata-proxy-1.9.0~alpha2-38.1.x86_64
qemu-system-or32-2.0.0-1.el7.6.x86_64
qemu-vanilla-bin-4.1.0+git.9e06029aea-41.1.x86_64

please review this issue.

Thanks for raising @wParkhi.
Please:

Enable full debug.
Re-run the commands.
Run sudo kata-collect-data.sh > /tmp/kata.log.
Review the contents of kata.log.
Paste the contents of kata.log directly into this issue (as requested in the issue template).

@wParkhi This is a missing feature in Kata right now. See this: https://github.com/kata-containers/runtime/issues/1548

@jodh-intel
I attached my kata.log file. Thanks :)

How is it going this issue?

@jodh-intel
How is it going?

@jodh-intel
I've tried to allocate hugepages using same pod described at above issue.
Hugepages is still not allocated on Kata-containers' container.
There added more details what I tried.

[Host machine] It is worker node's memory Info regarding hugepages.
$ cat /proc/meminfo | grep Huge
AnonHugePages:         0 kB
HugePages_Total:      32
HugePages_Free:       32
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:    1048576 kB

[Host machine] It is worker node's kata configuration.toml.
Added kernel_params to update grub for hugepages, and enabled hugepages option.
I add the more kernel params on toml file about configuration of hugepasges.
$ cat configuration.toml | grep huge
kernel_params = "transparent_hugepage=never default_hugepagesz=1G hugepagesz=1G hugepages=1"
# Enable huge pages for VM RAM, default false
# being allocated using huge pages.
enable_hugepages = true

[Actual Result] Deployed Pod successfully.
$ kubectl get pods
NAME             READY   STATUS    RESTARTS   AGE
bind-devs-dpdk   1/1     Running   0          2m22s

But, even though Guest kernel is configured hugepage 1G, total hugepages still marked as zero.
$ crictl exec -it ${CONTAINER_ID} /bin/bash
root@bind-devs-dpdk:~/dpdk/pktgen-dpdk# cat /proc/meminfo | grep Huge
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:    1048576 kB
Hugetlb:               0 kB

Guest Kernel dmesg is shown the error about hugepages allocation failed.
First line of below dmesg, it seems to be fail allocation hugepage as 1G, because KVM has only 2G memory by default.
And, it seems to no enough memory on boot time for allocation hugepage as 1G.
Second one, I have no idea for that, I guess occured error when hot-plugging hugepage which is described on pod description.
root@bind-devs-dpdk:~/dpdk/pktgen-dpdk# dmesg | grep huge
[    0.080376] HugeTLB: allocating 1 of page size 1.00 GiB failed.  Only allocated 0 hugepages.
[    0.338225] systemd[80]: dev-hugepages.mount: Failed to connect stdout to the journal socket, ignoring: No such file or directory

It looks like Host machine allocated 3G hugepage to VM(2G) and Container(1G).
$ cat /proc/meminfo | grep Huge
AnonHugePages:         0 kB
HugePages_Total:      32
HugePages_Free:       29
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:    1048576 kB

I've tried on the ver. 1.10 of kata-runtime.
If there is any updates for this issue, please let me know about that.

[Expected Result]
$ crictl exec -it ${CONTAINER_ID} /bin/bash
root@bind-devs-dpdk:~/dpdk/pktgen-dpdk# cat /proc/meminfo | grep Huge
HugePages_Total:       1
HugePages_Free:        1
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:    1048576 kB
Hugetlb:               0 kB

@wansuyoo Taking a look at this.

@amshinde There is no further information ?

@wansuyoo I thought I had commented on this yesterday, but dont see the update here.
Anyways, I tried your setup and have been looking at identifying the gaps that need to be fixed wrt to having support for hugetable cgroups as well. Handling hugetable cgroups is going to require some additional implementation in Kata.
But we can start with just making sure hugepages work with Kata.
So, I tried a setup similar to yours but just using 2MB huge pages. I was able to see hugepages assigned to Kata.
Here is the pod yaml:
apiVersion: v1
kind: Pod
metadata:
  name: testpod-kata-huge
spec:
  runtimeClassName: kata
  containers:
  - name: dpdk-test
    image: debian
    imagePullPolicy: IfNotPresent
    command: [ "/bin/bash", "-c", "--" ]
    args: [ "while true; do sleep 300000; done;" ]
    volumeMounts:
    - mountPath: /dev/hugepages
      name: hugepage
      readOnly: False
    resources:
      requests:
        memory: "512Mi"
        hugepages-2Mi: "512Mi"
      limits:
        memory: "512Mi"
        hugepages-2Mi: "512Mi"
    securityContext:
      capabilities:
        add:
          ["IPC_LOCK"]
      runAsUser: 0
      privileged: false
  volumes:
  - name: hugepage
    hostPath:
      path: /dev/hugepages
      type: Directory

Note, you should not need to pass the host side /proc to Kata, this would not work as well since Kata container runs inside a VM having its own proc filesystem.
Note, instead of using annotation of untrusted workloads, I have used RuntimeClass()https://github.com/kata-containers/documentation/blob/3ed59ee50eea5bf4163d760a7a01221e2b4d343d/how-to/containerd-kata.md#kubernetes-runtimeclass feature that is meant to replace using annotations.
You can use either.
Changes made to Kata configuration:
cat /usr/share/defaults/kata-containers/configuration.toml | grep huge
kernel_params = "default_hugepagesz=2M hugepagesz=2M hugepages=256"
# Enable huge pages for VM RAM, default false
# being allocated using huge pages.
enable_hugepages = true

With this :
kubectl exec -it  testpod-kata-huge bash
root@testpod-kata-huge:/# mount | grep hugepages
hugetlbfs on /dev/hugepages type hugetlbfs (rw,nosuid,nodev,noexec,relatime,pagesize=2M)
root@testpod-kata-huge:/# cat /proc/meminfo | grep Huge
HugePages_Total:     256
HugePages_Free:      256
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
Hugetlb:          524288 kB

As you can see 256 pages of 2MB side have been allocated inside Kata.
Can you try with this again, and let me know if you are seeing issues. In that case, can you paste the output of kata-collect.sh script present in the runtime repository.
Resource Accounting:
One thing to note is, in case of Kata today, all of qemu and guest memory is allocated with huge pages as well as seen here:
root       6682  0.5  0.3 2186204 56404 ?       Sl   09:09   0:03 /usr/bin/qemu-vanilla-system-x86_64 -name sandbox-5b65581ded297d10b40076aa128eb5df542980627e26e47facd8bb092f8f6cf1 -uuid 9e226ad9-4a81-40bf-bd90-1420d4414bec -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host,pmu=off -qmp unix:/run/vc/vm/5b65581ded297d10b40076aa128eb5df542980627e26e47facd8bb092f8f6cf1/qmp.sock,server,nowait -m 1024M,slots=10,maxmem=17041M -device pci-bridge,bus=pci.0,id=pci-bridge-0,chassis_nr=1,shpc=on,addr=2,romfile= -device virtio-serial-pci,disable-modern=true,id=serial0,romfile= -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/vc/vm/5b65581ded297d10b40076aa128eb5df542980627e26e47facd8bb092f8f6cf1/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/kata-containers/kata-containers-image_clearlinux_1.10.0-alpha1_agent_c87f497312.img,size=134217728 -device virtio-scsi-pci,id=scsi0,disable-modern=true,romfile= -object rng-random,id=rng0,filename=/dev/urandom -device virtio-rng,rng=rng0,romfile= -device virtserialport,chardev=charch0,id=channel0,name=agent.channel.0 -chardev socket,id=charch0,path=/run/vc/vm/5b65581ded297d10b40076aa128eb5df542980627e26e47facd8bb092f8f6cf1/kata.sock,server,nowait -device virtio-9p-pci,disable-modern=true,fsdev=extra-9p-kataShared,mount_tag=kataShared,romfile= -fsdev local,id=extra-9p-kataShared,path=/run/kata-containers/shared/sandboxes/5b65581ded297d10b40076aa128eb5df542980627e26e47facd8bb092f8f6cf1,security_model=none -netdev tap,id=network-0,vhost=on,vhostfds=3,fds=4 -device driver=virtio-net-pci,netdev=network-0,mac=d2:11:e7:1f:40:81,disable-modern=true,mq=on,vectors=4,romfile= -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -object memory-backend-file,id=dimm1,size=1024M,mem-path=/dev/hugepages -numa node,memdev=dimm1 -kernel /usr/share/kata-containers/vmlinuz-<IP_ADDRESS>-44.container -append tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k console=hvc0 console=hvc1 iommu=off cryptomgr.notests net.ifnames=0 pci=lastbus=0 root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro ro rootfstype=ext4 debug systemd.show_status=true systemd.log_level=debug panic=1 nr_cpus=4 agent.use_vsock=false systemd.unit=kata-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket agent.log=debug default_hugepagesz=2M hugepagesz=2M hugepages=256 -pidfile /run/vc/vm/5b65581ded297d10b40076aa128eb5df542980627e26e47facd8bb092f8f6cf1/pid -D /run/vc/vm/5b65581ded297d10b40076aa128eb5df542980627e26e47facd8bb092f8f6cf1/qemu.log -smp 1,cores=1,threads=1,sockets=4,maxcpus=4

Note the option -object memory-backend-file,id=dimm1,size=2048M, passed to qemu.
So today if you want to have your app use some amount of hugepages memory say 1G, some part of it will be used by qemu and the guest. As a temporary workaround, you can add the memory overhead required into the huge-page requests in the pod yaml, say assign (1024 + 256 MB) of huge page memory.
I have been looking at ways how we can solve this resource accounting issue for huge pages.
One of the things I have considered is using the PodOverhead feature that we added to kubernetes to account for overhead associated with memory and CPU usage for Kata guest resources. However If we add resource overhead for huge pages in k8s, we are not going to be accounting correctly for regular memory for Kata correctly. This is going to become even more apparent when passing emptyDir based on hugepages to the container. (k8s creates a separate volume backed by hugepages in this case).  I am looking at ways of fixing this, by not backing the entire qemu memory with hugepages to be able to solve the resource accounting issue.
This is described in the issue here: https://github.com/kata-containers/runtime/issues/1548
I shall post my findings on resource accounting as I make some more progress on it.


[UI] User can see scan progress at icon in task bar.

Like we see in memory clean program while cleaning.

If we can't show percent maybe we can just show scanning with spinning ascii character animation like we saw when we do npm i which is :. .:

We cannot not determine how long a scanning process will last. How can we calculate the percentage from?

In that case we just show dot animation as mentioned above without progress bar or percentage number to let user know something running is fine enough.

Here's the lib 🐰  https://github.com/helloIAmPau/node-spinner

Please use ⣯ Spinner 28 of 30 , it will look like this while scanning.

For other state please see https://github.com/rabbots/eyes/issues/8


🦩newest version 🦩

What is this PR About?
update to newest ploigos version.. looks like older versions not in operator catalog
How do we test this?
Provide commands/steps to test this PR.
cc: @redhat-cop/day-in-the-life

/lgtm
/approve


Add a script to download macOS dependencies

@Ramzzzay, could you please prepare a script to download dependencies for macOS to the game directory?

Done by #26.


Registration rewards

(Copying across from old repo).
Allow configurable commands to execute once a user has successfully registered using /register (eg to reward the user with diamonds)

Now possible in v2 using https://namelessmc.com/resources/resource/15-namelessmc-websend/

See #127


Fix Nixops: update boto3, botocore and awscli

Motivation for this change
boto3 is currently broken because it is not compatible with botocore. Since nixops depends on boto3, it is also broken.
awscli is updated to build with the new botocore version.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build nixops awscli pythonPackages.boto3 pythonPackages.botocore

There's already other versions of boto* in staging-next - see https://github.com/NixOS/nixpkgs/pull/90627.
If nixops only works with specific versions of it, and can't keep up,  it'd probably be better if it'd use pinned versions internally.

Oh!
I actually did a Github search but nothing was found because your PR is closed and I didn't think about staging-*.
nixops is just broken because boto3 is broken.
Thanks!


[Catalog V2 UI] On viewing catalogs, OS and arch annotations should be respected

Note: Annotations will be introduced to all charts by the backend team, as prescribed in https://github.com/rancher/rancher/issues/36401.
Note: This issue should not be validated by QA until the backend issue is complete; however, UI can proceed with the changes assuming the defaults for these annotations described in the original ticket for all current charts.
UX Change
When a user visits the catalog, the Rancher UI should grab:

Set of all OSs currently running on nodes in this cluster (hasOS)
Set of all archs used by nodes in this cluster: (hasArch)

Once the charts to be displayed have been returned by the Rancher backend, for each chart Dashboard should:

Get the values of the catalog.cattle.io/permits-os annotation (permitsOS)
Get the values of the catalog.cattle.io/permits-arch annotation (permitsArch)
Validate that hasOS is a subset of permitsOS; if not, do not show the chart.
Validate that hasArch is a subset of permitsArch; if not, do not show the chart.

note: I edited the PR description to use catalog.cattle.io/deploys-on-os instead of catalog.cattle.io/os since catalog.cattle.io/os has an older definition that would break older Rancher setups if we choose to modify what it means.
Description should be up-to-date now with the expectations.


[webview_flutter]WebView doesn't load some Urls and has a blank white screen

Steps to Reproduce
Open the following URL in a webview 'http://attractions.timeout.com/en/11312/search/kirchberg'
Expected results: Webview loads URL as on any other browser
Actual results: Blank screen and no loading
import 'package:flutter/material.dart';
import 'package:webview_flutter/webview_flutter.dart';

class WebViewBug extends StatelessWidget {
  const WebViewBug({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
        appBar: AppBar(),
        body: IgnorePointer(
            child: WebView(
          javascriptMode: JavascriptMode.unrestricted,
          initialUrl:
              'http://attractions.timeout.com/en/11312/search/kirchberg',
        )));
  }
}

Hi @Justus-M, Thanks for filing the issue. Do you see any errors or unusual logs in the console? Please share the output of flutter run n-v and the output of flutter doctor -v.
Also, is this issue on android or IOS?

Hi @Justus-M, Thanks for filing the issue. Do you see any errors or unusual logs in the console? Please share the output of flutter run -v and the output of flutter doctor -v.
Also, is this issue on android or IOS?

Nothing unusual, I faced this issue on iOS but haven't tested on android. Same thing happens on various iOS devices, release and debug, physical and simulator.
Is this not reproducible for you?
I can run flutter run -v when I get home, but I already checked the debug console, url requests, and any other activity. There is no activity, which is the issue. On other browsers this url redirects to another, but this doesn't seem to happen in webview or inappwebview

I am able to reproduce the issue on stable and the master channel. I tried with both http and https, The app has blank white screen. This is reproducible on both ios and android. I tried adding android:networkSecurityConfig to android manifest but the app still has a white screen. Other URLs however load fine.

code sample
import 'package:flutter/material.dart';
import 'package:webview_flutter/webview_flutter.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      title: 'Flutter Google Maps Demo',
      home: NewPage(),
    );
  }
}

class NewPage extends StatefulWidget {
  const NewPage({Key? key}) : super(key: key);

  @override
  State<NewPage> createState() => _NewPageState();
}

class _NewPageState extends State<NewPage> {
  @override
  Widget build(BuildContext context) {
    return const WebView(
      javascriptMode: JavascriptMode.unrestricted,
      initialUrl: 'https://attractions.timeout.com/en/11312/search/kirchberg',
    );
  }
}

I can't reproduce this on iOS. @Justus-M What is your NSAppTransportSecurity setting?
@maheshmnj:

I tried with both http and https

https shouldn't load anything because it doesn't have a valid certificate. What exactly was your application configuration for testing http? You mentioned android:networkSecurityConfig, but not what you set it to.

I can't reproduce this on iOS. @Justus-M What is your NSAppTransportSecurity setting?

@stuartmorgan if you are referring to the Info.plist keys mentioned here (https://developer.apple.com/documentation/bundleresources/information_property_list/nsapptransportsecurity) to circumvent ATS protections, I haven't added any.
If this isn't your question, please let me know what/where you need me to check.. I'm relatively new to flutter

If you haven't added NSAppTransportSecurity exceptions, then this is expected behavior. iOS blocks http: URLs by default (as it says in the documentation you linked to).

But I am not sure how other sites were loading without it e.g https://flutter.dev

That's an https: URL, so doesn't require special allowances.


We should introduce a -APIVersion parameter for Set-PSResourceRepository

Summary of the new feature / enhancement
When a PSResourceRepository is registered, it is assigned an API version (currently  v2 or v3) there may be reasons a user wants to change or correct this version and users should not edit the Repository.xml file so we should introduce a way to update this field
Proposed technical implementation details (optional)
No response

Is the API version for NuGet or PowerShellGet?

NuGet

I don't know much about nuget but doesn't the url determine the API version?

Typically the url does determine the API version, but there are edge cases where we would not know... for example on prem ADO feed would look like local file share to us but would actually be a v3 feed


Nullable array type field / method argument

Added two unit tests in RealNamingTest.xml

renamedField with Nullable array type
renamedMethod with Nullable array type argument
both throw NullReferenceException when creating PineappleTreeView

I messed up my local branch. Please see commit 0088773 only

Thx


[doc] Fix documentation skip method

Fixes https://github.com/rectorphp/rector/issues/8770

@sflanker this fix https://github.com/rectorphp/rector/issues/8770

All checks have passed 🎉 @TomasVotruba I am merging it ;)


refactor: Generalise sign of power lemmas

Generalise the lemmas in Algebra.Parity from LinearOrderedRing to LinearOrderedSemiring + ExistsAddOfLE. This means they now apply to eg ℕ.
Move them to Algebra.GroupPower.Order.
For this to work, I must swap the order of import between Algebra.GroupPower.Order and Algebra.Parity. This means that I need to weaken one assert_not_exists to allow importing Data.Set.Defs. This is inconsequential.

[x] depends on: #12260
[ ] depends on: #12288
[ ] depends on: #12289

I did the minimal amount of fixes, but if you can find something smaller I'm all ears!

This looks good to me. @Ruben-VandeVelde, what exactly would you like to simplify in this PR?

@Vierkantor, it was done. See #12288 and #12289


http0.9: process headers if there are non-space characters

Previously, we fell back on HTTP/0.9 if there was a missing protocol except if the following line contained a colon.
We make libhtp simpler by only switching to HTTP/0.9 if we have only spaces afterwards

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=54982&q=label%3AProj-libhtp&can=2


Casting/assigning a normal function to a function type with-properties results in different references

See example: https://typescripttolua.github.io/play#code/JYOwLgpgTgZghgYwgAgGIFcQICoE8AOKA3gFDLnIAUAlAFzIBuA9sACZkX5RP4D89cELhIBfEiQRMQAZzDIYyALxVqigHxExkmXIBGcKAEZ6GLHkJL5EqbOT6oAJhOYcBFMpjiS9wwDouPJYAzNYyTAA2EL7hTADmlD7+3PjUodIRUTHx9g5JPNRAA

This may not have an elegant solution; If so, it might be best to add this to the caveats in docs, and/or detect and provide a warning in such cases.

Probably the best we can do is disallow assignments of functions without properties to types that have them. We already have assignment validations for all of the self vs noself stuff which covers all the various types of assignments (passing as arguments, etc...), so we can likely add this check there.

Actually, here's a potential solution: instead of creating a table with a __call metamethod, give the function a metatable using debug.setmetatble with __index and __newindex set to the same table. Also add a check in case the function already has a metatable; this can be done with lualib.


[Docs] Add Link to GH Page on README

Background
Despite the recently added v2 documentation reference with great new styles, there did not seem to be a link to the generated output. This PR seeks to save additional googling to hunt down the documentation.
Changes

Updates README.md

Addresses
#115

Thanks!


feat: ✨ Add getBytecode, getBlockNumber, getToken, getFeeHistory, waitForTransactionReceipt - Social Login Controls

Implemented - getBytecode
Corrected & implemented - getBlockNumber & getToken
Modified getAccount to parse more details including connection type. (This still needs some rework in the future to parse the whole connection object from js)
Also added control for social login options besides email

@kaumudpa great !
is this ready for review ?

@Chralu Ready for review - Kindly review & Merge.

@Chralu Changes done according to your inputs - Also implemented 2 new action methods - getFeeHistory & waitForTransactionReceipt .
Kindly review again and let me know if you have further suggestions or its LGTM .

I check this tomorrow morning 👍

Thank you for the fixes - @Chralu

We need the config object similar to what it is in js - We should provide the ability to use different transport methods as well in config - Any ideas how can we achieve that with our lib @Chralu
Shall we create a issue for it?

We need the config object similar to what it is in js - We should provide the ability to use different transport methods as well in config - Any ideas how can we achieve that with our lib @Chralu
Shall we create a issue for it?

It would be great to have that similarity between Dart/JS.
Yes, I think creating an issue is a good idea.


Condotion Builder: Continue work on Usage page

follow on from #4900
follow on from #5426
Resources

Usage template in Figma

Current Usage page (ver 0.4)
Usage guidance in Figma
Notes

Sync with Tracy on the new version
Variants naming consider: Non-Hierarchical, Hierarchical

Deliverable

[ ] Draft of the Conditions builder usage docs

Version 0.6 is done. @janhassel, @amal-k-joy, @kingtraceyj, @RichKummer, @carrenelloyd, @elycheea, @sstrubberg
Once we mark the final review as done, I'll create a separate Figma file for it an label is as final.

Updated all the examples to reflect logical statement and updated design.
Left the note about examples not appearing correctly on the Gatsby version.

Closing for now to track the effort


chore: correct typos docs

I reviewed the entire repository, no more typos found in docs.
Hope this helps streamline the project!
Best regards,
Bilogweb3

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Already fixed in https://github.com/Consensys/gnark-crypto/pull/563. Thanks for opening the PR in any case!


Fix build dispatch warnings

Description
Please include a summary of the change. For large or complex changes please include enough information to introduce your change and explain motivation for it.
Changes proposed in this pull request:

/intelci: run

/intelci: run


CircleCI codecov job is flaky

Seeing these failures in the CircleCI codecov job:
2018-10-08T13:45:33.584403Z	error	tf	Failed to initialize dependency 'policyBackend': listen tcp :1071: bind: address already in use
--- FAIL: TestHTTPLocal (0.00s)
	pilot_test.go:69: unable to satisfy dependency 'policyBackend': listen tcp :1071: bind: address already in use
FAIL```
Examples:
https://circleci.com/gh/istio/istio/210173
https://circleci.com/gh/istio/istio/210247
https://circleci.com/gh/istio/istio/210188
Not all CircleCI codecov jobs are failing.

Please reassign as makes sense.


[forStatement] ANTLR reference grammar is incorrect

The issue
In qasm3Parser.g4#L66
forStatement: FOR scalarType Identifier IN (setExpression | LBRACKET rangeExpression RBRACKET | Identifier) body=statementOrScope;

the grammar state that the iterable (i.e., the thing that will be iterated during the for-loop) is either:

a setExpression
a rangeExpression
an Identifier

whereas the official documentation on for-loop explicitly states that using indexedIdentifiers should be allowed:

It is valid to use an indexing expression (e.g. my_array[1:3]) to arrive at one of the types given above.

How to fix this
Replace Identifier by indexedIdentifier in the forStatement rule.

indexedIdentifier in the ANTLR grammar is a shorthand in the grammar for making certain l-value expressions clearer, whereas this is an r-value expression.  I'm fine to change the grammar (and the corresponding parser), but the targets should probably change to setExpression | LBRACKET rangeExpression RBRACKET | expression instead and the parser should sort out the type safety (the current reference parser only produces an untyped AST at the moment, so it doesn't actually do any type checking).

I will make a PR for this in the near future then. I agree with the l-value/r-value argument here.


Fix #758 - Add precheck when deleting profile

What this PR does / why we need it:
Fix for #758 Add precheck when deleting profile
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Added few test results to verify deletion.
root@shruthi-VirtualBox:~/go/src/github.com/opensds/opensds# curl -X DELETE http://<IP_ADDRESS>:50040/v1beta/e93b4c0934da416eb9c8d120c5d04d96/profiles/638658b0-5952-47f9-bad6-ae9531a33d51
{"code":400,"message":"There are dependent volumes : [11vol vol4 vol3 vol3 vol1 vol2] for the specified profile 638658b0-5952-47f9-bad6-ae9531a33d51"}

root@shruthi-VirtualBox:~/go/src/github.com/opensds/opensds# curl -X DELETE http://<IP_ADDRESS>:50040/v1beta/e93b4c0934da416eb9c8d120c5d04d96/profiles/b859e948-42e7-450b-a617-bb1b1c5ea068
{"code":400,"message":"There are dependent fileshares : [fileshare3 fileshare2 fileshare1] for the specified profile b859e948-42e7-450b-a617-bb1b1c5ea068"}

root@shruthi-VirtualBox:~/go/src/github.com/opensds/opensds# curl -X DELETE http://<IP_ADDRESS>:50040/v1beta/e93b4c0934da416eb9c8d120c5d04d96/profiles/a637b596-0987-4149-a216-1ec6dcff8c5b
{"code":400,"message":"There are dependent filesharesnapshots : [snap5] for the specified profile a637b596-0987-4149-a216-1ec6dcff8c5b"}

Release note:

The logic is not correct, you need to make sure all resources are not existed.

I think it's fine because only volume and fileshare depend on profile directly.


Failed to add firewall rule - Using self-hosted runner and Deny public access in AzureSQL server

I have an error when deploying a bacpac from a self hosted runner...I have a sql server but denying public access in the sql server firewall options (obviously this disables the option to add any rule by runner ip)
How could I deploy a bacpac from a self hosted runner to a server that only uses private endpoint. I need to automate this action.
"Error: Failed to add firewall rule. Unable to detect client IP Address. Error: There was a error when attempting to execute the process 'sqlcmd'. This may indicate the process failed to start. Error: spawn sqlcmd ENOENT."

no. I only have the task of downloading the build job artifact, then azure login and finally this sql-deploy action.
my runner is linux and I only use it as a bridge to deploy and connect to my Azure resources.
It works perfect for deploying to webapps.

No problem, we can get you up and running!
The task has 2 prerequisites for self-hosted runners:

sqlcmd in mssql-tools: https://docs.microsoft.com/sql/linux/sql-server-linux-setup-tools
sqlpackage: https://docs.microsoft.com/sql/tools/sqlpackage/sqlpackage-download

An evergreen link (https://aka.ms/sqlpackage-linux) is available that points to the current version of sqlpackage for Linux .NET Core, which can be used in automating environments with the latest sqlpackage.

Please feel free to respond with more questions/info and we can reopen the issue.

we have the same issue of deploying from a self-host-runner to a Azure SQL database through private endpoint only.  "public access" is disabled in database.
could you elaborate the solution?  will sql-action work after sqlcmd and sqlpackage installed in SHR?


Add nominee: Geomancer: An Open-Source Framework for Geospatial Feature Engineering

Automatic addition of a new nominee submitted through the online form available at https://digitalpublicgoods.net/submission

Thanks @nathanbaleeta. Made small edit in 115e96f to shorten the name field, removed empty field and added org website. This is ready for your approval and merge.

resolved #108


spawnCreep returns a more general type than is needed

spawnCreep is defined as:
    /**
     * Start the creep spawning process. The required energy amount can be withdrawn from all spawns and extensions in the room.
     * @returns A creep on success or an errorcode on failure
     */
    spawnCreep(
      body: BodyPartConstant[]
    ): { object?: Creep; error?: ERR_BUSY | ERR_INVALID_ARGS | ERR_NOT_ENOUGH_ENERGY };

But according to both the jsdoc here and the documentation, it never returns both object and error.
This means that in reality, !spawnCreep().error implies that an object was returned, but the type inference misses that.
I propose one of the following definitions:
   spawnCreep(
      body: BodyPartConstant[]
    ): { object: undefined; error: ERR_BUSY | ERR_INVALID_ARGS | ERR_NOT_ENOUGH_ENERGY } |
 { object: Creep; error: undefined };

   spawnCreep(
      body: BodyPartConstant[]
    ): { error: ERR_BUSY | ERR_INVALID_ARGS | ERR_NOT_ENOUGH_ENERGY } | { object: Creep; };

I'm pretty sure the second one is correct (when console.logging the result of spawnCreep it always contained only one of object or error), but only the first one lets me do if (spawnCreep(...).object) (although I can still do if ('object' in spawnCreep(...)))

Hi @guyguy2001 Thank you for taking the time to report the issue.
I agree that the following definition sounds more correct if the spawn method in fact contains either one or the other.
spawnCreep(
      body: BodyPartConstant[]
    ): { error: ERR_BUSY | ERR_INVALID_ARGS | ERR_NOT_ENOUGH_ENERGY } | { object: Creep; };

If you could make a PR to the develop branch and update the tests https://github.com/screepers/typed-screeps-arena/blob/develop/dist/test/screeps-arena-tests.ts and run the test with npm run test it would be very much appreciated :)

Just to make sure - the section in the Readme about deploying to definitely typed is for when you publish a version, and not for PRs to your repo, right?

Yes, it just details how we push types to DT, the screeps-arena-tests.ts are however run by DT when we actually do make a PR to them.
the PR you should make should be to this repo (typed-screeps-arena) and it should be a PR from the develop branch :)

Alright, I got a long weekend thanks to Passover so I can do some PRs here
Before I go into it, one usability question -
Currently, I check if the spawn succeeded like this:
      const creep = spawn.spawnCreep([MOVE, CARRY, MOVE, CARRY]).object;
      if (creep) {
         ...
      }

But this gives an error with the new declaration.
How would you change the code to work with it?
While I'm all for being as correct as possible, I don't wanna introduce a breaking change which can be a regression in a lot of cases

I think I personally would do it the same no matter how it's typed
      const potentiallySpawnedCreepResult= spawn.spawnCreep([MOVE, CARRY, MOVE, CARRY]);
      if (!potentiallySpawnedCreepResult.error) {
         const creep = potentiallySpawnedCreepResult.object
      }

keep in mind though that the .object that is returned might not actually get spawned, we can cancel the spawn in the next tick, or an extension could be destroyed on the same tick that we request it to spawn.

But this gives the same error:

Same if I try to destruct it.
This isn't an issue in this typing:
   spawnCreep(
      body: BodyPartConstant[]
    ): { object: undefined; error: ERR_BUSY | ERR_INVALID_ARGS | ERR_NOT_ENOUGH_ENERGY } |
 { object: Creep; error: undefined };

but then the "error" in result guard won't work, because it technically isn't correct (although I'm not sure how much that matters)

It has been over 2 years since the previous comment, so I wanted to update this thread before closing it out.
Screeps Arena now generates official typings in dist folders to provide code completion (intellisense) for javascript players.
The official types specifies the spawnCreep method returning a SpawnCreepResult:
https://github.com/screeps/arena-definitions/blob/3f1f33ede4d1bba7cb3553d942e906e8e22e5a39/common/typings/game/prototypes/spawn.d.ts#L7-L13
export interface SpawnCreepResult {
    /** the instance of the {@link Creep} being spawned */
    object?: Creep | undefined;

    /** the error code */
    error?: typeof ERR_NOT_OWNER | typeof ERR_INVALID_ARGS | typeof ERR_NOT_ENOUGH_ENERGY | typeof ERR_BUSY | undefined;
}

This matches the return type that we used previously in the season-alpha branch.
The type has been updated in the season-beta branch to use the SpawnCreepResult name.
Here is some example code that demonstrates calling the spawnCreep method in Screeps Arena during Season Alpha:
const mySpawn = getObjectsByPrototype(StructureSpawn).find((spawn) => spawn.my);
const body = [ATTACK, MOVE];
const { object: creep, error } = mySpawn.spawnCreep(body);

if (creep) {
  console.log('Creep spawning:', creep);
}

if (error) {
  console.log('Spawn error:', error);
}


RTL support for the drawer (open drawer from right of the screen)

Can you explain how can I implement this great navigation drawer to be opened from right to left of the screen. I have tried many ways like android:layout_gravity:right,         getWindow().getDecorView().setLayoutDirection(View.LAYOUT_DIRECTION_RTL);, or giving LayoutParams to the drawer object but none of them worked for me.

Release 2.2.0 includes support for RTL text and automatically aligns the drawer to the right on RTL locales.

Wow! That's great and thank you.

how to have RTL support on not RTL languages?


SIGINT hook does not allow to kill dataset constructor

SIGINT hook traps signals before dataset construction and processes it after it. If dataset construction takes too long, it does not allow to kill it by Ctrl+C. An expected behavior would be to start trapping signals before training.

Good point. It can not be handle with a hook though. This must be resolved directly in cxflow right?

It should be doable by a hook. Actually, I am not sure why is it happening, since sigint hook registers the handler in before_training function, which should be launched after the dataset is created. I will have to diagnose deeper.

similar problem with dataset methods

Well, I don't think we can solve it for other dataset methods than constructor, because if we want to terminate gracefully and the dataset is already doing something in the middle of the training, we have to wait for it. I am not sure how to solve it. It may be possible to call e.g.t, dataset's terminate() function or to forward the SIGINT. However, the implementation of the dataset would complicate somehow.

I am strongly against yet another enforced method.  :)

What is the status? Do we want to take some action before we merge #157 ?

I believe that in #157 will partially solve the issue. Unfortunately, the problem of killing lazy datasets in stream functions still remains. I believe there is not much we can do about it though.