Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 711948 - app-emulation/qemu-4.2.0-r1 issue for VMs booting from a qcow2 image file
Summary: app-emulation/qemu-4.2.0-r1 issue for VMs booting from a qcow2 image file
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-09 12:13 UTC by Jacques Landru
Modified: 2020-03-09 21:03 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jacques Landru 2020-03-09 12:13:31 UTC
Since last gentoo world update, app-emulation/qemu updated from 4.1.0-r1 to 4.2.0-r1, my VMs booting from a qcow2 file disk hang with "no bootable disk" message. Other VMs booting from raw iso or raw image file start as usual. Unfortunately,  at the moment, I have no time to investigate deeper and I really need some of my qcow2 image VMs. As qemu-4.1.0-rc1 ebuild is not more available in portage tree,  I recreated that ebuild on a local repo and restarted my VMs from that previous version.
Comment 1 Ionen Wolkens gentoo-dev 2020-03-09 13:01:42 UTC
I don't know what's the issue (current qcow2 working fine for me, but I made/used them only with 4.2.0), but if in a hurry you can convert your images to raw and see if they work.

Alternatively, converting from qcow2 to qcow2 may possibly update them to work.

"qemu-img convert -O qcow2 old.qcow2 new.qcow2"
or
"qemu-img convert -O raw old.qcow2 new.img"
Comment 2 Jonas Stein gentoo-dev 2020-03-09 15:46:24 UTC
It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis.
We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. 

I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3].
I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4].
Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product.

[1] https://www.gentoo.org/get-involved/irc-channels/
[2] https://forums.gentoo.org/
[3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html
[4] https://www.gentoo.org/support/
Comment 3 Jacques Landru 2020-03-09 20:56:33 UTC
(In reply to Ionen Wolkens from comment #1)
> I don't know what's the issue (current qcow2 working fine for me, but I
> made/used them only with 4.2.0), but if in a hurry you can convert your
> images to raw and see if they work.
> 
> Alternatively, converting from qcow2 to qcow2 may possibly update them to
> work.
> 
> "qemu-img convert -O qcow2 old.qcow2 new.qcow2"
> or
> "qemu-img convert -O raw old.qcow2 new.img"

OK, I gave it a try to convert my qcow2 image under qemu-4.2.0-r1

# qemu-img convert -O qcow2 cirrus-v2-k3s-agent-disk-image-cow00-qemu410.qcow2 cirrus-v2-k3s-agent-disk-image-cow00-qemu420.qcow2

It works, the VM now starts without error, but the image size qcow2 increases tenfold from 54 MiB to 545MiB

# qemu-img info cirrus-v2-k3s-agent-disk-image-cow00-qemu410.qcow2
image: cirrus-v2-k3s-agent-disk-image-cow00-qemu410.qcow2
file format: qcow2
virtual size: 10 GiB (10737418240 bytes)
disk size: 53.9 MiB
cluster_size: 65536
backing file: cirrus-v2-k3s-agent-master-disk-image.qcow2
Format specific information:
    compat: 1.1
    lazy refcounts: false
    refcount bits: 16
    corrupt: false
qemu-img info cirrus-v2-k3s-agent-disk-image-cow00-qemu420.qcow2
image: cirrus-v2-k3s-agent-disk-image-cow00-qemu420.qcow2
file format: qcow2
virtual size: 10 GiB (10737418240 bytes)
disk size: 545 MiB
cluster_size: 65536
Format specific information:
    compat: 1.1
    lazy refcounts: false
    refcount bits: 16
    corrupt: false

I use qemu/kvm for several years, for me it's the first time I need to convert my qcow2 images. I just looked at 4.2.0 changelog (https://wiki.qemu.org/ChangeLog/4.2), some nbd changes but no mention for an eventual conversion need.
Comment 4 Jacques Landru 2020-03-09 21:03:45 UTC
(In reply to Jonas Stein from comment #2)
> It is sad to read that you have problems with the software. The situation
> seems to be a bit more complicate and requires some analysis.
> We can not help you efficiently via bug tracker. The bug tracker aims rather
> on specific problems in .ebuilds and less on individual systems. 
> 
> I have had very good experience on the gentoo IRC [1] with questions like
> this. Of course there are also forums and mailing lists [2,3].
> I hope you understand, that I will close the bug here therefore and wish you
> good luck on one of the mentioned channels [4].
> Please reopen the ticket in order to provide an indication for an specific
> error in an ebuild or any gentoo related product.
> 
> [1] https://www.gentoo.org/get-involved/irc-channels/
> [2] https://forums.gentoo.org/
> [3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html
> [4] https://www.gentoo.org/support/

OK, I understand, sorry for clumsily posting in the wrong place. But if a qcow2 file conversion is needed after the '.2.0 update, maybe a warning message might be useful.