raspberry pi 4 #55

amonsifr · 2019-09-10T11:46:20Z

Description of problem

Hello,
I am trying to install kata container on a raspberry pi 4 following this page:
https://github.com/kata-containers/documentation/blob/master/Developer-Guide.md

However I can't obtain the busybox shell.

Expected result

a running shell

Actual result

sudo docker run -ti --runtime kata-runtime busybox sh
docker: Error response from daemon: OCI runtime create failed: fail to launch qemu: exit status 1, error messages from qemu log:: unknown.

tonio@ubuntu:~$ sudo kata-collect-data.sh

Show kata-collect-data.sh details

Meta details

Running kata-collect-data.sh version 1.9.0-alpha1 (commit 0cc1a6f6ed0228e6c70b1503436172d96a452f01) at 2019-09-10.08:50:28.594343010+0000.

Runtime is /usr/local/bin/kata-runtime.

`kata-env`

Output of "/usr/local/bin/kata-runtime kata-env":

[Meta]
  Version = "1.0.23"

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

[Hypervisor]
  MachineType = "virt"
  Version = "QEMU emulator version 4.1.50 (v4.1.0-733-g89ea03a7dc-dirty)\nCopyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers"
  Path = "/usr/bin/qemu-system-aarch64"
  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-2019-08-28-14:34:51.381609631+0000-64caa3f"

[Kernel]
  Path = "/usr/share/kata-containers/vmlinuz-4.19.65-48"
  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-alpha0-c843aeddcf56d1e60b082b2223d77bfaf971a0d9"
  Path = "/usr/libexec/kata-containers/kata-proxy"
  Debug = true

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

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

[Host]
  Kernel = "5.2.10-v8+"
  Architecture = "arm64"
  VMContainerCapable = true
  SupportVSocks = true
  [Host.Distro]
    Name = "Ubuntu"
    Version = "19.04"
  [Host.CPU]
    Vendor = "ARM Limited"
    Model = "v8"

[Netmon]
  Version = "kata-netmon version 1.9.0-alpha1"
  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-system-aarch64"
kernel = "/usr/share/kata-containers/vmlinuz.container"
#initrd = "/usr/share/kata-containers/kata-containers-initrd.img"
image = "/usr/share/kata-containers/kata-containers.img"
machine_type = "virt"

# 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 = 1

# 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 = 0

# 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 = 512
#
# 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=false

# 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-system-aarch64"
kernel = "/usr/share/kata-containers/vmlinuz.container"
#initrd = "/usr/share/kata-containers/kata-containers-initrd.img"
image = "/usr/share/kata-containers/kata-containers.img"
machine_type = "virt"

# 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 = 1

# 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 = 0

# 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 = 512
#
# 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=false

# 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 " --version":

/usr/local/bin/kata-collect-data.sh: line 178: --version: command not found

systemd service

Image details

---
osbuilder:
  url: "https://github.com/kata-containers/osbuilder"
  version: "unknown"
rootfs-creation-time: "Failed at 173: date -u -d@${SOURCE_DATE_EPOCH:-$(date +%s.%N)} '+%Y-%m-%dT%T.%N%zZ'"
description: "osbuilder rootfs"
file-format-version: "0.0.2"
architecture: "aarch64"
base-distro:
  name: "Alpine"
  version: "v3.7"
  packages:
    default:
      - "iptables"
    extra:

agent:
  url: "https://github.com/kata-containers/agent"
  name: "kata-agent"
  version: "1.9.0-alpha0-dfbcc01c5444a344e98a85986a012c5b3412181f"
  agent-is-init-daemon: "yes"

Initrd details

No initrd

Logfiles

Runtime logs

Recent runtime problems found in system journal:

