On Thu, Feb 19, 2015 at 15:59:17 +0100, Ján Tomko wrote: > 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 > --- > src/storage/storage_backend.c | 6 ++++++ > src/storage/storage_backend_fs.c | 7 +++++++ > src/storage/storage_backend_rbd.c | 6 ++++++ > src/storage/storage_backend_sheepdog.c | 6 ++++++ > src/storage/storage_driver.c | 14 ++++++++++++- > tests/storagevolxml2argvdata/qcow2-nocapacity.argv | 5 +++++ > tests/storagevolxml2argvtest.c | 20 +++++++++++-------- > .../vol-qcow2-nocapacity-backing.xml | 23 ++++++++++++++++++++++ > 8 files changed, 78 insertions(+), 9 deletions(-) > create mode 100644 tests/storagevolxml2argvdata/qcow2-nocapacity.argv > create mode 100644 tests/storagevolxml2xmlin/vol-qcow2-nocapacity-backing.xml > This is the correct place for the hunk I was complaining about. ACK after the release. Peter
Attachment:
signature.asc
Description: Digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list