Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CRC 1.27 fails to start VM - Unable to determine VM's IP address #2397

Closed
jmajulian21 opened this issue Jun 3, 2021 · 15 comments
Closed

CRC 1.27 fails to start VM - Unable to determine VM's IP address #2397

jmajulian21 opened this issue Jun 3, 2021 · 15 comments
Labels
kind/bug Something isn't working nested-virt To identify issues that are related to nested virtualization priority/minor status/stale Issue went stale; did not receive attention or no reply from the OP

Comments

@jmajulian21
Copy link

General information

  • OS: Linux
  • Hypervisor: KVM
  • Did you run crc setup before starting it (Yes/No)? Yes
  • Running CRC on: VM

CRC version

# Put `crc version` output here
CodeReady Containers version: 1.27.0+3d6bc39d
OpenShift version: 4.7.11 (embedded in executable)

## CRC config
# Put `crc config view` output here
- consent-telemetry                     : yes


## Host Operating System
NAME="Red Hat Enterprise Linux"
VERSION="8.4 (Ootpa)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="8.4"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Red Hat Enterprise Linux 8.4 (Ootpa)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:8.4:GA"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/red_hat_enterprise_linux/8/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_BUGZILLA_PRODUCT_VERSION=8.4
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.4"

### Steps to reproduce

  1. crc setup
  2. crc start

### Expected
State running without errors

### Actual
State running with errors

### Logs
INFO Starting CodeReady Containers VM for OpenShift 4.7.11...
DEBU Updating CRC VM configuration
DEBU (crc) Calling .GetConfigRaw
DEBU (crc) Calling .Start
DEBU (crc) DBG | time="2021-06-02T15:43:55-03:00" level=debug msg="Starting VM crc"
DEBU (crc) DBG | time="2021-06-02T15:43:55-03:00" level=debug msg="Validating network"
DEBU (crc) DBG | time="2021-06-02T15:43:55-03:00" level=debug msg="Validating storage pool"
DEBU (crc) DBG | time="2021-06-02T15:44:00-03:00" level=debug msg="GetIP called for crc"
DEBU (crc) DBG | time="2021-06-02T15:44:00-03:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2021-06-02T15:44:00-03:00" level=debug msg="Waiting for machine to come up 0/60"
DEBU (crc) DBG | time="2021-06-02T15:44:03-03:00" level=debug msg="GetIP called for crc"
DEBU (crc) DBG | time="2021-06-02T15:44:03-03:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2021-06-02T15:44:03-03:00" level=debug msg="Waiting for machine to come up 1/60"
DEBU (crc) DBG | time="2021-06-02T15:44:06-03:00" level=debug msg="GetIP called for crc"
DEBU (crc) DBG | time="2021-06-02T15:44:06-03:00" level=debug msg="Getting current state..."
.
.
DEBU (crc) DBG | time="2021-06-02T15:46:57-03:00" level=debug msg="Waiting for machine to come up 59/60"
DEBU (crc) DBG | time="2021-06-02T15:47:00-03:00" level=warning msg="Unable to determine VM's IP address, did it fail to boot?"
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
DEBU (crc) DBG | time="2021-06-02T15:47:00-03:00" level=debug msg="Closing plugin on server side"
Error starting machine: Error in driver during machine start: Unable to determine VM's IP address, did it fail to boot?

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.
@jmajulian21 jmajulian21 added kind/bug Something isn't working status/need triage labels Jun 3, 2021
@gbraad
Copy link
Contributor

gbraad commented Jun 4, 2021

Can you try running with the user network mode?
https://github.com/code-ready/crc/wiki/VPN-support--with-an--userland-network-stack

@praveenkumar
Copy link
Member

Check #2214 if you have recently updated or have docker clients.

@jmajulian21
Copy link
Author

Can you try running with the user network mode? Yes, I performed the steps for Linux and it did not work. (log attached)
https://github.com/code-ready/crc/wiki/VPN-support--with-an--userland-network-stack

crc-start.log
crc-deamon.log

@praveenkumar
Copy link
Member

@jmajulian21 This looks like vm is failed to start, not sure why. Can you check virsh -c qemu:///system list after crc start failed? And also look in journalctl -u libvirtd, and in /var/lib/libvirt/qemu/crc.log

@jmajulian21
Copy link
Author

@jmajulian21 This looks like vm is failed to start, not sure why. Can you check virsh -c qemu:///system list after crc start failed? And also look in journalctl -u libvirtd, and in /var/lib/libvirt/qemu/crc.log

virsh -c qemu:///system list
image

journalctl -u libvirtd
image

"/var/lib/libvirt/qemu/crc.log": The file does not exists

@Xplouder
Copy link

Xplouder commented Jun 9, 2021

Same problem here, cant find a way to workaround this.

@jmajulian21
Copy link
Author

Do you know another way to make a locally raised openshift? with CetOs or with windows? I need to know urgently :'(

@Xplouder
Copy link

@jmajulian21 try with a centos vagrant box. I managed to execute the setup and start commands successfully but did didn't work as expected. Next week i might keep debugging this.

@praveenkumar
Copy link
Member

praveenkumar commented Jun 14, 2021

@jmajulian21 I can see you are running it on a VM can you tell us what is the base OS and hypervisor? In the past we did see some issue with CRC when users tried to run it in nested #2082

@Xplouder Are you also running it some nested environment?

@praveenkumar praveenkumar added the nested-virt To identify issues that are related to nested virtualization label Jun 14, 2021
@Xplouder
Copy link

@praveenkumar i guess so. Tryed using arch but libvirt is not recognized by the binary even when im sure that it is installed. Then tryed use a centos vagrant box since its a supported distro but faced the problem described in this issue.

@praveenkumar
Copy link
Member

@praveenkumar i guess so. Tryed using arch but libvirt is not recognized by the binary even when im sure that it is installed. Then tryed use a centos vagrant box since its a supported distro but faced the problem described in this issue.

@Xplouder centos vagrant box directly on the host which have arch?

@Xplouder
Copy link

@praveenkumar yes, Manjaro to be more precise.

@stale
Copy link

stale bot commented Aug 23, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status/stale Issue went stale; did not receive attention or no reply from the OP label Aug 23, 2021
@stale stale bot closed this as completed Sep 7, 2021
@johnwmail
Copy link

Hi, any workaround? Thanks.

@praveenkumar
Copy link
Member

@johnwmail This is a closed issue, can you create a new issue using template and provide us more info around it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working nested-virt To identify issues that are related to nested virtualization priority/minor status/stale Issue went stale; did not receive attention or no reply from the OP
Projects
None yet
Development

No branches or pull requests

6 participants