Re: changing compat when create volume from volume via libvirt api

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2017-05-12 16:20 GMT+03:00 Vasiliy Tolstov <v.tolstov@xxxxxxxxx>:
> I'm use via php binding
> https://libvirt.org/html/libvirt-libvirt-storage.html#virStorageVolCreateXMLFrom
>
> and see that image grows:
>
> image: new.qcow2
> file format: qcow2
> virtual size: 4.9G (5242880000 bytes)
> disk size: 854M
> cluster_size: 65536
> Format specific information:
>     compat: 0.10
>     refcount bits: 16
>
> image: old.qcow2
> file format: qcow2
> virtual size: 4.9G (5242880000 bytes)
> disk size: 277M
> cluster_size: 65536
> Format specific information:
>     compat: 1.1
>     lazy refcounts: false
>     refcount bits: 16
>     corrupt: false
>
> Why libvirt create new image with different compat?


Also, specify compat in xml desc of new disk helps with comat version,
but image size grows:
image: new2.qcow2
file format: qcow2
virtual size: 4.9G (5242880000 bytes)
disk size: 854M
cluster_size: 65536
Format specific information:
    compat: 1.1
    lazy refcounts: false
    refcount bits: 16
    corrupt: false


-- 
Vasiliy Tolstov,
e-mail: v.tolstov@xxxxxxxxx

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list



[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]
  Powered by Linux