Ditto for Qcow2. We use it on ZFS.
I do a snapshot-create-as to get the QCOW2 consistent image, then zfs
snapshot, then replicate to another host for backups. All the VMS have
consistent backups in this way.
On 11/7/2017 5:16 AM, Vasiliy Tolstov wrote:
> Please don't use lvm thin for vm. In our
2017-11-07 13:46 GMT+03:00 Jan Hutař :
> Do you have some comparasion of IO performance on thin pool vs. qcow2
> file on fs?
>
I don't have actual data (i'm switched from lvm thinp is about 1-1.5
year ago. But when we test it - sometimes qcow2 gave us better
performance when raw on fs and thin vol
Do you have some comparasion of IO performance on thin pool vs. qcow2
file on fs?
In my case each VM would have its own thin volume. I just want to
overcommit disk-space.
Regards,
Jan
On 2017-11-07 13:16 +0300, Vasiliy Tolstov wrote:
Please don't use lvm thin for vm. In our hosting in Russia
Please don't use lvm thin for vm. In our hosting in Russia we have
100-150 vps on each node with lvm thin pool on ssd and have locks,
slowdowns and other bad things because of COW. After we switching to
qcow2 files on plain ssd ext4 fs and happy =).
2017-11-04 23:21 GMT+03:00 Jan Hutař :
> Hello,
Hello,
as usual, I'm few years behind trends so I have learned about LVM thin
volumes recently and I especially like that your volumes can be "sparse"
- that you can have 1TB thin volume on 250GB VG/thin pool.
Is it somehow possible to use that with libvirt?
I have found this post from 2014:
