Crc: Unable to start due to missing backing file format

Created on 14 Oct 2020 · 9Comments · Source: code-ready/crc

General information

OS: Linux / (Ubuntu20.04)
Hypervisor:Hyper-V
Did you run crc setup before starting it (Yes/No)? Yes

CRC version 1.17.0

## CRC status
CRC VM:          Stopped
OpenShift:       Stopped
Disk Usage:      0B of 0B (Inside the CRC VM)
Cache Usage:     13.04GB
Cache Directory: /home/ss97/.crc/cache


## CRC config
```bash
# Put the output of `crc config view`

## 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

### Steps to reproduce ### Logs You can start crc with `crc start --log-level debug` to collect logs.

DEBU CodeReady Containers version: 1.17.0+99f5c87 
DEBU OpenShift version: 4.5.14 (embedded in binary) 
DEBU Total memory of system is 12508778496 bytes  
DEBU Unable to find out if a new version is available: Get https://mirror.openshift.com/pub/openshift-v4/clients/crc/latest/release-info.json: dial tcp: lookup mirror.openshift.com: no such host 
INFO Checking if oc binary is cached              
DEBU Running '/home/ss97/.crc/bin/oc/oc version --client' 
DEBU Found oc version 4.5.14                      
DEBU oc binary already cached                     
INFO Checking if podman remote binary is cached   
DEBU Currently podman remote is not supported     
INFO Checking if goodhosts binary is cached       
DEBU goodhost binary already cached               
INFO Checking minimum RAM requirements            
DEBU Total memory of system is 12508778496 bytes  
INFO Checking if running as non-root              
INFO Checking if Virtualization is enabled        
DEBU Checking if the vmx/svm flags are present in /proc/cpuinfo 
DEBU CPU virtualization flags are good            
INFO Checking if KVM is enabled                   
DEBU Checking if /dev/kvm exists                  
DEBU /dev/kvm was found                           
INFO Checking if libvirt is installed             
DEBU Checking if 'virsh' is available             
DEBU 'virsh' was found in /usr/bin/virsh          
INFO Checking if user is part of libvirt group    
DEBU Checking if current user is part of the libvirt group 
DEBU Running '/usr/bin/groups ss97'               
DEBU Current user is already in the libvirt group 
INFO Checking if libvirt daemon is running        
DEBU Checking if libvirtd service is running      
DEBU Running 'systemctl status virtqemud.socket'  
DEBU Command failed: exit status 4                
DEBU stdout:                                      
DEBU stderr: Unit virtqemud.socket could not be found. 
DEBU virtqemud.socket is not running              
DEBU Running 'systemctl status libvirtd.socket'   
DEBU libvirtd.socket is running                   
INFO Checking if a supported libvirt version is installed 
DEBU Checking if libvirt version is >=3.4.0       
DEBU Running 'virsh -v'                           
INFO Checking if crc-driver-libvirt is installed  
DEBU Checking if crc-driver-libvirt is installed  
DEBU Running '/home/ss97/.crc/bin/crc-driver-libvirt version' 
DEBU Found crc-driver-libvirt version 0.12.10     
DEBU crc-driver-libvirt is already installed      
INFO Checking if libvirt 'crc' network is available 
DEBU Checking if libvirt 'crc' network exists     
DEBU Running 'virsh --connect qemu:///system net-info crc' 
DEBU Checking if libvirt 'crc' definition is up to date 
DEBU Running 'virsh --connect qemu:///system net-dumpxml --inactive crc' 
DEBU libvirt 'crc' network has the expected value 
INFO Checking if libvirt 'crc' network is active  
DEBU Checking if libvirt 'crc' network is active  
DEBU Running 'virsh --connect qemu:///system net-info crc' 
DEBU libvirt 'crc' network is already active      
INFO Checking if NetworkManager is installed      
DEBU Checking if 'nmcli' is available             
DEBU 'nmcli' was found in /usr/bin/nmcli          
INFO Checking if NetworkManager service is running 
DEBU Checking if NetworkManager.service is running 
DEBU Running 'systemctl status NetworkManager'    
DEBU NetworkManager.service is already running    
INFO Checking if /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf exists 
DEBU Checking NetworkManager configuration        
DEBU NetworkManager configuration is good         
INFO Checking if /etc/NetworkManager/dnsmasq.d/crc.conf exists 
DEBU Checking dnsmasq configuration               
DEBU dnsmasq configuration is good                
INFO Starting CodeReady Containers VM for OpenShift 4.5.14... 
DEBU Updating CRC VM configuration                
ERRO Error starting stopped VM: virError(Code=55, Domain=18, Message='Requested operation is not valid: format of backing image '/home/ss97/.crc/cache/crc_libvirt_4.5.14/crc.qcow2' of image '/home/ss97/.crc/machines/crc/crc.qcow2' was not specified in the image metadata (See https://libvirt.org/kbase/backing_chains.html for troubleshooting)') 
Error starting stopped VM: virError(Code=55, Domain=18, Message='Requested operation is not valid: format of backing image '/home/ss97/.crc/cache/crc_libvirt_4.5.14/crc.qcow2' of image '/home/ss97/.crc/machines/crc/crc.qcow2' was not specified in the image metadata (See https://libvirt.org/kbase/backing_chains.html for troubleshooting)')

Source

vyom-soft

Most helpful comment

I am running ubuntu 20.4
After following all the manual setup steps at this Link I faced the same issue.
This is what worked from me based on this documentation.

Edit the VM image using
$ virsh edit crc

Locate the disk section and add following:

<backingStore type='file'> <format type='qcow2'/> <source file='/home/USER_NAME_HERE/.crc/cache/crc_libvirt_4.5.14/crc.qcow2'/> <backingStore/> </backingStore>

Save and run. Works for me.

kchamit on 15 Oct 2020

❤4

All 9 comments

Can you attach the crc.log file please (located in ~/.crc) ? I would like to know which operation is not valid.

guillaumerose on 14 Oct 2020

Note: I am not the original poster, but I am running into the same issue (same OS, same version), the end of my crc.log is pasted below

time="2020-10-15T14:24:07+02:00" level=info msg="Starting CodeReady Containers VM for OpenShift 4.5.14..." time="2020-10-15T14:24:07+02:00" level=debug msg="Updating CRC VM configuration" (crc) Calling .UpdateConfigRaw (crc) Calling .UpdateConfigRaw (crc) Calling .GetConfigRaw (crc) Calling .Start (crc) DBG | Starting VM crc (crc) Failed to start: virError(Code=55, Domain=18, Message='Requested operation is not valid: format of backing image '/home/obondu/.crc/cache/crc_libvirt_4.5.14/crc.qcow2' of image '/home/obondu/.crc/machines/crc/crc.qcow2' was not specified in the image metadata (See https://libvirt.org/kbase/backing_chains.html for troubleshooting)') time="2020-10-15T14:24:08+02:00" level=error msg="Error starting stopped VM: virError(Code=55, Domain=18, Message='Requested operation is not valid: format of backing image '/home/obondu/.crc/cache/crc_libvirt_4.5.14/crc.qcow2' of image '/home/obondu/.crc/machines/crc/crc.qcow2' was not specified in the image metadata (See https://libvirt.org/kbase/backing_chains.html for troubleshooting)')" Making call to close driver server (crc) Calling .Close Successfully made call to close driver server Making call to close connection to plugin binary

OlivierBondu on 15 Oct 2020

I am running ubuntu 20.4
After following all the manual setup steps at this Link I faced the same issue.
This is what worked from me based on this documentation.

Edit the VM image using
$ virsh edit crc

Locate the disk section and add following:

<backingStore type='file'> <format type='qcow2'/> <source file='/home/USER_NAME_HERE/.crc/cache/crc_libvirt_4.5.14/crc.qcow2'/> <backingStore/> </backingStore>

Save and run. Works for me.

kchamit on 15 Oct 2020

❤4

Can you paste the output of qemu-img info image.qcow2 for both images ? We might find something with this command.

Also, did you hit this bug ? https://github.com/code-ready/crc/issues/1578

guillaumerose on 15 Oct 2020

Thanks a lot @kchamit ! I run into another issue but at least this one step seems solved.

@guillaumerose : outputs can be found below, and on my end no, I did not hit bug 1578

➜  ~ qemu-img info /home/obondu/.crc/cache/crc_libvirt_4.5.14/crc.qcow2
image: /home/obondu/.crc/cache/crc_libvirt_4.5.14/crc.qcow2
file format: qcow2
virtual size: 31 GiB (33285996544 bytes)
disk size: 9.97 GiB
cluster_size: 65536
Format specific information:
    compat: 1.1
    lazy refcounts: true
    refcount bits: 16
    corrupt: false
➜  ~ qemu-img info /home/obondu/.crc/machines/crc/crc.qcow2
image: /home/obondu/.crc/machines/crc/crc.qcow2
file format: qcow2
virtual size: 31 GiB (33285996544 bytes)
disk size: 53.1 MiB
cluster_size: 65536
backing file: /home/obondu/.crc/cache/crc_libvirt_4.5.14/crc.qcow2
Format specific information:
    compat: 1.1
    lazy refcounts: false
    refcount bits: 16
    corrupt: false

OlivierBondu on 15 Oct 2020

backing file format is missing. According to the doc https://libvirt.org/kbase/backing_chains.html#vm-refuses-to-start-due-to-misconfigured-backing-store-format, you need to perform:

qemu-img rebase -f qcow2 -F qcow2 -b /home/obondu/.crc/cache/crc_libvirt_4.5.14/crc.qcow2 /home/obondu/.crc/machines/crc/crc.qcow2

guillaumerose on 15 Oct 2020

seems to work as well, except I am now running into the above mentioned issue #1578 ...

OlivierBondu on 15 Oct 2020

Good to know. If you change the machine image to use the cache image, you will not be able to do crc delete/start and have a fresh install. You will have to delete the cache also.

guillaumerose on 15 Oct 2020

Closing this issue as the fix for it has been merged in machine-driver-libvirt

cfergeau on 26 Oct 2020

Was this page helpful?

0 / 5 - 0 ratings

Related issues

Error approving the node csr Temporary Error: exit status 1

arprakas · 9Comments

Error starting crc version 1.10.0+9025021. OpenShift version: 4.4.3 (embedded in binary)

jriverol · 5Comments

"FATA Libvirt crc network is not active" triggered falsely by non-C locale

fabiand · 10Comments

[BUG]failed to connect socket to '/var/run/libvirt/virtlogd-sock': Connection refused') Making call to close driver server

Eyaldavid7 · 8Comments

[BUG] kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

drpaneas · 7Comments