How to mount qcow2 image

I’ve read that with qemu-nbd and the network block device kernel module, I can mount a qcow2 image. I haven’t seen any tutorials on mounting a qcow2 via a loop device. Is it possible? If not, why?

I don’t really understand the difference between a qcow2 and an iso.

Answers:

Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

Thanks to Gilles for pointing out guestmount. Mounting a qcow2 image is very simple on RHEL/Centos/Fedora:

1. First install guestmount (comes as part of libguestfs-tools in Centos6)

   yum install libguestfs-tools libguestfs

2. Then you should be able to auto-magically mount your qcow2 image using the -i option

   guestmount -a path_to_image.qcow2 -i --ro /mount_point

   You can manually specify mount points (within the image) using the -m option.
   As always read the man page on guestmount for more details…

Note: This only addresses the question title. Please see Peter’s answer for the differences between qcow2 and ISOs…

Method 2

Step 1 – Enable NBD on the host

modprobe nbd max_part=8

Step 2 – Connect the QCOW2 as a network block device

qemu-nbd --connect=/dev/nbd0 /var/lib/vz/images/100/vm-100-disk-1.qcow2

Step 3 – List partitions inside the QCOW2

fdisk /dev/nbd0 -l

Step 4 – Mount the partition from the VM

mount /dev/nbd0p1 /mnt/somepoint/

You can also mount the filesystem with normal user permissions, ie. non-root:

mount /dev/nbd0p1 /mnt/somepoint -o uid=$UID,gid=$(id -g)

Step 5 – After you’re done, unmount and disconnect

umount /mnt/somepoint/
qemu-nbd --disconnect /dev/nbd0
rmmod nbd

Shamefully stolen from: https://gist.github.com/shamil/62935d9b456a6f9877b5

Method 3

A loop device just turns a file into a block device. If the file has some special internal mapping of its blocks, the loop device won’t translate any of it. qcow2 is special… it has special mapping inside that handles different snapshots of the same blocks stored in different places. If you mount that as a loop device, you’ll just get one big block device that doesn’t represent the actual data in the image.

Another option is to convert to raw and mount as a loop device:

qemu-img convert -p -O raw oldfile.qcow2 newfile.raw

But then you have to convert it back to qcow2 to use it again as before.

I think using qemu-nbd is not the most efficient IO, but is easy. Mounting it in a VM, like one booted with a live usb, is easy too. Converting doesn’t make much sense… it was just an example of how they’re different.

Method 4

There’s also a way to do this with FUSE with nbdfuse. It has the advantage that you do not need root access, but it won’t be as efficient as the NBD module approach given in other answers:

$ touch /tmp/file.raw
$ nbdfuse /tmp/file.raw [ qemu-nbd -f qcow2 file.qcow2 ] &
$ ls -l /tmp/file.raw
 -rw-rw-rw-. 1 nbd nbd 1073741824 Jan  1 10:10 /tmp/file.raw

Method 5

I could not make guestfs work on my vbox machine and qemu-img convert was not an option or maybe I just did not know the way to convert into a format where the disk was not of full size defined for qcow2 – it wanted to create 40GB of VDI apparently although there was only few GB of disk used. So I looked for something different and found qemu-nbd to be a great alternative especially if you have many partitions on the disk. It is a bit more commands but it is still faster than the path I would have to go to make guestmount to work on my vbox VM.
manual for qemu-nbd is realtievely simple but you can see here for further advice:

https://gist.github.com/shamil/62935d9b456a6f9877b5

It worked like a charm. So in case you cannot get over the mount error 1, you can try this.

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0