time="2019-09-03T12:08:33.283691466Z" level=warning msg="load sandbox devices failed" arch=arm64 command=create container=acd33e08be7d7a0e442be45f2224c2b086f3966f11bf7b276f86832f3e2f90b3 error="open /run/vc/sbs/acd33e08be7d7a0e442be45f2224c2b086f3966f11bf7b276f86832f3e2f90b3/devices.json: no such file or directory" name=kata-runtime pid=3341 sandbox=acd33e08be7d7a0e442be45f2224c2b086f3966f11bf7b276f86832f3e2f90b3 sandboxid=acd33e08be7d7a0e442be45f2224c2b086f3966f11bf7b276f86832f3e2f90b3 source=virtcontainers subsystem=sandbox
time="2019-09-03T12:08:34.295807834Z" level=error msg="Unable to launch /usr/bin/qemu-system-aarch64: exit status 1" arch=arm64 command=create container=acd33e08be7d7a0e442be45f2224c2b086f3966f11bf7b276f86832f3e2f90b3 name=kata-runtime pid=3341 source=virtcontainers subsystem=qmp
time="2019-09-03T12:08:34.296775922Z" level=error msg="Could not access KVM kernel module: No such file or directory\nqemu-system-aarch64: failed to initialize KVM: No such file or directory\n" arch=arm64 command=create container=acd33e08be7d7a0e442be45f2224c2b086f3966f11bf7b276f86832f3e2f90b3 name=kata-runtime pid=3341 source=virtcontainers subsystem=qmp
time="2019-09-03T12:08:34.374380838Z" level=warning msg="failed to cleanup netns" arch=arm64 command=create container=acd33e08be7d7a0e442be45f2224c2b086f3966f11bf7b276f86832f3e2f90b3 error="failed to get netns /var/run/netns/cni-bb969b12-6c66-a0aa-d62a-30a522b98009: failed to Statfs \"/var/run/netns/cni-bb969b12-6c66-a0aa-d62a-30a522b98009\": no such file or directory" name=kata-runtime path=/var/run/netns/cni-bb969b12-6c66-a0aa-d62a-30a522b98009 pid=3341 source=katautils
time="2019-09-03T12:08:34.374734096Z" level=error msg="fail to launch qemu: exit status 1, error messages from qemu log: Could not access KVM kernel module: No such file or directory\nqemu-system-aarch64: failed to initialize KVM: No such file or directory\n" arch=arm64 command=create container=acd33e08be7d7a0e442be45f2224c2b086f3966f11bf7b276f86832f3e2f90b3 name=kata-runtime pid=3341 source=runtime
time="2019-09-03T14:04:38.787561791Z" level=warning msg="VM memory (512MB) smaller than image \"/usr/share/kata-containers/kata-containers-2019-08-28-14:34:51.381609631+0000-64caa3f\" size (1024MB)" arch=arm64 command=create name=kata-runtime pid=1167 source=katautils
time="2019-09-03T14:04:39.106638492Z" level=info msg="Unable to know if the system is running inside a VM" arch=arm64 command=create container=a4082a21d99b0c3a08afcd9d20ec0c127a7890e0b78bc983378e9aa18fa432c2 name=kata-runtime pid=1167 source=virtcontainers
time="2019-09-03T14:04:39.107237003Z" level=warning msg="load sandbox devices failed" arch=arm64 command=create container=a4082a21d99b0c3a08afcd9d20ec0c127a7890e0b78bc983378e9aa18fa432c2 error="open /run/vc/sbs/a4082a21d99b0c3a08afcd9d20ec0c127a7890e0b78bc983378e9aa18fa432c2/devices.json: no such file or directory" name=kata-runtime pid=1167 sandbox=a4082a21d99b0c3a08afcd9d20ec0c127a7890e0b78bc983378e9aa18fa432c2 sandboxid=a4082a21d99b0c3a08afcd9d20ec0c127a7890e0b78bc983378e9aa18fa432c2 source=virtcontainers subsystem=sandbox
time="2019-09-03T14:04:40.552777585Z" level=error msg="Unable to launch /usr/bin/qemu-system-aarch64: exit status 1" arch=arm64 command=create container=a4082a21d99b0c3a08afcd9d20ec0c127a7890e0b78bc983378e9aa18fa432c2 name=kata-runtime pid=1167 source=virtcontainers subsystem=qmp
time="2019-09-03T14:04:40.552998835Z" level=error msg="qemu-system-aarch64: -device nvdimm,id=nv0,memdev=mem0: 'nvdimm' is not a valid device model name\n" arch=arm64 command=create container=a4082a21d99b0c3a08afcd9d20ec0c127a7890e0b78bc983378e9aa18fa432c2 name=kata-runtime pid=1167 source=virtcontainers subsystem=qmp
time="2019-09-03T14:04:40.634089735Z" level=warning msg="failed to cleanup netns" arch=arm64 command=create container=a4082a21d99b0c3a08afcd9d20ec0c127a7890e0b78bc983378e9aa18fa432c2 error="failed to get netns /var/run/netns/cni-cb2391c7-b376-378a-0720-e0830ced025f: failed to Statfs \"/var/run/netns/cni-cb2391c7-b376-378a-0720-e0830ced025f\": no such file or directory" name=kata-runtime path=/var/run/netns/cni-cb2391c7-b376-378a-0720-e0830ced025f pid=1167 source=katautils
time="2019-09-03T14:04:40.634305689Z" level=error msg="fail to launch qemu: exit status 1, error messages from qemu log: qemu-system-aarch64: -device nvdimm,id=nv0,memdev=mem0: 'nvdimm' is not a valid device model name\n" arch=arm64 command=create container=a4082a21d99b0c3a08afcd9d20ec0c127a7890e0b78bc983378e9aa18fa432c2 name=kata-runtime pid=1167 source=runtime
time="2019-09-03T14:18:41.515793435Z" level=warning msg="VM memory (512MB) smaller than image \"/usr/share/kata-containers/kata-containers-2019-08-28-14:34:51.381609631+0000-64caa3f\" size (1024MB)" arch=arm64 command=create name=kata-runtime pid=1972 source=katautils
time="2019-09-03T14:18:42.285774217Z" level=info msg="Unable to know if the system is running inside a VM" arch=arm64 command=create container=782f083ffa53575ac71beecedd85bad3022710abe70ac490093a46d6105c06da name=kata-runtime pid=1972 source=virtcontainers
time="2019-09-03T14:18:42.286794084Z" level=warning msg="load sandbox devices failed" arch=arm64 command=create container=782f083ffa53575ac71beecedd85bad3022710abe70ac490093a46d6105c06da error="open /run/vc/sbs/782f083ffa53575ac71beecedd85bad3022710abe70ac490093a46d6105c06da/devices.json: no such file or directory" name=kata-runtime pid=1972 sandbox=782f083ffa53575ac71beecedd85bad3022710abe70ac490093a46d6105c06da sandboxid=782f083ffa53575ac71beecedd85bad3022710abe70ac490093a46d6105c06da source=virtcontainers subsystem=sandbox
time="2019-09-03T14:18:43.308144028Z" level=error msg="Unable to launch /usr/bin/qemu-system-aarch64: exit status 1" arch=arm64 command=create container=782f083ffa53575ac71beecedd85bad3022710abe70ac490093a46d6105c06da name=kata-runtime pid=1972 source=virtcontainers subsystem=qmp
time="2019-09-03T14:18:43.308367064Z" level=error msg="qemu-system-aarch64: Property '.virt' not found\n" arch=arm64 command=create container=782f083ffa53575ac71beecedd85bad3022710abe70ac490093a46d6105c06da name=kata-runtime pid=1972 source=virtcontainers subsystem=qmp
time="2019-09-03T14:18:43.384422032Z" level=warning msg="failed to cleanup netns" arch=arm64 command=create container=782f083ffa53575ac71beecedd85bad3022710abe70ac490093a46d6105c06da error="failed to get netns /var/run/netns/cni-93861221-dd62-bf90-0749-e9ce8c012ce0: failed to Statfs \"/var/run/netns/cni-93861221-dd62-bf90-0749-e9ce8c012ce0\": no such file or directory" name=kata-runtime path=/var/run/netns/cni-93861221-dd62-bf90-0749-e9ce8c012ce0 pid=1972 source=katautils
time="2019-09-03T14:18:43.384696105Z" level=error msg="fail to launch qemu: exit status 1, error messages from qemu log: qemu-system-aarch64: Property '.virt' not found\n" arch=arm64 command=create container=782f083ffa53575ac71beecedd85bad3022710abe70ac490093a46d6105c06da name=kata-runtime pid=1972 source=runtime
time="2019-09-03T14:24:04.163837562Z" level=warning msg="VM memory (512MB) smaller than image \"/usr/share/kata-containers/kata-containers-2019-08-28-14:34:51.381609631+0000-64caa3f\" size (1024MB)" arch=arm64 command=create name=kata-runtime pid=2650 source=katautils
time="2019-09-03T14:24:04.700306427Z" level=info msg="Unable to know if the system is running inside a VM" arch=arm64 command=create container=64965ec0551b7180d22f1e6b64cceb3ea6c3c6e937532d271519c7fb22819c46 name=kata-runtime pid=2650 source=virtcontainers
time="2019-09-03T14:24:04.701305474Z" level=warning msg="load sandbox devices failed" arch=arm64 command=create container=64965ec0551b7180d22f1e6b64cceb3ea6c3c6e937532d271519c7fb22819c46 error="open /run/vc/sbs/64965ec0551b7180d22f1e6b64cceb3ea6c3c6e937532d271519c7fb22819c46/devices.json: no such file or directory" name=kata-runtime pid=2650 sandbox=64965ec0551b7180d22f1e6b64cceb3ea6c3c6e937532d271519c7fb22819c46 sandboxid=64965ec0551b7180d22f1e6b64cceb3ea6c3c6e937532d271519c7fb22819c46 source=virtcontainers subsystem=sandbox
time="2019-09-03T14:24:05.466759329Z" level=error msg="Unable to launch /usr/bin/qemu-system-aarch64: exit status 1" arch=arm64 command=create container=64965ec0551b7180d22f1e6b64cceb3ea6c3c6e937532d271519c7fb22819c46 name=kata-runtime pid=2650 source=virtcontainers subsystem=qmp
time="2019-09-03T14:24:05.467006049Z" level=error msg="qemu-system-aarch64: Property '.virto-blk' not found\n" arch=arm64 command=create container=64965ec0551b7180d22f1e6b64cceb3ea6c3c6e937532d271519c7fb22819c46 name=kata-runtime pid=2650 source=virtcontainers subsystem=qmp
time="2019-09-03T14:24:05.547597686Z" level=warning msg="failed to cleanup netns" arch=arm64 command=create container=64965ec0551b7180d22f1e6b64cceb3ea6c3c6e937532d271519c7fb22819c46 error="failed to get netns /var/run/netns/cni-8156911f-806f-597e-3bc1-aa8ef92098f8: failed to Statfs \"/var/run/netns/cni-8156911f-806f-597e-3bc1-aa8ef92098f8\": no such file or directory" name=kata-runtime path=/var/run/netns/cni-8156911f-806f-597e-3bc1-aa8ef92098f8 pid=2650 source=katautils
time="2019-09-03T14:24:05.547771722Z" level=error msg="fail to launch qemu: exit status 1, error messages from qemu log: qemu-system-aarch64: Property '.virto-blk' not found\n" arch=arm64 command=create container=64965ec0551b7180d22f1e6b64cceb3ea6c3c6e937532d271519c7fb22819c46 name=kata-runtime pid=2650 source=runtime
time="2019-09-03T14:30:14.003398032Z" level=warning msg="VM memory (512MB) smaller than image \"/usr/share/kata-containers/kata-containers-2019-08-28-14:34:51.381609631+0000-64caa3f\" size (1024MB)" arch=arm64 command=create name=kata-runtime pid=3259 source=katautils
time="2019-09-03T14:30:15.69201395Z" level=info msg="Unable to know if the system is running inside a VM" arch=arm64 command=create container=7c6837dfe1ff10570520a9173201a10e9e6fcf5154bdc1cf111e9db88430ae77 name=kata-runtime pid=3259 source=virtcontainers
time="2019-09-03T14:30:15.692984188Z" level=warning msg="load sandbox devices failed" arch=arm64 command=create container=7c6837dfe1ff10570520a9173201a10e9e6fcf5154bdc1cf111e9db88430ae77 error="open /run/vc/sbs/7c6837dfe1ff10570520a9173201a10e9e6fcf5154bdc1cf111e9db88430ae77/devices.json: no such file or directory" name=kata-runtime pid=3259 sandbox=7c6837dfe1ff10570520a9173201a10e9e6fcf5154bdc1cf111e9db88430ae77 sandboxid=7c6837dfe1ff10570520a9173201a10e9e6fcf5154bdc1cf111e9db88430ae77 source=virtcontainers subsystem=sandbox
time="2019-09-03T14:30:16.749254689Z" level=error msg="Unable to launch /usr/bin/qemu-system-aarch64: exit status 1" arch=arm64 command=create container=7c6837dfe1ff10570520a9173201a10e9e6fcf5154bdc1cf111e9db88430ae77 name=kata-runtime pid=3259 source=virtcontainers subsystem=qmp
time="2019-09-03T14:30:16.749492651Z" level=error msg="qemu-system-aarch64: Property '.virtio-blk' not found\n" arch=arm64 command=create container=7c6837dfe1ff10570520a9173201a10e9e6fcf5154bdc1cf111e9db88430ae77 name=kata-runtime pid=3259 source=virtcontainers subsystem=qmp
time="2019-09-03T14:30:16.83235203Z" level=warning msg="failed to cleanup netns" arch=arm64 command=create container=7c6837dfe1ff10570520a9173201a10e9e6fcf5154bdc1cf111e9db88430ae77 error="failed to get netns /var/run/netns/cni-24130e52-726a-3a80-203d-1bff5a501862: failed to Statfs \"/var/run/netns/cni-24130e52-726a-3a80-203d-1bff5a501862\": no such file or directory" name=kata-runtime path=/var/run/netns/cni-24130e52-726a-3a80-203d-1bff5a501862 pid=3259 source=katautils
time="2019-09-03T14:30:16.832928232Z" level=error msg="fail to launch qemu: exit status 1, error messages from qemu log: qemu-system-aarch64: Property '.virtio-blk' not found\n" arch=arm64 command=create container=7c6837dfe1ff10570520a9173201a10e9e6fcf5154bdc1cf111e9db88430ae77 name=kata-runtime pid=3259 source=runtime
time="2019-09-03T14:32:28.547073422Z" level=warning msg="VM memory (512MB) smaller than image \"/usr/share/kata-containers/kata-containers-2019-08-28-14:34:51.381609631+0000-64caa3f\" size (1024MB)" arch=arm64 command=create name=kata-runtime pid=3861 source=katautils
time="2019-09-03T14:32:28.849962319Z" level=info msg="Unable to know if the system is running inside a VM" arch=arm64 command=create container=fb00b8a28eafbfb1157bcf468f6a3a1c0b90a576357d6c3a2a2750ccc47e1a9f name=kata-runtime pid=3861 source=virtcontainers
time="2019-09-03T14:32:28.85096002Z" level=warning msg="load sandbox devices failed" arch=arm64 command=create container=fb00b8a28eafbfb1157bcf468f6a3a1c0b90a576357d6c3a2a2750ccc47e1a9f error="open /run/vc/sbs/fb00b8a28eafbfb1157bcf468f6a3a1c0b90a576357d6c3a2a2750ccc47e1a9f/devices.json: no such file or directory" name=kata-runtime pid=3861 sandbox=fb00b8a28eafbfb1157bcf468f6a3a1c0b90a576357d6c3a2a2750ccc47e1a9f sandboxid=fb00b8a28eafbfb1157bcf468f6a3a1c0b90a576357d6c3a2a2750ccc47e1a9f source=virtcontainers subsystem=sandbox
time="2019-09-03T14:32:28.967019088Z" level=error msg="Unable to launch /usr/bin/qemu-system-aarch64: exit status 1" arch=arm64 command=create container=fb00b8a28eafbfb1157bcf468f6a3a1c0b90a576357d6c3a2a2750ccc47e1a9f name=kata-runtime pid=3861 source=virtcontainers subsystem=qmp
time="2019-09-03T14:32:28.967248143Z" level=error msg="qemu-system-aarch64: Property '.virtio-scsi' not found\n" arch=arm64 command=create container=fb00b8a28eafbfb1157bcf468f6a3a1c0b90a576357d6c3a2a2750ccc47e1a9f name=kata-runtime pid=3861 source=virtcontainers subsystem=qmp
time="2019-09-03T14:32:29.044400498Z" level=warning msg="failed to cleanup netns" arch=arm64 command=create container=fb00b8a28eafbfb1157bcf468f6a3a1c0b90a576357d6c3a2a2750ccc47e1a9f error="failed to get netns /var/run/netns/cni-40c890a1-36c6-05c1-bf28-13984e3406cc: failed to Statfs \"/var/run/netns/cni-40c890a1-36c6-05c1-bf28-13984e3406cc\": no such file or directory" name=kata-runtime path=/var/run/netns/cni-40c890a1-36c6-05c1-bf28-13984e3406cc pid=3861 source=katautils
time="2019-09-03T14:32:29.044708756Z" level=error msg="fail to launch qemu: exit status 1, error messages from qemu log: qemu-system-aarch64: Property '.virtio-scsi' not found\n" arch=arm64 command=create container=fb00b8a28eafbfb1157bcf468f6a3a1c0b90a576357d6c3a2a2750ccc47e1a9f name=kata-runtime pid=3861 source=runtime
time="2019-09-10T08:41:27.729594114Z" level=warning msg="VM memory (512MB) smaller than image \"/usr/share/kata-containers/kata-containers-2019-08-28-14:34:51.381609631+0000-64caa3f\" size (1024MB)" arch=arm64 command=create name=kata-runtime pid=4175 source=katautils
time="2019-09-10T08:41:28.064227015Z" level=info msg="Unable to know if the system is running inside a VM" arch=arm64 command=create container=c9232a90e81ed5f6dab154b5164a3c4db9131a83107c690538d6e517d45f680b name=kata-runtime pid=4175 source=virtcontainers
time="2019-09-10T08:41:28.064840585Z" level=debug msg="Could not retrieve anything from storage" arch=arm64 command=create container=c9232a90e81ed5f6dab154b5164a3c4db9131a83107c690538d6e517d45f680b name=kata-runtime pid=4175 source=virtcontainers subsystem=kata_agent
time="2019-09-10T08:41:28.064983102Z" level=warning msg="load sandbox devices failed" arch=arm64 command=create container=c9232a90e81ed5f6dab154b5164a3c4db9131a83107c690538d6e517d45f680b error="open /run/vc/sbs/c9232a90e81ed5f6dab154b5164a3c4db9131a83107c690538d6e517d45f680b/devices.json: no such file or directory" name=kata-runtime pid=4175 sandbox=c9232a90e81ed5f6dab154b5164a3c4db9131a83107c690538d6e517d45f680b sandboxid=c9232a90e81ed5f6dab154b5164a3c4db9131a83107c690538d6e517d45f680b source=virtcontainers subsystem=sandbox
time="2019-09-10T08:41:28.182967239Z" level=debug arch=arm64 command=create container=c9232a90e81ed5f6dab154b5164a3c4db9131a83107c690538d6e517d45f680b default-kernel-parameters="console=hvc0 console=hvc1 iommu.passthrough=0 root=/dev/pmem0p1 rootflags=data=ordered,errors=remount-ro ro rootfstype=ext4 debug systemd.show_status=true systemd.log_level=debug" name=kata-runtime pid=4175 source=virtcontainers subsystem=qemu
time="2019-09-10T08:41:29.113178433Z" level=error msg="Unable to launch /usr/bin/qemu-system-aarch64: exit status 1" arch=arm64 command=create container=c9232a90e81ed5f6dab154b5164a3c4db9131a83107c690538d6e517d45f680b name=kata-runtime pid=4175 source=virtcontainers subsystem=qmp
time="2019-09-10T08:41:29.114285795Z" level=error arch=arm64 command=create container=c9232a90e81ed5f6dab154b5164a3c4db9131a83107c690538d6e517d45f680b name=kata-runtime pid=4175 source=virtcontainers subsystem=qmp
time="2019-09-10T08:41:29.191321454Z" level=warning msg="sandox cgroups path is empty" arch=arm64 command=create container=c9232a90e81ed5f6dab154b5164a3c4db9131a83107c690538d6e517d45f680b name=kata-runtime pid=4175 sandbox=c9232a90e81ed5f6dab154b5164a3c4db9131a83107c690538d6e517d45f680b source=virtcontainers subsystem=sandbox
time="2019-09-10T08:41:29.196055235Z" level=warning msg="failed to cleanup netns" arch=arm64 command=create container=c9232a90e81ed5f6dab154b5164a3c4db9131a83107c690538d6e517d45f680b error="failed to get netns /var/run/netns/cni-4aa4ee3c-6fbb-06dd-3337-2c3db991643e: failed to Statfs \"/var/run/netns/cni-4aa4ee3c-6fbb-06dd-3337-2c3db991643e\": no such file or directory" name=kata-runtime path=/var/run/netns/cni-4aa4ee3c-6fbb-06dd-3337-2c3db991643e pid=4175 source=katautils
time="2019-09-10T08:41:29.196626786Z" level=error msg="fail to launch qemu: exit status 1, error messages from qemu log: " arch=arm64 command=create container=c9232a90e81ed5f6dab154b5164a3c4db9131a83107c690538d6e517d45f680b name=kata-runtime pid=4175 source=runtime

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:32:20 2019
 OS/Arch:           linux/arm64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.2
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.8
  Git commit:       6a30dfc
  Built:            Thu Aug 29 05:30:52 2019
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Output of "docker info":

