Ján Tomko 155ca616eb Allow creating volumes with a backing store but no capacity ... The tool creating the image can get the capacity from the backing storage. Just refresh the volume afterwards. https://bugzilla.redhat.com/show_bug.cgi?id=958510		2015-03-02 08:07:11 +01:00
..
vol-file-backing.xml	storage: allow interleave in volume XML	2013-11-25 07:51:14 -07:00
vol-file-naming.xml
vol-file.xml	Added timestamps to storage volumes	2012-08-02 17:14:17 -06:00
vol-gluster-dir-neg-uid.xml	storage: unify permission formatting	2014-12-16 15:47:56 +01:00
vol-gluster-dir.xml	storage: improve directory support in gluster pool	2013-11-25 12:46:19 -07:00
vol-logical-backing.xml	storage: expose volume meta-type in XML	2013-11-25 10:55:19 -07:00
vol-logical.xml	storage: expose volume meta-type in XML	2013-11-25 10:55:19 -07:00
vol-partition.xml	storage: expose volume meta-type in XML	2013-11-25 10:55:19 -07:00
vol-qcow2-0.10-lazy.xml
vol-qcow2-1.1.xml
vol-qcow2-lazy.xml
vol-qcow2-nobacking.xml
vol-qcow2-nocapacity-backing.xml	Allow creating volumes with a backing store but no capacity	2015-03-02 08:07:11 +01:00
vol-qcow2-nocapacity.xml	Allow cloning volumes with no capacity specified	2015-03-02 08:07:11 +01:00
vol-qcow2-nocow.xml	add nocow test case	2014-07-16 13:35:26 +02:00
vol-qcow2.xml	Move volume XMLs out of storagevolxml2argvdata	2013-07-25 13:26:41 +02:00
vol-sheepdog.xml	storage: expose volume meta-type in XML	2013-11-25 10:55:19 -07:00