-
Notifications
You must be signed in to change notification settings - Fork 243
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 2.39.0 fails to start VM - Unable to determine VM's IP address #4313
Comments
@Manfred73 Hi, If I understood correctly you are trying to run crc on a ubuntu VM which is running on windows machine. Why can't you directly use crc on that windows machine ? In past we also issue which raised by users are using nested virt (check the label) and in your case also it is same. We don't perform nested virtualization so not even sure why it is happen, Also we recently did 2.40.0 release try that and see if that works (it fixes one of the issue crc-org/machine-driver-libvirt#122 if underlying hardware is AMD one) |
I want to use an Ubuntu/Linux image with crc and other tooling pre installed for training purposes, so I can easily share the image. Some users will have macOS, some Linux and some Windows. First I tried Virtual Box, but understood that doesn't work at all with nested virt and crc. I understood QEMU did supporr this. Are there workarounds for this, or assigning IP manually. Update: I tried version 2.40.0. Unfortunately still the same issue. |
Check the logs under
|
I do see one error related to libvirtd in the
I also followed the steps you mentioned before, but without the I did
It suggests I do
Then
Now, doing a
When I stop gitlab and try
Should I run these docker images on another port? Or can I configure crc to use others? I have stopped both docker images and did another:
This results in errors:
On the Ubuntu guest I have a config file defined in the |
I think following explain it, looks like libvirt is not working at all properly and VM is not running, you can check status of the VM using |
I create a complete new Ubuntu image and right after that installed prerequisites for crc (docker, libvirt):
Right after that installed crc:
libvirt service is running:
crc status shows:
sudo virsh list --all shows:
In the
and in
|
We can only debug more around this if it can reproduce in our testing/dev environment and which is not the case :( . There is lot of things depend for failure like base/guest HyperVisor and also underlying hardware. As I told before |
General information
crc setup
before starting it (Yes/No)? YesCRC version
CRC status
The debug log shows
DEBU systemd-networkd.service is not running
, so I enabled and started it, but thancrc start
complains it cannot work withsystemd-networkd.service
, so I stopped and disabled it again.I also see errors about
systemctl status virtqemud.socket' which cannot be found (not running nor listening). It was my understanding that this should be available when installing
libvirt-daemon-system`. I installed the following applications:Am I missing another library here?
I understand libvirtd is moving away from monolith to modules. I didn't get the modular approach to work though.
CRC config
Host Operating System
Steps to reproduce
Booting QEMU from Windows 11 host (with 64 GB RAM) using a batch file with the following options (using networking mode NAT). I noticed the crc network runs in bridge mode and thought that might be a problem. I tried to run QEMU in bridge, but didn't get that to work together with SPICE (the image won't boot if I use bridge mode).
Checked if NetworkManager is installed and running on Ubuntu guest. This was the case.
Installed QEMU and related applications on Ubuntu guest, enabled and started libvirtd:
crc setup
crc start
crc config set cpus 6
crc config set memory 12000
Added the following to /etc/hosts oh Ubuntu guest:
Expected
CRC to start succesfully and
Actual
crc start takes a long time, and log shows 60 tries to GetIP for crc.
Doing another start shows:
But a
crc status
shows:The CRC VM is running, but OpenShift is unreachable because it didn't get an IP assigned?
Logs
Before gather the logs try following if that fix your issue
Please consider posting the output of
crc start --log-level debug
on http://gist.github.com/ and post the link in the issue.virsh net-list --all
nmcli connection
virsh net-dumpxml crc | grep -i dhcp
systemctl status libvirtd.service
systemctl status NetworkManager
Older (related?) bugs/posts?
I have seen older other similar bugs around here:
The text was updated successfully, but these errors were encountered: