gns3-registry icon indicating copy to clipboard operation
gns3-registry copied to clipboard

error while starting TinyCoreLinux11.1-1: Could not create 'hda' disk image: qemu-img returned with 1

Open mb720 opened this issue 4 years ago • 11 comments

Hi and thanks for GNS3!

I downloaded and installed the Tiny Core appliances with and without Firefox.

The appliance with Firefox works fine, but when I try to start the other one, I get this error:

error while starting TinyCoreLinux11.1-1: Could not create 'hda' disk image: qemu-img returned with 1
qemu-img: /home/mb/.local/share/GNS3/projects/Test_2/project-files/qemu/308610bf-e689-4697-b223-36d2b24a7a3b/hda_disk.qcow2: Could not open backing file: Could not open '/home/gns3/GNS3/images/QEMU/empty30G.qcow2': No such file or directory
Could not open backing image.

Could not create 'hda' disk image: qemu-img returned with 1
qemu-img: /home/mb/.local/share/GNS3/projects/Test_2/project-files/qemu/308610bf-e689-4697-b223-36d2b24a7a3b/hda_disk.qcow2: Could not open backing file: Could not open '/home/gns3/GNS3/images/QEMU/empty30G.qcow2': No such file or directory
Could not open backing image.

The path for the backing file doesn't look right to me, since there is no directory at /home/gns3/ on my machine.

I'm running GNS3 2.2.15 on Arch Linux.

Is there a way to fix this issue?

mb720 avatar Oct 13 '20 17:10 mb720

See issue https://github.com/GNS3/gns3-server/issues/1817

The tinycore-linux appliance is in bad shape, I suggest to look for alternatives.

b-ehlers avatar Oct 16 '20 10:10 b-ehlers

I have the exact same error but with a different image

error while starting CiscoIOSvL215.2(4.0.55)E-1: Could not create 'hda' disk image: qemu-img returned with 1 qemu-img: /home/zodiac/GNS3/projects/Test/project-files/qemu/b4567084-b1f6-431c-9427-e1c0dbd8912e/hda_disk.qcow2: Backing file specified without backing format Detected format of vmdk. Could not create 'hda' disk image: qemu-img returned with 1 qemu-img: /home/zodiac/GNS3/projects/Test/project-files/qemu/b4567084-b1f6-431c-9427-e1c0dbd8912e/hda_disk.qcow2: Backing file specified without backing format Detected format of vmdk.

I'm running GNS3 2.2.24 on Arch Linux.

Is there a way to fix this issue?

KrishanHaridaran avatar Sep 04 '21 01:09 KrishanHaridaran

What version of Qemu do you have?

grossmj avatar Sep 05 '21 05:09 grossmj

I assume, @ZodiaCKiLl3r uses Qemu v6.1. The warning "backing file without format" of previous versions is now an error, see https://github.com/qemu/qemu/blob/master/docs/about/removed-features.rst#qemu-img-backing-file-without-format-removed-in-61.

That affects also https://github.com/GNS3/gns3-gui/issues/3131.

A solution would be to query the image format with qemu-img info --output=json, attribute format:

$ qemu-img info --output=json GNS3/images/QEMU/vEOS-lab-4.14.5F.vmdk
{
    "virtual-size": 2147483648,
    "filename": "GNS3/images/QEMU/vEOS-lab-4.14.5F.vmdk",
    "cluster-size": 65536,
    "format": "vmdk",
    "actual-size": 422383616,
    .
    .
}

b-ehlers avatar Sep 05 '21 07:09 b-ehlers

A solution would be to query the image format with qemu-img info --output=json, attribute format.

I was thinking using qemu-img or detecting the file format by looking for the magic value in the header. qemu-img is a much simpler solution... ;)

grossmj avatar Sep 05 '21 07:09 grossmj

After querying the image format with @b-ehlers given command this is the out put,

qemu-img info --output=json image.qcow2
{ "virtual-size": 2147483648, "filename": "image.qcow2", "cluster-size": 65536, "format": "qcow2", "actual-size": 41160704, "format-specific": { "type": "qcow2", "data": { "compat": "1.1", "compression-type": "zlib", "lazy-refcounts": false, "refcount-bits": 16, "corrupt": false, "extended-l2": false } }, "dirty-flag": false }

what should i do now ? i need help please guide me through, :)

btw, i am using qemu-img version 6.1.0

KrishanHaridaran avatar Sep 06 '21 02:09 KrishanHaridaran

@ZodiaCKiLl3r This is a problem with Qemu >= 6.1.0

This should have been fixed on our 2.2 branch: https://github.com/GNS3/gns3-server/tree/2.2

So you have 3 options:

  • Downgrade Qemu
  • Manually install the development version from https://github.com/GNS3/gns3-server/tree/2.2
  • Wait for us to release GNS3 v2.2.25

grossmj avatar Sep 06 '21 02:09 grossmj

Actually the fixes for Qemu >= 6.1.0 `will fix only the issue @ZodiaCKiLl3r reported. The initial issue from @mb720 (and @vasiliyaltunin reported in https://github.com/GNS3/gns3-server/issues/1817) is not fixed. Therefore Tiny Core Linux v11.1 is still broken.

b-ehlers avatar Sep 06 '21 06:09 b-ehlers

@b-ehlers correct, my answer is just for @ZodiaCKiLl3r, the OP issue isn't resolved.

grossmj avatar Sep 06 '21 06:09 grossmj

Hi all folks

I have same issues

So this is my GNS3 log

myubuntu@myubuntu:~$ cat /home/keng/.config/GNS3/2.2/gns3_gui.log 

2021-10-13 20:19:05 INFO logger.py:126 Log level: INFO
2021-10-13 20:19:05 INFO main.py:259 GNS3 GUI version 2.2.26
2021-10-13 20:19:05 INFO main.py:260 Copyright (c) 2007-2021 GNS3 Technologies Inc.
2021-10-13 20:19:05 INFO main.py:261 Application started with /usr/bin/gns3
2021-10-13 20:19:27 ERROR node.py:257 error while starting TinyCoreLinux11.1-1: Could not create 'hda' disk image: qemu-img returned with 1
qemu-img: /home/myubuntu/GNS3/projects/05-Linux-StatelessStateFull-Firewall/project-files/qemu/d8079306-6d8b-496e-b655-56287376e68d/hda_disk.qcow2: Could not open backing file: Could not open '/home/gns3/GNS3/images/QEMU/empty30G.qcow2': No such file or directory
Could not open backing image.

2021-10-13 20:19:27 CRITICAL __init__.py:1626 Could not create 'hda' disk image: qemu-img returned with 1
qemu-img: /home/myubuntu/GNS3/projects/05-Linux-StatelessStateFull-Firewall/project-files/qemu/d8079306-6d8b-496e-b655-56287376e68d/hda_disk.qcow2: Could not open backing file: Could not open '/home/gns3/GNS3/images/QEMU/empty30G.qcow2': No such file or directory
Could not open backing image.

Other information OS : Ubuntu 21.04 VMWarePlayer : 16.1.2 build-17966106 GNS3 server VMWARE : 2.2.26 GNS3 GUI : 2.2.26

Alpine Linux = Can Simulate Mikrotik CHR image = Can Simulate

secfun avatar Oct 13 '21 13:10 secfun

1- Change Path Of Backing File: /home/gns3/GNS3/images/QEMU/empty30G.qcow2

sudo qemu-img rebase -f qcow2 -u -b /opt/gns3/images/QEMU/empty30G.qcow2 linux-tinycore-11.1.qcow2

More information: https://blog.programster.org/qemu-img-cheatsheet

2- Increase template memory to 256 MB

3- To solve mouse problem in TightVNC Viewer: In connection options under Local Cursor Shape select Do not show

Benaattia avatar Apr 06 '22 00:04 Benaattia