minishift: Preflight check for libvirt check FAILs when only OpenVSwitch bridge has been defined
Hi,
I am getting an unexpected “libvirt FAIL” error message On ubuntu 14.04 as follows, though all requirments seems to have been fulfilled (as evident from virt-manager working)
ERROR
$ ./minishift version
minishift v1.7.0+1549135
$ ./minishift start
-- Checking if KVM driver is installed ...
Driver is available at /usr/local/bin/docker-machine-driver-kvm ...
Checking driver binary is executable ... OK
-- Checking if Libvirt is installed ... OK
-- Checking if Libvirt default network is present and active ... FAIL
See the 'Setting Up the Driver Plug-in' topic for more information
ALL REQUIREED COMPONENTS FULFILLED
In pursuant to https://docs.openshift.org/latest/minishift/getting-started/setting-up-driver-plugin.html
- THE DOCKER-MACHINE-DRIVER-KVM PULLED IN THE RIGHT PLACE
$ ls -la /usr/local/bin/docker-machine*
-rwxr-xr-x 1 root root 26574656 Oct 29 16:47 /usr/local/bin/docker-machine
-rwxr-xr-x 1 root root 12096944 Oct 27 13:00 /usr/local/bin/docker-machine-driver-kvm
- THE OPENVSWITCH BRIDGE CONFIGURED
$ virsh net-list --all
Name State Autostart Persistent
----------------------------------------------------------
ovsbr0 active yes yes
- REQUIRED PACKAGES INSTALLED
$ dpkg -l | grep libvirt-bin
ii libvirt-bin 1.2.2-0ubuntu13.1.23 amd64 programs for the libvirt library
$ dpkg -l | grep qemu-kvm
ii qemu-kvm 2.0.0+dfsg-2ubuntu1.36 amd64 QEMU Full virtualization
- USER ALREADY IN THE LIBVIRTD GROUP
$ cat /etc/group | grep libvirtd
libvirtd:x:120:zenny,vnc
Just wondering why minishift reports ‘Checking if Libvirt default network is present and active … FAIL’?
Cheers, zenny
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 16 (8 by maintainers)
AFAIK You can use the default
registry-routeaddon for this, here’s the docs link to addons: https://docs.openshift.org/latest/minishift/using/addons.html#default-addonsI saw the same error :
-- Checking if Libvirt default network is present and active ... FAILThen after reboot, the error gone. I did nothing, only reboot.This was the clean installation on my fedora and I followed these steps (from copied from oficial docs) https://gist.github.com/helio-frota/339991b88c6e4983c6e6d09af2d477c8