search for: libvirtsource

...tion for a guest's volume. Specifically, it will not return volume information if the volume is not in a storage pool. Rather than displaying a generic libvirt error in this case, advise the user how they can create an appropriate storage pool. Fixes RHBZ#672498 --- lib/Sys/VirtV2V/Connection/LibVirtSource.pm | 27 +++++++++++++++++++++++---- 1 files changed, 23 insertions(+), 4 deletions(-) diff --git a/lib/Sys/VirtV2V/Connection/LibVirtSource.pm b/lib/Sys/VirtV2V/Connection/LibVirtSource.pm index 628074c..9db9f60 100644 --- a/lib/Sys/VirtV2V/Connection/LibVirtSource.pm +++ b/lib/Sys/VirtV2V/Conn...

...will also be extended to provide a file interface. ReadStream/WriteStream Provides read/write streaming access to a volume's data. --- MANIFEST | 12 +- lib/Sys/VirtV2V/Connection/LibVirt.pm | 193 ++------ lib/Sys/VirtV2V/Connection/LibVirtSource.pm | 247 +++++++++ .../LibVirt.pm => Connection/LibVirtTarget.pm} | 228 +++------ .../{LibVirtXML.pm => LibVirtXMLSource.pm} | 81 ++- .../{Target/RHEV.pm => Connection/RHEVTarget.pm} | 520 +++++++++++-------- .../{Connection.pm => Connection/Source.pm}...

If a volume is not an exact multiple of 512 bytes, qemu-img will report its size rounded down to a 512 byte boundary. However, when copying, the file is still read until EOF, which will return more data than was expected. This change prevents that causing a failure in itself. The situation is still not resolved, however, as there are still situations where this will cause a failure. For example,