Ask Your Question

Instance failed to start "qemu-img: Could not open...No such file or directory"

asked 2013-05-17 08:38:43 -0500

Shrirang gravatar image

updated 2013-05-17 08:39:29 -0500


Does anyone have faced above error? Whenever I try to start an instance it says:

""qemu-img: Could not open '/var/lib/nova/instances/_base/1ec1b1939bae30e12e799232f51bf77182b97be7': No such file or directory\n""

Please find detailed logs attached.

Please help.

Regards, Shrirang

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2013-05-21 14:55:35 -0500

david-wittman gravatar image

I'm pretty sure this bug is related to your issue:

To fix, you can either apply (this patch) or boot an instance with a 0GB root disk flavor to this host. This will cache the base image and prevent this bug from appearing. Make sure you use the same image that you wish to boot your other flavors from.

If you choose to do the latter, you can select the host to which your instance will boot by including --availability-zone in your nova boot command. For example:

nova boot --flavor 1 --image 95e50545-3452-4ee9-be32-cfd65ee0ac6f --availability-zone nova:$COMPUTE_HOST instance-name

Where $COMPUTE_HOST is the hostname of the compute host as defined in the nova.compute_nodes table.

edit flag offensive delete link more

answered 2013-05-17 19:25:36 -0500

annegentle gravatar image

Couple of thoughts: (some more info on your OpenStack version and operating system might help)

Could something be clearing out the disk for this image? There is a setting in nova.conf, removeunusedbase_images=True, that enables libvirt base file cleanup by default.

Could you have a permissions problem on that particular file (due to rootwrap behavior or some such)?

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2013-05-17 08:38:43 -0500

Seen: 3,702 times

Last updated: May 21 '13