Why do we suggest using raw disks instead of qcow2 images?
Moderators: Cat_7, Ronald P. Regensburg
-
- Tinkerer
- Posts: 82
- Joined: Fri Jul 05, 2019 10:10 pm
Why do we suggest using raw disks instead of qcow2 images?
qcow2 images are dymanically-expanding, instead of pre-allocating all the space at once, which allows to save space.
If you need more info, tell me
-
- Tinkerer
- Posts: 82
- Joined: Fri Jul 05, 2019 10:10 pm
Re: Why do we suggest using raw disks instead of qcow2 images?
I see why now...
If you need more info, tell me
- adespoton
- Forum All-Star
- Posts: 4274
- Joined: Fri Nov 27, 2009 5:11 am
- Location: Emaculation.com
- Contact:
Re: Why do we suggest using raw disks instead of qcow2 images?
QCOW2 is a great format in that you can keep it sparse, and with the -c flag you can even compress the blocks.
Another benefit is that you can snapshot an image that uses the QCOW2 format.
Unfortunately, because it's copy-on-write, it also can become corrupted, especially when combined with a virtual NVMe controller and disk caching. QEMU is really stable with raw image formats, but you do risk losing the image if you're using QCOW2 and something goes wrong.
Another benefit is that you can snapshot an image that uses the QCOW2 format.
Unfortunately, because it's copy-on-write, it also can become corrupted, especially when combined with a virtual NVMe controller and disk caching. QEMU is really stable with raw image formats, but you do risk losing the image if you're using QCOW2 and something goes wrong.