![]() ![]() The conversion process actually makes a qcow2 copy of the raw image and leaves the raw image intact. Let's take a look at the image file format:ģ. In this example, we convert an image file of size 10 GB for a VM called vm2.Ģ. It is easy to convert from a raw VM image (which doesn?t support libvirt snapshots) to qcow2 format. vm-images/vm1.img: Qemu Image, Format: Qcow, Version: 2Ĭonverting disk format from raw to qcow2: * If you create a VM with a raw disk of 10 GB, you?ll see that the disk image size for the VM will be exactly 10 GB, whereas for a VM with a qcow2 disk the actual file size will be a fraction of 10 GB (say 2-3 GB) and it will grow as you occupy disk space inside the VM. * Raw disks have better I/O performance than qcow2 because the VM disk space is pre-allocated before the VM is created, as opposed to qcow2, where VM disk space is thinly provisioned and allocated on-the-go as the VM requires it. * Raw disks are presented as-is to the VM without any disk layering and do not support snapshots, whereas qcow2 disks support a range of special features including snapshots, compression and encryption. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |