[Help wanted] qemu-guest-agent don't start on coreOS

[souovan]

Hi y'all i'm trying to execute a crc lab on my laptop, but even following the documentation i cannot

I run the crc setup then crc start the below output:

INFO Loading bundle: crc_okd_libvirt_4.15.0-0.okd-2024-02-23-163410_amd64... 
INFO A CRC VM for OKD 4.15.0-0.okd-2024-02-23-163410 is already running 
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: PHX79-zmtbm-9PPmT-I9JMB

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


NOTE:
This cluster was built from OKD - The Community Distribution of Kubernetes that powers Red Hat OpenShift.
If you find an issue, please report it at https://github.com/openshift/okd

but when i try to access the web console or login through the cli i can't

i did some troubleshoot and checked that:

• the cluster is unreachable

van@fedora:~$ crc status
CRC VM:          Running
OpenShift:       Unreachable (v4.15.0-0.okd-2024-02-23-163410)
RAM Usage:       618.2MB of 10.95GB
Disk Usage:      21.5GB of 32.68GB (Inside the CRC VM)
Cache Usage:     27.69GB
Cache Directory: /home/van/.crc/cache

• the qemu-guest-agent service don't start at the crc VM

core@crc:~$ systemctl status qemu-guest-agent.service 
× qemu-guest-agent.service - QEMU Guest Agent
     Loaded: loaded (/etc/systemd/system/qemu-guest-agent.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Tue 2024-06-18 19:57:38 UTC; 8min ago
   Duration: 5ms
    Process: 1887 ExecStart=/usr/bin/qemu-ga --method=vsock-listen --path=3:1234 --blacklist=${BLACKLIST_RPC} -F${FSFREEZE_HOOK_PATHNAME} (code=exited, status=1/FAILURE)
   Main PID: 1887 (code=exited, status=1/FAILURE)
        CPU: 4ms

Jun 18 19:57:38 crc systemd[1]: qemu-guest-agent.service: Scheduled restart job, restart counter is at 5.
Jun 18 19:57:38 crc systemd[1]: qemu-guest-agent.service: Start request repeated too quickly.
Jun 18 19:57:38 crc systemd[1]: qemu-guest-agent.service: Failed with result 'exit-code'.
Jun 18 19:57:38 crc systemd[1]: Failed to start qemu-guest-agent.service - QEMU Guest Agent.

Here are the logs from journalctl -u qemu-guest-agent:

...
Jun 18 19:57:38 crc (qemu-ga)[1881]: qemu-guest-agent.service: Referenced but unset environment variable evaluates to an empty string: BLACKLIST_RPC
Jun 18 19:57:38 crc systemd[1]: Started qemu-guest-agent.service - QEMU Guest Agent.
Jun 18 19:57:38 crc qemu-ga[1881]: 1718740658.757133: critical: Failed to bind socket: Cannot assign requested address
Jun 18 19:57:38 crc qemu-ga[1881]: 1718740658.757163: critical: failed to create guest agent channel
Jun 18 19:57:38 crc qemu-ga[1881]: 1718740658.757168: critical: failed to initialize guest agent channel
Jun 18 19:57:38 crc systemd[1]: qemu-guest-agent.service: Main process exited, code=exited, status=1/FAILURE
Jun 18 19:57:38 crc systemd[1]: qemu-guest-agent.service: Failed with result 'exit-code'.
Jun 18 19:57:38 crc systemd[1]: qemu-guest-agent.service: Scheduled restart job, restart counter is at 3.
Jun 18 19:57:38 crc systemd[1]: Started qemu-guest-agent.service - QEMU Guest Agent.
Jun 18 19:57:38 crc (qemu-ga)[1884]: qemu-guest-agent.service: Referenced but unset environment variable evaluates to an empty string: BLACKLIST_RPC
Jun 18 19:57:38 crc qemu-ga[1884]: 1718740658.782650: critical: Failed to bind socket: Cannot assign requested address
Jun 18 19:57:38 crc qemu-ga[1884]: 1718740658.782683: critical: failed to create guest agent channel
Jun 18 19:57:38 crc qemu-ga[1884]: 1718740658.782687: critical: failed to initialize guest agent channel
Jun 18 19:57:38 crc systemd[1]: qemu-guest-agent.service: Main process exited, code=exited, status=1/FAILURE
Jun 18 19:57:38 crc systemd[1]: qemu-guest-agent.service: Failed with result 'exit-code'.
Jun 18 19:57:38 crc systemd[1]: qemu-guest-agent.service: Scheduled restart job, restart counter is at 4.
Jun 18 19:57:38 crc systemd[1]: Started qemu-guest-agent.service - QEMU Guest Agent.
Jun 18 19:57:38 crc (qemu-ga)[1887]: qemu-guest-agent.service: Referenced but unset environment variable evaluates to an empty string: BLACKLIST_RPC
Jun 18 19:57:38 crc qemu-ga[1887]: 1718740658.799548: critical: Failed to bind socket: Cannot assign requested address
Jun 18 19:57:38 crc qemu-ga[1887]: 1718740658.799580: critical: failed to create guest agent channel
Jun 18 19:57:38 crc qemu-ga[1887]: 1718740658.799584: critical: failed to initialize guest agent channel
Jun 18 19:57:38 crc systemd[1]: qemu-guest-agent.service: Main process exited, code=exited, status=1/FAILURE
Jun 18 19:57:38 crc systemd[1]: qemu-guest-agent.service: Failed with result 'exit-code'.
Jun 18 19:57:38 crc systemd[1]: qemu-guest-agent.service: Scheduled restart job, restart counter is at 5.
Jun 18 19:57:38 crc systemd[1]: qemu-guest-agent.service: Start request repeated too quickly.
Jun 18 19:57:38 crc systemd[1]: qemu-guest-agent.service: Failed with result 'exit-code'.
Jun 18 19:57:38 crc systemd[1]: Failed to start qemu-guest-agent.service - QEMU Guest Agent.

I don't know what i have to do in the following and appreciate any help or tips 😄

[cfergeau]

It's normal that qemu-guest-agent does not start when using crc on a linux host, crc-org/snc#914 should improve this.
It's not because of qemu-guest-agent that the cluster is unreachable.
crc delete && crc start --log-level debug could give more hints.