crc: [BUG] Running on a self-compiled (vanilla) kernel might result in a seccomp_init() failed error

General information

  • OS: Linux / macOS / Windows Fedora 37

  • Hypervisor: KVM / Hyper-V / hyperkit / vfkit KVM

  • Did you run crc setup before starting it (Yes/No)? Yes

  • Running CRC on: Laptop / Baremetal-Server / VM Baremetal

CRC version

# Put `crc version` output here
$ crc version
CRC version: 2.15.0+cc05160
OpenShift version: 4.12.5
Podman version: 4.3.1

CRC status

# Put `crc status --log-level debug` output here
crc status --log-level debug
DEBU CRC version: 2.15.0+cc05160                  
DEBU OpenShift version: 4.12.5                    
DEBU Podman version: 4.3.1                        
DEBU Running 'crc status'                         
CRC VM:          Stopped
OpenShift:       Stopped (v4.12.0-0.okd-2023-02-18-033438)
RAM Usage:       0B of 0B
Disk Usage:      0B of 0B (Inside the CRC VM)
Cache Usage:     32.48GB
Cache Directory: /home/jj/.crc/cache

CRC config

# Put `crc config view` output here
crc config view
- consent-telemetry                     : no
- preset                                : okd

Host Operating System

# Put the output of `cat /etc/os-release` in case of Linux
# put the output of `sw_vers` in case of Mac
# Put the output of `systeminfo` in case of Windows

cat /etc/os-release
NAME="Fedora Linux"
VERSION="37 (Workstation Edition)"
ID=fedora
VERSION_ID=37
VERSION_CODENAME=""
PLATFORM_ID="platform:f37"
PRETTY_NAME="Fedora Linux 37 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:37"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f37/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=37
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=37
SUPPORT_END=2023-11-14
VARIANT="Workstation Edition"
VARIANT_ID=workstation

Steps to reproduce

  1. crc delete
  2. crc setup
  3. crc start

Expected

A running okd instance -

Actual

An error install

Logs

# tail -f crc.log 
-device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \
-audiodev '{"id":"audio1","driver":"none"}' \
-vnc 127.0.0.1:0,audiodev=audio1 \
-device '{"driver":"cirrus-vga","id":"video0","bus":"pcie.0","addr":"0x1"}' \
-object '{"qom-type":"rng-random","id":"objrng0","filename":"/dev/urandom"}' \
-device '{"driver":"virtio-rng-pci","rng":"objrng0","id":"rng0","bus":"pci.5","addr":"0x0"}' \
-msg timestamp=on
2023-04-04T14:08:33.267526Z qemu-system-x86_64: -device {"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"dir0","bus":"pci.1","addr":"0x0"}: Failed to write msg. Wrote -1 instead of 12.
2023-04-04T14:08:33.267547Z qemu-system-x86_64: -device {"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"dir0","bus":"pci.1","addr":"0x0"}: vhost_backend_init failed: Protocol error
2023-04-04 14:08:33.333+0000: shutting down, reason=failed
---
[root@darkstar qemu]# tail -f crc-fs0-virtiofsd.log
seccomp_init() failed
virtio_session_mount: Waiting for vhost-user socket connection...
virtio_session_mount: Received vhost-user socket connection
seccomp_init() failed
virtio_session_mount: Waiting for vhost-user socket connection...
virtio_session_mount: Received vhost-user socket connection
seccomp_init() failed
virtio_session_mount: Waiting for vhost-user socket connection...
virtio_session_mount: Received vhost-user socket connection
seccomp_init() failed

Before gather the logs try following if that fix your issue

$ crc delete -f
$ crc cleanup
$ crc setup
$ crc start --log-level debug

Please consider posting the output of crc start --log-level debug on http://gist.github.com/ and post the link in the issue.

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 25 (13 by maintainers)

Most upvoted comments

FYI @gbraad Ok, …

uname -a Linux darkstar 6.2.9 #8 SMP PREEMPT_DYNAMIC Tue Apr 4 18:56:10 CEST 2023 x86_64 x86_64 x86_64 GNU/Linux

`Enable seccomp to safely execute untrusted bytecode (SECCOMP) - Y -

And …

DEBU (crc) Calling .GetState                      
DEBU (crc) DBG | time="2023-04-04T18:59:04+02:00" level=debug msg="Getting current state..." 
DEBU (crc) DBG | time="2023-04-04T18:59:04+02:00" level=debug msg="Fetching VM..." 
INFO Starting CRC VM for openshift 4.12.5...      
DEBU Updating CRC VM configuration                
DEBU (crc) Calling .GetConfigRaw                  
DEBU (crc) Calling .Start                         
DEBU (crc) DBG | time="2023-04-04T18:59:04+02:00" level=debug msg="Starting VM crc" 
DEBU (crc) DBG | time="2023-04-04T18:59:04+02:00" level=debug msg="Validating network" 
DEBU (crc) DBG | time="2023-04-04T18:59:04+02:00" level=debug msg="Validating storage pool" 
DEBU (crc) DBG | time="2023-04-04T18:59:09+02:00" level=debug msg="GetIP called for crc" 
DEBU (crc) DBG | time="2023-04-04T18:59:09+02:00" level=debug msg="Getting current state..." 
DEBU (crc) DBG | time="2023-04-04T18:59:09+02:00" level=debug msg="IP address: 192.168.130.11" 
DEBU (crc) DBG | time="2023-04-04T18:59:09+02:00" level=info msg="Found IP for machine: 192.168.130.11" 
DEBU (crc) Calling .GetConfigRaw                  
DEBU Waiting for machine to be running, this may take a few minute`s... 
DEBU retry loop: attempt 0                        
DEBU (crc) Calling .GetState                      
DEBU (crc) DBG | time="2023-04-04T18:59:09+02:00" level=debug msg="Getting current state..." 
DEBU Machine is up and running!                   
DEBU (crc) Calling .GetState                      
DEBU (crc) DBG | time="2023-04-04T18:59:09+02:00" level=debug msg="Getting current state..." 
DEBU (crc) Calling .GetIP                         
DEBU (crc) DBG | time="2023-04-04T18:59:09+02:00" level=debug msg="GetIP called for crc" 
DEBU (crc) DBG | time="2023-04-04T18:59:09+02:00" level=debug msg="Getting current state..." 

OMG!

DEBU Unexpected operator status for ingress: EvaluationConditionsDetected 
DEBU openshift-apiserver operator not available, Reason: APIServices_Error 
INFO Operator openshift-apiserver is not yet available 
DEBU Unexpected operator status for ingress: EvaluationConditionsDetected 
INFO All operators are available. Ensuring stability... 
DEBU Unexpected operator status for ingress: EvaluationConditionsDetected 
INFO Operators are stable (2/3)...                
DEBU Unexpected operator status for ingress: EvaluationConditionsDetected 
INFO Operators are stable (3/3)...                
DEBU Cluster took 6m30.511855245s to stabilize    
INFO Adding crc-admin and crc-developer contexts to kubeconfig... 
DEBU Making call to close driver server           
DEBU (crc) Calling .Close                         
DEBU Successfully made call to close driver server 
DEBU Making call to close connection to plugin binary 
Started the OpenShift cluster.

The server is accessible via web console at:
  https://console-openshift-console.apps-crc.testing

Log in as administrator:
  Username: kubeadmin
  Password: xxxxxx

Log in as user:
  Username: developer
  Password: developer

Use the 'oc' command line interface:
  $ eval $(crc oc-env)
  $ oc login -u developer https://api.crc.testing:6443

@jsliacan No need to verify this for now; non-standard setup