Client:
 Debug Mode: false

Server:
 Containers: 1
  Running: 0
  Paused: 0
  Stopped: 1
 Images: 1
 Server Version: 19.03.2
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: kata-runtime runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 5.2.10-v8+
 Operating System: Ubuntu 19.04
 OSType: linux
 Architecture: aarch64
 CPUs: 4
 Total Memory: 1.84GiB
 Name: ubuntu
 ID: 2COC:BESL:UDHX:3BYE:K5RD:WHKK:I7BI:7EO3:3HWX:6UZQ:RGYC:LHBE
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 21
  Goroutines: 35
  System Time: 2019-09-10T08:50:35.790140249Z
  EventsListeners: 0
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No swap limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support

Output of "systemctl show docker":

Type=notify
Restart=always
NotifyAccess=main
RestartUSec=2s
TimeoutStartUSec=infinity
TimeoutStopUSec=infinity
RuntimeMaxUSec=infinity
WatchdogUSec=0
WatchdogTimestampMonotonic=0
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=3973
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
StatusErrno=0
Result=success
UID=[not set]
GID=[not set]
NRestarts=0
ExecMainStartTimestamp=Tue 2019-09-10 08:41:08 UTC
ExecMainStartTimestampMonotonic=863762198
ExecMainExitTimestampMonotonic=0
ExecMainPID=3973
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/bin/dockerd ; argv[]=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock --add-runtime kata-runtime=/usr/local/bin/kata-runtime ; ignore_errors=no ; start_time=[Tue 2019-09-10 08:41:08 UTC] ; stop_time=[n/a] ; pid=3973 ; 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
ControlGroup=/system.slice/docker.service
MemoryCurrent=86310912
CPUUsageNSec=[not set]
TasksCurrent=[not set]
IPIngressBytes=18446744073709551615
IPIngressPackets=18446744073709551615
IPEgressBytes=18446744073709551615
IPEgressPackets=18446744073709551615
Delegate=yes
DelegateControllers=cpu cpuacct io blkio memory devices pids bpf-firewall bpf-devices
CPUAccounting=no
CPUWeight=[not set]
StartupCPUWeight=[not set]
CPUShares=[not set]
StartupCPUShares=[not set]
CPUQuotaPerSecUSec=infinity
IOAccounting=no
IOWeight=[not set]
StartupIOWeight=[not set]
BlockIOAccounting=no
BlockIOWeight=[not set]
StartupBlockIOWeight=[not set]
MemoryAccounting=yes
MemoryMin=0
MemoryLow=0
MemoryHigh=infinity
MemoryMax=infinity
MemorySwapMax=infinity
MemoryLimit=infinity
DevicePolicy=auto
TasksAccounting=yes
TasksMax=infinity
IPAccounting=no
UMask=0022
LimitCPU=infinity
LimitCPUSoft=infinity
LimitFSIZE=infinity
LimitFSIZESoft=infinity
LimitDATA=infinity
LimitDATASoft=infinity
LimitSTACK=infinity
LimitSTACKSoft=8388608
LimitCORE=infinity
LimitCORESoft=infinity
LimitRSS=infinity
LimitRSSSoft=infinity
LimitNOFILE=infinity
LimitNOFILESoft=infinity
LimitAS=infinity
LimitASSoft=infinity
LimitNPROC=infinity
LimitNPROCSoft=infinity
LimitMEMLOCK=67108864
LimitMEMLOCKSoft=67108864
LimitLOCKS=infinity
LimitLOCKSSoft=infinity
LimitSIGPENDING=1613
LimitSIGPENDINGSoft=1613
LimitMSGQUEUE=819200
LimitMSGQUEUESoft=819200
LimitNICE=0
LimitNICESoft=0
LimitRTPRIO=0
LimitRTPRIOSoft=0
LimitRTTIME=infinity
LimitRTTIMESoft=infinity
OOMScoreAdjust=0
Nice=0
IOSchedulingClass=0
IOSchedulingPriority=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardInputData=
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SyslogLevel=6
SyslogFacility=3
LogLevelMax=-1
LogRateLimitIntervalUSec=0
LogRateLimitBurst=0
SecureBits=0
CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config cap_mknod cap_lease cap_audit_write cap_audit_control cap_setfcap cap_mac_override cap_mac_admin cap_syslog cap_wake_alarm cap_block_suspend
AmbientCapabilities=
DynamicUser=no
RemoveIPC=no
MountFlags=
PrivateTmp=no
PrivateDevices=no
ProtectKernelTunables=no
ProtectKernelModules=no
ProtectControlGroups=no
PrivateNetwork=no
PrivateUsers=no
PrivateMounts=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
LockPersonality=no
RuntimeDirectoryPreserve=no
RuntimeDirectoryMode=0755
StateDirectoryMode=0755
CacheDirectoryMode=0755
LogsDirectoryMode=0755
ConfigurationDirectoryMode=0755
MemoryDenyWriteExecute=no
RestrictRealtime=no
RestrictNamespaces=no
MountAPIVFS=no
KeyringMode=private
KillMode=process
KillSignal=15
FinalKillSignal=9
SendSIGKILL=yes
SendSIGHUP=no
WatchdogSignal=6
Id=docker.service
Names=docker.service
Requires=system.slice docker.socket sysinit.target
Wants=network-online.target
BindsTo=containerd.service
WantedBy=multi-user.target
ConsistsOf=docker.socket
Conflicts=shutdown.target
Before=shutdown.target multi-user.target
After=network-online.target sysinit.target docker.socket containerd.service system.slice firewalld.service basic.target systemd-journald.socket
TriggeredBy=docker.socket
Documentation=https://docs.docker.com
Description=Docker Application Container Engine
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/lib/systemd/system/docker.service
UnitFileState=enabled
UnitFilePreset=enabled
StateChangeTimestamp=Tue 2019-09-10 08:41:11 UTC
StateChangeTimestampMonotonic=866437946
InactiveExitTimestamp=Tue 2019-09-10 08:41:08 UTC
InactiveExitTimestampMonotonic=863763358
ActiveEnterTimestamp=Tue 2019-09-10 08:41:11 UTC
ActiveEnterTimestampMonotonic=866437946
ActiveExitTimestamp=Tue 2019-09-10 08:41:08 UTC
ActiveExitTimestampMonotonic=863741721
InactiveEnterTimestamp=Tue 2019-09-10 08:41:08 UTC
InactiveEnterTimestampMonotonic=863747571
CanStart=yes
CanStop=yes
CanReload=yes
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
NeedDaemonReload=no
JobTimeoutUSec=infinity
JobRunningTimeoutUSec=infinity
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Tue 2019-09-10 08:41:08 UTC
ConditionTimestampMonotonic=863759136
AssertTimestamp=Tue 2019-09-10 08:41:08 UTC
AssertTimestampMonotonic=863759136
Transient=no
Perpetual=no
StartLimitIntervalUSec=1min
StartLimitBurst=3
StartLimitAction=none
FailureAction=none
FailureActionExitStatus=-1
SuccessAction=none
SuccessActionExitStatus=-1
InvocationID=dba538197cb841809c24d1beb51fac54
CollectMode=inactive

