Bug 1328675 - virsh: blockpull: bad error on arg overflow: argument key 'speed' must not be negative
Summary: virsh: blockpull: bad error on arg overflow: argument key 'speed' must not be...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-20 03:14 UTC by Fangge Jin
Modified: 2024-12-17 12:04 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-12-17 12:04:39 UTC
Embargoed:


Attachments (Terms of Use)

Description Fangge Jin 2016-04-20 03:14:49 UTC
Description of problem:
When use 9223372036854775808( the_maximum_of_long_long + 1) for blockjob bandwidth, libvirt reports "argument key 'speed' must not be negative".

Version-Release number of selected component:
libvirt-1.3.3-2.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
virsh # start rhel7.2-1030
Domain rhel7.2-1030 started

virsh # snapshot-create rhel7.2-1030 --disk-only
Domain snapshot 1461044800 created

virsh # blockpull rhel7.2-1030 /var/lib/libvirt/images/rhel6.6-GUI.1461044800 --bytes 9223372036854775808
error: internal error: argument key 'speed' must not be negative

virsh # blockpull rhel7.2-1030 /var/lib/libvirt/images/rhel6.6-GUI.1461044800 --bytes 9223372036854775807
Block Pull started


Actual results:
When use 9223372036854775808( the maximum of long long + 1) for blockjob bandwidth, libvirt reports "argument key 'speed' must not be negative".

Expected results:
Libvirt reports error like this:
error: numerical overflow: 'speed' must be less than 9223372036854775807


Additional info:
Same issue exists with blockcommit/blockcopy/blockjob

Comment 3 Daniel Berrangé 2024-12-17 12:04:39 UTC
Thank you for reporting this issue to the libvirt project. Unfortunately we have been unable to resolve this issue due to insufficient maintainer capacity and it will now be closed. This is not a reflection on the possible validity of the issue, merely the lack of resources to investigate and address it, for which we apologise. If you none the less feel the issue is still important, you may choose to report it again at the new project issue tracker https://gitlab.com/libvirt/libvirt/-/issues The project also welcomes contribution from anyone who believes they can provide a solution.


Note You need to log in before you can comment on or make changes to this bug.