Closed miguelmota closed 6 years ago
Changed the default_memory
in /usr/share/defaults/kata-containers/configuration.toml
which seems to solve that particular memory error, but now get
[fedora@ip-172-30-0-179 ~]$ sudo docker run busybox uname -a
docker: Error response from daemon: OCI runtime create failed: Could not access KVM kernel module: No such file or directory
qemu-lite-system-x86_64: failed to initialize KVM: No such file or directory: unknown.
Tried enabling the kernel module but got Operation not supported
[fedora@ip-172-30-0-179 ~]$ sudo modprobe kvm-intel
modprobe: ERROR: could not insert 'kvm_intel': Operation not supported
It looks like kata only works on bare metal? (trying it on an ec2 instance)
Do you open nest virtualization?
Not possible with EC2 (non baremetal), therefore closing issue
I'm confused - the output of kata-env
above suggests your environment would work. It certainly is possible to run Kata on a non-baremetal system.
To run all the hardware checks (which will tell you if the system is "Kata capable"):
$ sudo kata-runtime kata-check
See: https://github.com/kata-containers/runtime#hardware-requirements
@jodh-intel this is the output
[fedora@ip-172-30-0-179 ~]$ sudo kata-runtime kata-check
INFO[0000] CPU property found arch=amd64 description="Intel Architecture CPU" name=GenuineIntel pid=9485 source=runtime type=attribute
ERRO[0000] CPU property not found arch=amd64 description="Virtualization support" name=vmx pid=9485 source=runtime type=flag
INFO[0000] CPU property found arch=amd64 description="64Bit CPU" name=lm pid=9485 source=runtime type=flag
INFO[0000] CPU property found arch=amd64 description=SSE4.1 name=sse4_1 pid=9485 source=runtime type=flag
INFO[0000] kernel property found arch=amd64 description="Kernel-based Virtual Machine" name=kvm pid=9485 source=runtime type=module
INFO[0000] kernel property found arch=amd64 description="Host kernel accelerator for virtio" name=vhost pid=9485 source=runtime type=module
INFO[0000] kernel property found arch=amd64 description="Host kernel accelerator for virtio network" name=vhost_net pid=9485 source=runtime type=module
INFO[0000] kernel property found arch=amd64 description="Intel KVM" name=kvm_intel pid=9485 source=runtime type=module
doesn't look like nested vm is supported in this ec2 instance
[fedora@ip-172-30-0-179 ~]$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 63
model name : Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz
stepping : 2
microcode : 0x3c
cpu MHz : 2399.918
cache size : 30720 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm cpuid_fault invpcid_single pti fsgsbase bmi1 avx2 smep bmi2 erms invpcid xsaveopt
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass
bogomips : 4800.10
clflush size : 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:
@jodh-intel
@miguelmota As the kata-check output shows, you need vmx support on the host to run KVM based virtual machines, something which kata depends on internally.
/cc @jodh-intel However, I think runtime logs suggest something else. If not, can we work to make the log output better?
@miguelmota - thanks for the info. However, it looks like you only pasted part of the kata-check
output?
@jodh-intel my mistake, here's the full output
[fedora@ip-172-30-0-179 ~]$ sudo kata-runtime kata-check
INFO[0000] CPU property found arch=amd64 description="Intel Architecture CPU" name=GenuineIntel pid=10721 source=runtime type=attribute
ERRO[0000] CPU property not found arch=amd64 description="Virtualization support" name=vmx pid=10721 source=runtime type=flag
INFO[0000] CPU property found arch=amd64 description="64Bit CPU" name=lm pid=10721 source=runtime type=flag
INFO[0000] CPU property found arch=amd64 description=SSE4.1 name=sse4_1 pid=10721 source=runtime type=flag
INFO[0000] kernel property found arch=amd64 description="Kernel-based Virtual Machine" name=kvm pid=10721 source=runtime type=module
INFO[0000] kernel property found arch=amd64 description="Host kernel accelerator for virtio" name=vhost pid=10721 source=runtime type=module
INFO[0000] kernel property found arch=amd64 description="Host kernel accelerator for virtio network" name=vhost_net pid=10721 source=runtime type=module
INFO[0000] kernel property found arch=amd64 description="Intel KVM" name=kvm_intel pid=10721 source=runtime type=module
ERRO[0000] open /sys/module/kvm_intel/parameters/nested: no such file or directory arch=amd64 name=kata-runtime pid=10721 source=runtime
open /sys/module/kvm_intel/parameters/nested: no such file or directory
[fedora@ip-172-30-0-179 ~]$
@ydjainopensource - issue fixed on #660.
Description of problem
Getting error
invalid value of -m option maxmem: maximum memory size (0x7d600000) must be at least the initial memory size (0x80000000)
when following kata for docker on fedora tutorialExpected result
no failure
Actual result
[fedora@ip-172-30-0-179 ~]$ sudo kata-collect-data.sh
Meta details
Running
kata-collect-data.sh
version1.2.0 (commit 0bcb32f)
at2018-08-24.21:29:29.567206188+0000
.Runtime is
/usr/bin/kata-runtime
.kata-env
Output of "
/usr/bin/kata-runtime kata-env
":Runtime config files
Runtime default config files
Runtime config file contents
Config file
/etc/kata-containers/configuration.toml
not found Output of "cat "/usr/share/defaults/kata-containers/configuration.toml"
":Image details
Initrd details
No initrd
Logfiles
Runtime logs
Recent runtime problems found in system journal:
Proxy logs
No recent proxy problems found in system journal.
Shim logs
No recent shim problems found in system journal.
Container manager details
Have
docker
Docker
Output of "
docker version
":Output of "
docker info
":Output of "
systemctl show docker
":No
kubectl
Packages
No
dpkg
Haverpm
Output of "rpm -qa|egrep "(cc-oci-runtimecc-runtimerunv|kata-proxy|kata-runtime|kata-shim|kata-containers-image|linux-container|qemu-)"
":