No kubectl
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
RuntimeMaxUSec=infinity
WatchdogUSec=0
WatchdogTimestampMonotonic=0
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=1003
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
StatusErrno=0
Result=success
UID=[not set]
GID=[not set]
NRestarts=0
ExecMainStartTimestamp=Tue 2019-09-10 08:32:07 UTC
ExecMainStartTimestampMonotonic=322479497
ExecMainExitTimestampMonotonic=0
ExecMainPID=1003
ExecMainCode=0
ExecMainStatus=0
ExecStartPre={ path=/sbin/modprobe ; argv[]=/sbin/modprobe overlay ; ignore_errors=yes ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
ExecStart={ path=/usr/bin/containerd ; argv[]=/usr/bin/containerd ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
Slice=system.slice
ControlGroup=/system.slice/containerd.service
MemoryCurrent=92733440
CPUUsageNSec=[not set]
TasksCurrent=[not set]
IPIngressBytes=18446744073709551615
IPIngressPackets=18446744073709551615
IPEgressBytes=18446744073709551615
IPEgressPackets=18446744073709551615
Delegate=yes
DelegateControllers=cpu cpuacct io blkio memory devices pids bpf-firewall bpf-devices
CPUAccounting=no
CPUWeight=[not set]
StartupCPUWeight=[not set]
CPUShares=[not set]
StartupCPUShares=[not set]
CPUQuotaPerSecUSec=infinity
IOAccounting=no
IOWeight=[not set]
StartupIOWeight=[not set]
BlockIOAccounting=no
BlockIOWeight=[not set]
StartupBlockIOWeight=[not set]
MemoryAccounting=yes
MemoryMin=0
MemoryLow=0
MemoryHigh=infinity
MemoryMax=infinity
MemorySwapMax=infinity
MemoryLimit=infinity
DevicePolicy=auto
TasksAccounting=yes
TasksMax=infinity
IPAccounting=no
UMask=0022
LimitCPU=infinity
LimitCPUSoft=infinity
LimitFSIZE=infinity
LimitFSIZESoft=infinity
LimitDATA=infinity
LimitDATASoft=infinity
LimitSTACK=infinity
LimitSTACKSoft=8388608
LimitCORE=infinity
LimitCORESoft=infinity
LimitRSS=infinity
LimitRSSSoft=infinity
LimitNOFILE=1048576
LimitNOFILESoft=1048576
LimitAS=infinity
LimitASSoft=infinity
LimitNPROC=infinity
LimitNPROCSoft=infinity
LimitMEMLOCK=67108864
LimitMEMLOCKSoft=67108864
LimitLOCKS=infinity
LimitLOCKSSoft=infinity
LimitSIGPENDING=1613
LimitSIGPENDINGSoft=1613
LimitMSGQUEUE=819200
LimitMSGQUEUESoft=819200
LimitNICE=0
LimitNICESoft=0
LimitRTPRIO=0
LimitRTPRIOSoft=0
LimitRTTIME=infinity
LimitRTTIMESoft=infinity
OOMScoreAdjust=0
Nice=0
IOSchedulingClass=0
IOSchedulingPriority=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardInputData=
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SyslogLevel=6
SyslogFacility=3
LogLevelMax=-1
LogRateLimitIntervalUSec=0
LogRateLimitBurst=0
SecureBits=0
CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config cap_mknod cap_lease cap_audit_write cap_audit_control cap_setfcap cap_mac_override cap_mac_admin cap_syslog cap_wake_alarm cap_block_suspend
AmbientCapabilities=
DynamicUser=no
RemoveIPC=no
MountFlags=
PrivateTmp=no
PrivateDevices=no
ProtectKernelTunables=no
ProtectKernelModules=no
ProtectControlGroups=no
PrivateNetwork=no
PrivateUsers=no
PrivateMounts=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
LockPersonality=no
RuntimeDirectoryPreserve=no
RuntimeDirectoryMode=0755
StateDirectoryMode=0755
CacheDirectoryMode=0755
LogsDirectoryMode=0755
ConfigurationDirectoryMode=0755
MemoryDenyWriteExecute=no
RestrictRealtime=no
RestrictNamespaces=no
MountAPIVFS=no
KeyringMode=private
KillMode=process
KillSignal=15
FinalKillSignal=9
SendSIGKILL=yes
SendSIGHUP=no
WatchdogSignal=6
Id=containerd.service
Names=containerd.service
Requires=sysinit.target system.slice
WantedBy=multi-user.target
BoundBy=docker.service
Conflicts=shutdown.target
Before=shutdown.target docker.service multi-user.target
After=network.target sysinit.target system.slice systemd-journald.socket basic.target
Documentation=https://containerd.io
Description=containerd container runtime
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/lib/systemd/system/containerd.service
UnitFileState=enabled
UnitFilePreset=enabled
StateChangeTimestamp=Tue 2019-09-10 08:32:07 UTC
StateChangeTimestampMonotonic=322479789
InactiveExitTimestamp=Tue 2019-09-10 08:32:07 UTC
InactiveExitTimestampMonotonic=322474060
ActiveEnterTimestamp=Tue 2019-09-10 08:32:07 UTC
ActiveEnterTimestampMonotonic=322479789
ActiveExitTimestamp=Tue 2019-09-10 08:24:55 UTC
ActiveExitTimestampMonotonic=43695663
InactiveEnterTimestamp=Tue 2019-09-10 08:24:55 UTC
InactiveEnterTimestampMonotonic=43695663
CanStart=yes
CanStop=yes
CanReload=no
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
NeedDaemonReload=no
JobTimeoutUSec=infinity
JobRunningTimeoutUSec=infinity
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Tue 2019-09-10 08:32:07 UTC
ConditionTimestampMonotonic=322470519
AssertTimestamp=Tue 2019-09-10 08:32:07 UTC
AssertTimestampMonotonic=322470520
Transient=no
Perpetual=no
StartLimitIntervalUSec=10s
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
FailureActionExitStatus=-1
SuccessAction=none
SuccessActionExitStatus=-1
InvocationID=e725f792a03843b5a599287d8d595ff0
CollectMode=inactive

Output of "cat /etc/containerd/config.toml":

disabled_plugins = ["cri"]

#root = "/var/lib/containerd"
#state = "/run/containerd"
#subreaper = true
#oom_score = 0

#[grpc]
#  address = "/run/containerd/containerd.sock"
#  uid = 0
#  gid = 0

#[debug]
#  address = "/run/containerd/debug.sock"
#  uid = 0
#  gid = 0
#  level = "info"

Packages

/usr/bin/dpkg-query: 1: /usr/bin/dpkg-query: Syntax error: Unterminated quoted string

No rpm

The text was updated successfully, but these errors were encountered:

devimc · 2019-09-10T12:30:03Z

@amonsifr seems like your system doesn't support KVM. I got this from the log message Could not access KVM kernel module: No such file or directory. Try loading the KVM kernel module.

cc @Pennyzct @jongwu

amonsifr · 2019-09-10T12:44:25Z

Thank you for your prompt answer, I thought my kernel support kvm? I have this in in .config file : CONFIG_VIRTUALIZATION=y CONFIG_KVM=y CONFIG_KVM_ARM_HOST=y CONFIG_KVM_ARM_PMU=y CONFIG_KVM_INDIRECT_VECTORS=y CONFIG_VHOST_NET=m CONFIG_VHOST_VSOCK=m CONFIG_VHOST=m I have put kvm in built-in module, do you think this is a problem ?

Pennyzct · 2019-09-11T01:31:06Z

you may want to check the kata-runtime kata-check command, it will try to evaluate if you system could use KVM to build a VM. ;)
BTW, I, and my colleague, @jongwu, is also trying to run kata containers in Respberry 4, and the official kernel will be for 32bit. Is this your customized 64bit kernel? Happy to collaborate~~~~

jongwu · 2019-09-11T01:45:16Z

good job @amonsifr . I have a pi4 but I find there is no official or third party linux distribution for arm64. so how do you install this ubuntu 19.04 on pi4. I can build a environment like you and test kata.
as far as your issue, I think you can run a vm using qemu first to test if the qemu works, then you can run kata without docker, just using "kata-runtime run "container-name", you need rootfs and config file at side.
also you can grab the command line of qemu when run kata and run these command line by hand to trace.

amonsifr · 2019-09-11T06:25:23Z

sudo kata-runtime kata-check
WARN[0000] VM memory (512MB) smaller than image "/usr/share/kata-containers/kata-containers-2019-08-28-14:34:51.381609631+0000-64caa3f" size (1024MB)
System is capable of running Kata Containers
System can currently create Kata Containers

for the 64 bit kernel I have started with the following page:
https://blog.cloudkernels.net/posts/rpi4-64bit-image/

Pennyzct · 2019-09-11T06:58:51Z

You may prefer the initrd as your guest rootfs. it will be much smaller than image.
And you can decrease the VM memory in configuration.toml, the default value will be 2GB.

amonsifr · 2019-09-11T12:48:21Z

I have used the initrd as my guest rootfs and this is better I haven't anymore the warning about the problem of VM memory size.

I have tried :
sudo kata-runtime --log /tmp/kata4.log run hardcore_noyce
fail to launch qemu: exit status 1, error messages from qemu log:

in the log file I have found:
error="open /run/vc/sbs/hardcore_noyce/devices.json: no such file or directory
Do you know what I am doing wrong ?

I haven't found any devices.json file on the raspberry...

jodh-intel · 2019-09-11T12:58:00Z

Hi @amonsifr - please could you re-run the sudo kata-collect-data.sh and paste the output in a comment here?

amonsifr · 2019-09-11T13:03:24Z

Show kata-collect-data.sh details

Meta details

Running kata-collect-data.sh version 1.9.0-alpha1 (commit 0cc1a6f6ed0228e6c70b1503436172d96a452f01) at 2019-09-11.13:00:01.689683522+0000.

Runtime is /usr/local/bin/kata-runtime.

`kata-env`

Output of "/usr/local/bin/kata-runtime kata-env":

[Meta]
  Version = "1.0.23"

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

[Hypervisor]
  MachineType = "virt"
  Version = "QEMU emulator version 4.1.50 (v4.1.0-733-g89ea03a7dc-dirty)\nCopyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers"
  Path = "/usr/bin/qemu-system-aarch64"
  BlockDeviceDriver = "virtio-scsi"
  EntropySource = "/dev/urandom"
  Msize9p = 8192
  MemorySlots = 10
  Debug = true
  UseVSock = false
  SharedFS = "virtio-9p"

[Image]
  Path = ""

[Kernel]
  Path = "/usr/share/kata-containers/vmlinuz-4.19.65-49"
  Parameters = "agent.log=debug agent.log=debug initcall_debug"

[Initrd]
  Path = "/usr/share/kata-containers/kata-containers-initrd-2019-09-11-08:50:12.713623899+0000-c8e6054"

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

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

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

[Host]
  Kernel = "5.2.10-v8+"
  Architecture = "arm64"
  VMContainerCapable = true
  SupportVSocks = true
  [Host.Distro]
    Name = "Ubuntu"
    Version = "19.04"
  [Host.CPU]
    Vendor = "ARM Limited"
    Model = "v8"

[Netmon]
  Version = "kata-netmon version 1.9.0-alpha1"
  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-system-aarch64"
kernel = "/usr/share/kata-containers/vmlinuz.container"
initrd = "/usr/share/kata-containers/kata-containers-initrd.img"
#image = "/usr/share/kata-containers/kata-containers.img"
machine_type = "virt"

# 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 = 1

# 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 = 0

# 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 = 512
#
# 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=false

# 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-system-aarch64"
kernel = "/usr/share/kata-containers/vmlinuz.container"
#initrd = "/usr/share/kata-containers/kata-containers-initrd.img"
image = "/usr/share/kata-containers/kata-containers.img"
machine_type = "virt"

# 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 = 1

# 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 = 0

# 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 = 512
#
# 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=false

# 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 " --version":

/usr/local/bin/kata-collect-data.sh: line 178: --version: command not found

systemd service

Image details

No image

Initrd details

---
osbuilder:
  url: "https://github.com/kata-containers/osbuilder"
  version: "unknown"
rootfs-creation-time: "Failed at 173: date -u -d@${SOURCE_DATE_EPOCH:-$(date +%s.%N)} '+%Y-%m-%dT%T.%N%zZ'"
description: "osbuilder rootfs"
file-format-version: "0.0.2"
architecture: "aarch64"
base-distro:
  name: "Alpine"
  version: "v3.7"
  packages:
    default:
      - "iptables"
    extra:

agent:
  url: "https://github.com/kata-containers/agent"
  name: "kata-agent"
  version: "1.9.0-alpha1-dc235c3d740682dd83402e01a0bc9eb7827b7a6e"
  agent-is-init-daemon: "yes"

Logfiles

Runtime logs

Recent runtime problems found in system journal:

time="2019-09-11T08:56:00.930566392Z" level=error msg="open /home/tonio/config.json: no such file or directory" arch=arm64 command=run container=focused_blackburn name=kata-runtime pid=27648 source=runtime
time="2019-09-11T08:59:13.126020451Z" level=info msg="Unable to know if the system is running inside a VM" arch=arm64 command=run container=focused_blackburn name=kata-runtime pid=27693 source=virtcontainers
time="2019-09-11T08:59:13.197062648Z" level=debug msg="Could not retrieve anything from storage" arch=arm64 command=run container=focused_blackburn name=kata-runtime pid=27693 source=virtcontainers subsystem=kata_agent
time="2019-09-11T08:59:13.223517511Z" level=warning msg="load sandbox devices failed" arch=arm64 command=run container=focused_blackburn error="open /run/vc/sbs/focused_blackburn/devices.json: no such file or directory" name=kata-runtime pid=27693 sandbox=focused_blackburn sandboxid=focused_blackburn source=virtcontainers subsystem=sandbox
time="2019-09-11T08:59:13.430077625Z" level=error msg="Unable to launch /usr/bin/qemu-system-aarch64: exit status 1" arch=arm64 command=run container=focused_blackburn name=kata-runtime pid=27693 source=virtcontainers subsystem=qmp
time="2019-09-11T08:59:13.447146384Z" level=error arch=arm64 command=run container=focused_blackburn name=kata-runtime pid=27693 source=virtcontainers subsystem=qmp
time="2019-09-11T08:59:13.548591003Z" level=warning msg="sandox cgroups path is empty" arch=arm64 command=run container=focused_blackburn name=kata-runtime pid=27693 sandbox=focused_blackburn source=virtcontainers subsystem=sandbox
time="2019-09-11T08:59:13.668925791Z" level=warning msg="failed to cleanup netns" arch=arm64 command=run container=focused_blackburn error="failed to get netns /var/run/netns/cni-7d046e29-a5e3-129d-e796-8dbd4693424d: failed to Statfs \"/var/run/netns/cni-7d046e29-a5e3-129d-e796-8dbd4693424d\": no such file or directory" name=kata-runtime path=/var/run/netns/cni-7d046e29-a5e3-129d-e796-8dbd4693424d pid=27693 source=katautils
time="2019-09-11T08:59:13.68640375Z" level=error msg="fail to launch qemu: exit status 1, error messages from qemu log: " arch=arm64 command=run container=focused_blackburn name=kata-runtime pid=27693 source=runtime
time="2019-09-11T09:05:12.61779033Z" level=info msg="Unable to know if the system is running inside a VM" arch=arm64 command=run container=focused_blackburn name=kata-runtime pid=28615 source=virtcontainers
time="2019-09-11T09:05:12.660166629Z" level=debug msg="Could not retrieve anything from storage" arch=arm64 command=run container=focused_blackburn name=kata-runtime pid=28615 source=virtcontainers subsystem=kata_agent
time="2019-09-11T09:05:12.679559924Z" level=warning msg="load sandbox devices failed" arch=arm64 command=run container=focused_blackburn error="open /run/vc/sbs/focused_blackburn/devices.json: no such file or directory" name=kata-runtime pid=28615 sandbox=focused_blackburn sandboxid=focused_blackburn source=virtcontainers subsystem=sandbox
time="2019-09-11T09:05:12.957190753Z" level=error msg="Unable to launch /usr/bin/qemu-system-aarch64: exit status 1" arch=arm64 command=run container=focused_blackburn name=kata-runtime pid=28615 source=virtcontainers subsystem=qmp
time="2019-09-11T09:05:12.97073245Z" level=error arch=arm64 command=run container=focused_blackburn name=kata-runtime pid=28615 source=virtcontainers subsystem=qmp
time="2019-09-11T09:05:13.404815699Z" level=warning msg="sandox cgroups path is empty" arch=arm64 command=run container=focused_blackburn name=kata-runtime pid=28615 sandbox=focused_blackburn source=virtcontainers subsystem=sandbox
time="2019-09-11T09:05:13.497549745Z" level=warning msg="failed to cleanup netns" arch=arm64 command=run container=focused_blackburn error="failed to get netns /var/run/netns/cni-4fffaca4-f48a-f0df-7b40-c6ed651ebeeb: failed to Statfs \"/var/run/netns/cni-4fffaca4-f48a-f0df-7b40-c6ed651ebeeb\": no such file or directory" name=kata-runtime path=/var/run/netns/cni-4fffaca4-f48a-f0df-7b40-c6ed651ebeeb pid=28615 source=katautils
time="2019-09-11T09:05:13.519222872Z" level=error msg="fail to launch qemu: exit status 1, error messages from qemu log: " arch=arm64 command=run container=focused_blackburn name=kata-runtime pid=28615 source=runtime
time="2019-09-11T10:01:54.297942235Z" level=info msg="Unable to know if the system is running inside a VM" arch=arm64 command=create container=f9e546d51bc0fd4712afd18d4d4a98b4fe855721b214555e53afed23b4a3014a name=kata-runtime pid=2225 source=virtcontainers
time="2019-09-11T10:01:54.298579066Z" level=debug msg="Could not retrieve anything from storage" arch=arm64 command=create container=f9e546d51bc0fd4712afd18d4d4a98b4fe855721b214555e53afed23b4a3014a name=kata-runtime pid=2225 source=virtcontainers subsystem=kata_agent
time="2019-09-11T10:01:54.298722121Z" level=warning msg="load sandbox devices failed" arch=arm64 command=create container=f9e546d51bc0fd4712afd18d4d4a98b4fe855721b214555e53afed23b4a3014a error="open /run/vc/sbs/f9e546d51bc0fd4712afd18d4d4a98b4fe855721b214555e53afed23b4a3014a/devices.json: no such file or directory" name=kata-runtime pid=2225 sandbox=f9e546d51bc0fd4712afd18d4d4a98b4fe855721b214555e53afed23b4a3014a sandboxid=f9e546d51bc0fd4712afd18d4d4a98b4fe855721b214555e53afed23b4a3014a source=virtcontainers subsystem=sandbox
time="2019-09-11T10:01:54.884455707Z" level=error msg="Unable to launch /usr/bin/qemu-system-aarch64: exit status 1" arch=arm64 command=create container=f9e546d51bc0fd4712afd18d4d4a98b4fe855721b214555e53afed23b4a3014a name=kata-runtime pid=2225 source=virtcontainers subsystem=qmp
time="2019-09-11T10:01:54.884695095Z" level=error arch=arm64 command=create container=f9e546d51bc0fd4712afd18d4d4a98b4fe855721b214555e53afed23b4a3014a name=kata-runtime pid=2225 source=virtcontainers subsystem=qmp
time="2019-09-11T10:01:54.977974809Z" level=warning msg="sandox cgroups path is empty" arch=arm64 command=create container=f9e546d51bc0fd4712afd18d4d4a98b4fe855721b214555e53afed23b4a3014a name=kata-runtime pid=2225 sandbox=f9e546d51bc0fd4712afd18d4d4a98b4fe855721b214555e53afed23b4a3014a source=virtcontainers subsystem=sandbox
time="2019-09-11T10:01:54.980904389Z" level=warning msg="failed to cleanup netns" arch=arm64 command=create container=f9e546d51bc0fd4712afd18d4d4a98b4fe855721b214555e53afed23b4a3014a error="failed to get netns /var/run/netns/cni-168dc20a-5cf2-4e22-c8e3-e4e4950b570e: failed to Statfs \"/var/run/netns/cni-168dc20a-5cf2-4e22-c8e3-e4e4950b570e\": no such file or directory" name=kata-runtime path=/var/run/netns/cni-168dc20a-5cf2-4e22-c8e3-e4e4950b570e pid=2225 source=katautils
time="2019-09-11T10:01:54.981289962Z" level=error msg="fail to launch qemu: exit status 1, error messages from qemu log: " arch=arm64 command=create container=f9e546d51bc0fd4712afd18d4d4a98b4fe855721b214555e53afed23b4a3014a name=kata-runtime pid=2225 source=runtime
time="2019-09-11T10:09:05.072676552Z" level=info msg="Unable to know if the system is running inside a VM" arch=arm64 command=create container=594dd6562c3fe763f35ea855ca8ff24df2c3ab272e0535b8f912ea810be66bac name=kata-runtime pid=2326 source=virtcontainers
time="2019-09-11T10:09:05.073767914Z" level=debug msg="Could not retrieve anything from storage" arch=arm64 command=create container=594dd6562c3fe763f35ea855ca8ff24df2c3ab272e0535b8f912ea810be66bac name=kata-runtime pid=2326 source=virtcontainers subsystem=kata_agent
time="2019-09-11T10:09:05.074062819Z" level=warning msg="load sandbox devices failed" arch=arm64 command=create container=594dd6562c3fe763f35ea855ca8ff24df2c3ab272e0535b8f912ea810be66bac error="open /run/vc/sbs/594dd6562c3fe763f35ea855ca8ff24df2c3ab272e0535b8f912ea810be66bac/devices.json: no such file or directory" name=kata-runtime pid=2326 sandbox=594dd6562c3fe763f35ea855ca8ff24df2c3ab272e0535b8f912ea810be66bac sandboxid=594dd6562c3fe763f35ea855ca8ff24df2c3ab272e0535b8f912ea810be66bac source=virtcontainers subsystem=sandbox
time="2019-09-11T10:09:05.189917452Z" level=error msg="Unable to launch /usr/bin/qemu-system-aarch64: exit status 1" arch=arm64 command=create container=594dd6562c3fe763f35ea855ca8ff24df2c3ab272e0535b8f912ea810be66bac name=kata-runtime pid=2326 source=virtcontainers subsystem=qmp
time="2019-09-11T10:09:05.190150839Z" level=error arch=arm64 command=create container=594dd6562c3fe763f35ea855ca8ff24df2c3ab272e0535b8f912ea810be66bac name=kata-runtime pid=2326 source=virtcontainers subsystem=qmp
time="2019-09-11T10:09:05.267554068Z" level=warning msg="sandox cgroups path is empty" arch=arm64 command=create container=594dd6562c3fe763f35ea855ca8ff24df2c3ab272e0535b8f912ea810be66bac name=kata-runtime pid=2326 sandbox=594dd6562c3fe763f35ea855ca8ff24df2c3ab272e0535b8f912ea810be66bac source=virtcontainers subsystem=sandbox
time="2019-09-11T10:09:05.272059477Z" level=warning msg="failed to cleanup netns" arch=arm64 command=create container=594dd6562c3fe763f35ea855ca8ff24df2c3ab272e0535b8f912ea810be66bac error="failed to get netns /var/run/netns/cni-7ff0b526-ff24-73c1-5b3d-16f4814d222d: failed to Statfs \"/var/run/netns/cni-7ff0b526-ff24-73c1-5b3d-16f4814d222d\": no such file or directory" name=kata-runtime path=/var/run/netns/cni-7ff0b526-ff24-73c1-5b3d-16f4814d222d pid=2326 source=katautils
time="2019-09-11T10:09:05.272837415Z" level=error msg="fail to launch qemu: exit status 1, error messages from qemu log: " arch=arm64 command=create container=594dd6562c3fe763f35ea855ca8ff24df2c3ab272e0535b8f912ea810be66bac name=kata-runtime pid=2326 source=runtime
time="2019-09-11T12:19:43.24780768Z" level=error msg="open /home/tonio/config.json: no such file or directory" arch=arm64 command=run container=hardcore_noyce name=kata-runtime pid=2683 source=runtime
time="2019-09-11T12:19:52.40975463Z" level=info msg="Unable to know if the system is running inside a VM" arch=arm64 command=run container=hardcore_noyce name=kata-runtime pid=2700 source=virtcontainers
time="2019-09-11T12:19:52.410182162Z" level=debug msg="Could not retrieve anything from storage" arch=arm64 command=run container=hardcore_noyce name=kata-runtime pid=2700 source=virtcontainers subsystem=kata_agent
time="2019-09-11T12:19:52.410294143Z" level=warning msg="load sandbox devices failed" arch=arm64 command=run container=hardcore_noyce error="open /run/vc/sbs/hardcore_noyce/devices.json: no such file or directory" name=kata-runtime pid=2700 sandbox=hardcore_noyce sandboxid=hardcore_noyce source=virtcontainers subsystem=sandbox
time="2019-09-11T12:19:52.459901769Z" level=error msg="Unable to launch /usr/bin/qemu-system-aarch64: exit status 1" arch=arm64 command=run container=hardcore_noyce name=kata-runtime pid=2700 source=virtcontainers subsystem=qmp
time="2019-09-11T12:19:52.460617279Z" level=error arch=arm64 command=run container=hardcore_noyce name=kata-runtime pid=2700 source=virtcontainers subsystem=qmp
time="2019-09-11T12:19:52.462748442Z" level=warning msg="sandox cgroups path is empty" arch=arm64 command=run container=hardcore_noyce name=kata-runtime pid=2700 sandbox=hardcore_noyce source=virtcontainers subsystem=sandbox
time="2019-09-11T12:19:52.466087703Z" level=warning msg="failed to cleanup netns" arch=arm64 command=run container=hardcore_noyce error="failed to get netns /var/run/netns/cni-fc0f2001-22a8-1835-b708-72b8200769dc: failed to Statfs \"/var/run/netns/cni-fc0f2001-22a8-1835-b708-72b8200769dc\": no such file or directory" name=kata-runtime path=/var/run/netns/cni-fc0f2001-22a8-1835-b708-72b8200769dc pid=2700 source=katautils
time="2019-09-11T12:19:52.468001961Z" level=error msg="fail to launch qemu: exit status 1, error messages from qemu log: " arch=arm64 command=run container=hardcore_noyce name=kata-runtime pid=2700 source=runtime
time="2019-09-11T12:21:28.790936663Z" level=info msg="Unable to know if the system is running inside a VM" arch=arm64 command=run container=hardcore_noyce name=kata-runtime pid=2763 source=virtcontainers
time="2019-09-11T12:21:28.836992421Z" level=debug msg="Could not retrieve anything from storage" arch=arm64 command=run container=hardcore_noyce name=kata-runtime pid=2763 source=virtcontainers subsystem=kata_agent
time="2019-09-11T12:21:28.857149672Z" level=warning msg="load sandbox devices failed" arch=arm64 command=run container=hardcore_noyce error="open /run/vc/sbs/hardcore_noyce/devices.json: no such file or directory" name=kata-runtime pid=2763 sandbox=hardcore_noyce sandboxid=hardcore_noyce source=virtcontainers subsystem=sandbox
time="2019-09-11T12:21:29.024001219Z" level=error msg="Unable to launch /usr/bin/qemu-system-aarch64: exit status 1" arch=arm64 command=run container=hardcore_noyce name=kata-runtime pid=2763 source=virtcontainers subsystem=qmp
time="2019-09-11T12:21:29.739426368Z" level=error arch=arm64 command=run container=hardcore_noyce name=kata-runtime pid=2763 source=virtcontainers subsystem=qmp
time="2019-09-11T12:21:29.811223707Z" level=warning msg="sandox cgroups path is empty" arch=arm64 command=run container=hardcore_noyce name=kata-runtime pid=2763 sandbox=hardcore_noyce source=virtcontainers subsystem=sandbox
time="2019-09-11T12:21:29.879934524Z" level=warning msg="failed to cleanup netns" arch=arm64 command=run container=hardcore_noyce error="failed to get netns /var/run/netns/cni-7414b8d3-032b-71d4-3475-cd5fb7e4da33: failed to Statfs \"/var/run/netns/cni-7414b8d3-032b-71d4-3475-cd5fb7e4da33\": no such file or directory" name=kata-runtime path=/var/run/netns/cni-7414b8d3-032b-71d4-3475-cd5fb7e4da33 pid=2763 source=katautils
time="2019-09-11T12:21:29.895287011Z" level=error msg="fail to launch qemu: exit status 1, error messages from qemu log: " arch=arm64 command=run container=hardcore_noyce name=kata-runtime pid=2763 source=runtime

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:32:20 2019
 OS/Arch:           linux/arm64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.2
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.8
  Git commit:       6a30dfc
  Built:            Thu Aug 29 05:30:52 2019
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Output of "docker info":

Client:
 Debug Mode: false

Server:
 Containers: 13
  Running: 0
  Paused: 0
  Stopped: 13
 Images: 14
 Server Version: 19.03.2
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: kata-runtime runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 5.2.10-v8+
 Operating System: Ubuntu 19.04
 OSType: linux
 Architecture: aarch64
 CPUs: 4
 Total Memory: 1.84GiB
 Name: ubuntu
 ID: 2COC:BESL:UDHX:3BYE:K5RD:WHKK:I7BI:7EO3:3HWX:6UZQ:RGYC:LHBE
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 21
  Goroutines: 35
  System Time: 2019-09-11T13:00:07.664307635Z
  EventsListeners: 0
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No swap limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support

Output of "systemctl show docker":

Type=notify
Restart=always
NotifyAccess=main
RestartUSec=2s
TimeoutStartUSec=infinity
TimeoutStopUSec=infinity
RuntimeMaxUSec=infinity
WatchdogUSec=0
WatchdogTimestampMonotonic=0
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=2040
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
StatusErrno=0
Result=success
UID=[not set]
GID=[not set]
NRestarts=0
ExecMainStartTimestamp=Wed 2019-09-11 10:01:23 UTC
ExecMainStartTimestampMonotonic=12400756148
ExecMainExitTimestampMonotonic=0
ExecMainPID=2040
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/bin/dockerd ; argv[]=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock --add-runtime kata-runtime=/usr/local/bin/kata-runtime ; ignore_errors=no ; start_time=[Wed 2019-09-11 10:01:23 UTC] ; stop_time=[n/a] ; pid=2040 ; 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
ControlGroup=/system.slice/docker.service
MemoryCurrent=136118272
CPUUsageNSec=[not set]
TasksCurrent=[not set]
IPIngressBytes=18446744073709551615
IPIngressPackets=18446744073709551615
IPEgressBytes=18446744073709551615
IPEgressPackets=18446744073709551615
Delegate=yes
DelegateControllers=cpu cpuacct io blkio memory devices pids bpf-firewall bpf-devices
CPUAccounting=no
CPUWeight=[not set]
StartupCPUWeight=[not set]
CPUShares=[not set]
StartupCPUShares=[not set]
CPUQuotaPerSecUSec=infinity
IOAccounting=no
IOWeight=[not set]
StartupIOWeight=[not set]
BlockIOAccounting=no
BlockIOWeight=[not set]
StartupBlockIOWeight=[not set]
MemoryAccounting=yes
MemoryMin=0
MemoryLow=0
MemoryHigh=infinity
MemoryMax=infinity
MemorySwapMax=infinity
MemoryLimit=infinity
DevicePolicy=auto
TasksAccounting=yes
TasksMax=infinity
IPAccounting=no
UMask=0022
LimitCPU=infinity
LimitCPUSoft=infinity
LimitFSIZE=infinity
LimitFSIZESoft=infinity
LimitDATA=infinity
LimitDATASoft=infinity
LimitSTACK=infinity
LimitSTACKSoft=8388608
LimitCORE=infinity
LimitCORESoft=infinity
LimitRSS=infinity
LimitRSSSoft=infinity
LimitNOFILE=infinity
LimitNOFILESoft=infinity
LimitAS=infinity
LimitASSoft=infinity
LimitNPROC=infinity
LimitNPROCSoft=infinity
LimitMEMLOCK=67108864
LimitMEMLOCKSoft=67108864
LimitLOCKS=infinity
LimitLOCKSSoft=infinity
LimitSIGPENDING=1613
LimitSIGPENDINGSoft=1613
LimitMSGQUEUE=819200
LimitMSGQUEUESoft=819200
LimitNICE=0
LimitNICESoft=0
LimitRTPRIO=0
LimitRTPRIOSoft=0
LimitRTTIME=infinity
LimitRTTIMESoft=infinity
OOMScoreAdjust=0
Nice=0
IOSchedulingClass=0
IOSchedulingPriority=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardInputData=
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SyslogLevel=6
SyslogFacility=3
LogLevelMax=-1
LogRateLimitIntervalUSec=0
LogRateLimitBurst=0
SecureBits=0
CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config cap_mknod cap_lease cap_audit_write cap_audit_control cap_setfcap cap_mac_override cap_mac_admin cap_syslog cap_wake_alarm cap_block_suspend
AmbientCapabilities=
DynamicUser=no
RemoveIPC=no
MountFlags=
PrivateTmp=no
PrivateDevices=no
ProtectKernelTunables=no
ProtectKernelModules=no
ProtectControlGroups=no
PrivateNetwork=no
PrivateUsers=no
PrivateMounts=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
LockPersonality=no
RuntimeDirectoryPreserve=no
RuntimeDirectoryMode=0755
StateDirectoryMode=0755
CacheDirectoryMode=0755
LogsDirectoryMode=0755
ConfigurationDirectoryMode=0755
MemoryDenyWriteExecute=no
RestrictRealtime=no
RestrictNamespaces=no
MountAPIVFS=no
KeyringMode=private
KillMode=process
KillSignal=15
FinalKillSignal=9
SendSIGKILL=yes
SendSIGHUP=no
WatchdogSignal=6
Id=docker.service
Names=docker.service
Requires=docker.socket sysinit.target system.slice
Wants=network-online.target
BindsTo=containerd.service
WantedBy=multi-user.target
ConsistsOf=docker.socket
Conflicts=shutdown.target
Before=multi-user.target shutdown.target
After=docker.socket firewalld.service sysinit.target basic.target network-online.target systemd-journald.socket system.slice containerd.service
TriggeredBy=docker.socket
Documentation=https://docs.docker.com
Description=Docker Application Container Engine
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/lib/systemd/system/docker.service
UnitFileState=enabled
UnitFilePreset=enabled
StateChangeTimestamp=Wed 2019-09-11 10:01:29 UTC
StateChangeTimestampMonotonic=12406218737
InactiveExitTimestamp=Wed 2019-09-11 10:01:23 UTC
InactiveExitTimestampMonotonic=12400757471
ActiveEnterTimestamp=Wed 2019-09-11 10:01:29 UTC
ActiveEnterTimestampMonotonic=12406218737
ActiveExitTimestamp=Wed 2019-09-11 10:01:23 UTC
ActiveExitTimestampMonotonic=12400714048
InactiveEnterTimestamp=Wed 2019-09-11 10:01:23 UTC
InactiveEnterTimestampMonotonic=12400726479
CanStart=yes
CanStop=yes
CanReload=yes
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
NeedDaemonReload=no
JobTimeoutUSec=infinity
JobRunningTimeoutUSec=infinity
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Wed 2019-09-11 10:01:23 UTC
ConditionTimestampMonotonic=12400750568
AssertTimestamp=Wed 2019-09-11 10:01:23 UTC
AssertTimestampMonotonic=12400750569
Transient=no
Perpetual=no
StartLimitIntervalUSec=1min
StartLimitBurst=3
StartLimitAction=none
FailureAction=none
FailureActionExitStatus=-1
SuccessAction=none
SuccessActionExitStatus=-1
InvocationID=792f293d6dfe45b2adbdeefaf87729d0
CollectMode=inactive

No kubectl
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
RuntimeMaxUSec=infinity
WatchdogUSec=0
WatchdogTimestampMonotonic=0
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=570
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
StatusErrno=0
Result=success
UID=[not set]
GID=[not set]
NRestarts=0
ExecMainStartTimestamp=Wed 2019-09-11 06:35:19 UTC
ExecMainStartTimestampMonotonic=36844172
ExecMainExitTimestampMonotonic=0
ExecMainPID=570
ExecMainCode=0
ExecMainStatus=0
ExecStartPre={ path=/sbin/modprobe ; argv[]=/sbin/modprobe overlay ; ignore_errors=yes ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
ExecStart={ path=/usr/bin/containerd ; argv[]=/usr/bin/containerd ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
Slice=system.slice
ControlGroup=/system.slice/containerd.service
MemoryCurrent=127205376
CPUUsageNSec=[not set]
TasksCurrent=[not set]
IPIngressBytes=18446744073709551615
IPIngressPackets=18446744073709551615
IPEgressBytes=18446744073709551615
IPEgressPackets=18446744073709551615
Delegate=yes
DelegateControllers=cpu cpuacct io blkio memory devices pids bpf-firewall bpf-devices
CPUAccounting=no
CPUWeight=[not set]
StartupCPUWeight=[not set]
CPUShares=[not set]
StartupCPUShares=[not set]
CPUQuotaPerSecUSec=infinity
IOAccounting=no
IOWeight=[not set]
StartupIOWeight=[not set]
BlockIOAccounting=no
BlockIOWeight=[not set]
StartupBlockIOWeight=[not set]
MemoryAccounting=yes
MemoryMin=0
MemoryLow=0
MemoryHigh=infinity
MemoryMax=infinity
MemorySwapMax=infinity
MemoryLimit=infinity
DevicePolicy=auto
TasksAccounting=yes
TasksMax=infinity
IPAccounting=no
UMask=0022
LimitCPU=infinity
LimitCPUSoft=infinity
LimitFSIZE=infinity
LimitFSIZESoft=infinity
LimitDATA=infinity
LimitDATASoft=infinity
LimitSTACK=infinity
LimitSTACKSoft=8388608
LimitCORE=infinity
LimitCORESoft=infinity
LimitRSS=infinity
LimitRSSSoft=infinity
LimitNOFILE=1048576
LimitNOFILESoft=1048576
LimitAS=infinity
LimitASSoft=infinity
LimitNPROC=infinity
LimitNPROCSoft=infinity
LimitMEMLOCK=67108864
LimitMEMLOCKSoft=67108864
LimitLOCKS=infinity
LimitLOCKSSoft=infinity
LimitSIGPENDING=1613
LimitSIGPENDINGSoft=1613
LimitMSGQUEUE=819200
LimitMSGQUEUESoft=819200
LimitNICE=0
LimitNICESoft=0
LimitRTPRIO=0
LimitRTPRIOSoft=0
LimitRTTIME=infinity
LimitRTTIMESoft=infinity
OOMScoreAdjust=0
Nice=0
IOSchedulingClass=0
IOSchedulingPriority=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardInputData=
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SyslogLevel=6
SyslogFacility=3
LogLevelMax=-1
LogRateLimitIntervalUSec=0
LogRateLimitBurst=0
SecureBits=0
CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config cap_mknod cap_lease cap_audit_write cap_audit_control cap_setfcap cap_mac_override cap_mac_admin cap_syslog cap_wake_alarm cap_block_suspend
AmbientCapabilities=
DynamicUser=no
RemoveIPC=no
MountFlags=
PrivateTmp=no
PrivateDevices=no
ProtectKernelTunables=no
ProtectKernelModules=no
ProtectControlGroups=no
PrivateNetwork=no
PrivateUsers=no
PrivateMounts=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
LockPersonality=no
RuntimeDirectoryPreserve=no
RuntimeDirectoryMode=0755
StateDirectoryMode=0755
CacheDirectoryMode=0755
LogsDirectoryMode=0755
ConfigurationDirectoryMode=0755
MemoryDenyWriteExecute=no
RestrictRealtime=no
RestrictNamespaces=no
MountAPIVFS=no
KeyringMode=private
KillMode=process
KillSignal=15
FinalKillSignal=9
SendSIGKILL=yes
SendSIGHUP=no
WatchdogSignal=6
Id=containerd.service
Names=containerd.service
Requires=sysinit.target system.slice
WantedBy=multi-user.target
BoundBy=docker.service
Conflicts=shutdown.target
Before=shutdown.target docker.service multi-user.target
After=system.slice network.target systemd-journald.socket sysinit.target basic.target
Documentation=https://containerd.io
Description=containerd container runtime
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/lib/systemd/system/containerd.service
UnitFileState=enabled
UnitFilePreset=enabled
StateChangeTimestamp=Wed 2019-09-11 06:35:19 UTC
StateChangeTimestampMonotonic=36844460
InactiveExitTimestamp=Wed 2019-09-11 06:35:19 UTC
InactiveExitTimestampMonotonic=36668623
ActiveEnterTimestamp=Wed 2019-09-11 06:35:19 UTC
ActiveEnterTimestampMonotonic=36844460
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
NeedDaemonReload=no
JobTimeoutUSec=infinity
JobRunningTimeoutUSec=infinity
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Wed 2019-09-11 06:35:19 UTC
ConditionTimestampMonotonic=36663414
AssertTimestamp=Wed 2019-09-11 06:35:19 UTC
AssertTimestampMonotonic=36663416
Transient=no
Perpetual=no
StartLimitIntervalUSec=10s
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
FailureActionExitStatus=-1
SuccessAction=none
SuccessActionExitStatus=-1
InvocationID=542b1562ad5b4d1dab832105d43123b6
CollectMode=inactive

Output of "cat /etc/containerd/config.toml":

disabled_plugins = ["cri"]

#root = "/var/lib/containerd"
#state = "/run/containerd"
#subreaper = true
#oom_score = 0

#[grpc]
#  address = "/run/containerd/containerd.sock"
#  uid = 0
#  gid = 0

#[debug]
#  address = "/run/containerd/debug.sock"
#  uid = 0
#  gid = 0
#  level = "info"

Packages

/usr/bin/dpkg-query: 1: /usr/bin/dpkg-query: Syntax error: Unterminated quoted string

No rpm

amonsifr · 2019-09-13T16:06:59Z

Hello,

If you want to build the same environment as mine you can use the following set of scripts :
https://drive.google.com/open?id=1mgiXuAIBMUeYW0YH2FjeQ7ZDvurUAPmH

jongwu · 2019-09-16T10:46:08Z

thanks @amonsifr , I will try this.

jongwu · 2019-09-21T10:14:19Z

@amonsifr sorry to let wait so long.
I have tried kata on my respberry pi4. I can run kata now. I think your problem is lack of ram in your pi4.
I have 4G ram but you just 2G.
when I set my pi4 to 2G, I can't run kata too like you.

jongwu · 2019-09-21T10:25:36Z

good news @amonsifr
set image as your rootfs and set the default memory to 512M then kata will boot up.
I set my pi to 2G and do as above. it works. you can try it.

qemu: Add virtio-balloon device suppport.

…ta-containers#55) Add image build macro to change partition format for kernel's "dm-mod.create" command, and allow for igvm + image usecase in kata shim Signed-off-by: Dallas Delaney <dadelan@microsoft.com>

jodh-intel added this to To do in Issue backlog Aug 10, 2020

jodh-intel closed this as completed Apr 7, 2021

Issue backlog automation moved this from To do to Done Apr 7, 2021

dgibson pushed a commit to dgibson/kata-containers that referenced this issue Aug 5, 2021

Merge pull request kata-containers#55 from jcvenegas/virtio-balloon

5770f40

qemu: Add virtio-balloon device suppport.

raspberry pi 4 #55

raspberry pi 4 #55

Comments

amonsifr commented Sep 10, 2019

Description of problem

Expected result

Actual result

Meta details

kata-env

Runtime config files

Runtime default config files

Runtime config file contents

KSM throttler

version

systemd service

Image details

Initrd details

Logfiles

Runtime logs

Proxy logs

Shim logs

Throttler logs

Container manager details

Docker

containerd

Packages

devimc commented Sep 10, 2019

amonsifr commented Sep 10, 2019 via email • edited Loading

Pennyzct commented Sep 11, 2019

jongwu commented Sep 11, 2019

amonsifr commented Sep 11, 2019

Pennyzct commented Sep 11, 2019

amonsifr commented Sep 11, 2019

jodh-intel commented Sep 11, 2019

amonsifr commented Sep 11, 2019 • edited Loading

Meta details

kata-env

Runtime config files

Runtime default config files

Runtime config file contents

KSM throttler

version

systemd service

Image details

Initrd details

Logfiles

Runtime logs

Proxy logs

Shim logs

Throttler logs

Container manager details

Docker

containerd

Packages

amonsifr commented Sep 13, 2019 • edited Loading

jongwu commented Sep 16, 2019

jongwu commented Sep 21, 2019

jongwu commented Sep 21, 2019

`kata-env`

amonsifr commented Sep 10, 2019 via email •

edited

Loading

amonsifr commented Sep 11, 2019 •

edited

Loading

`kata-env`

amonsifr commented Sep 13, 2019 •

edited

Loading