RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 974010 - It should report error while the bps or iops values are not supported by guest
Summary: It should report error while the bps or iops values are not supported by guest
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Ján Tomko
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-13 09:30 UTC by Xuesong Zhang
Modified: 2014-06-18 00:51 UTC (History)
6 users (show)

Fixed In Version: libvirt-1.1.0-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 12:41:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Xuesong Zhang 2013-06-13 09:30:52 UTC 
Description of problem
It should report error while the bps or iops values are not supported by guest.

Version-Release number of selected component (if applicable):
libvirt-1.0.6-1.el7.x86_64
kernel-3.9.0-0.55.el7.x86_64
qemu-kvm-1.5.0-2.el7.x86_64

How reproducible:
100%

Steps
1. prepare one running guest.

2. Set iotune total_bytes_sec
# virsh blkdeviotune b hda --total-bytes-sec 12212221112000930000
error: Unable to change block I/O throttle
error: internal error Unexpected error

3. Set iotune total_bytes_sec with option --config
#virsh blkdeviotune b hda --total-bytes-sec 12212221112000930000 --config

4. check in the inactive dumpxml
# virsh dumpxml b --inactive |grep -A 5 disk
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='none'/>
      <source file='/var/lib/libvirt/images/kvm-rhel6.4-x86_64-qcow2.img'/>
      <target dev='hda' bus='ide'/>
      <iotune>
        <total_bytes_sec>12212221112000930000</total_bytes_sec>
......
5. destroy this domain and start it again.
# virsh destroy b
Domain b destroyed

# virsh start b
error: Failed to start domain b
error: internal error process exited while connecting to monitor: char device redirected to /dev/pts/1 (label charserial0)
qemu-kvm: -drive file=/var/lib/libvirt/images/kvm-rhel6.4-x86_64-qcow2.img,if=none,id=drive-ide0-0-0,format=qcow2,cache=none,bps=12212221112000930000: bps and iops values must be 0 or greater


Actual results:
as steps

Expected results:
It should report error in step3 if the bos or iops valuses are not supportted by guest.
The error message should be same as the one in step 2.
Comment 2 Ján Tomko 2013-06-24 12:29:33 UTC 
Upstream patch proposed:
https://www.redhat.com/archives/libvir-list/2013-June/msg00979.html
Comment 3 Ján Tomko 2013-06-24 13:36:32 UTC 
Now fixed upstream:
commit d3c87884927e6b745d0a5680e6d94a40c4f484f7
Author:     Ján Tomko <jtomko>
AuthorDate: 2013-06-24 14:18:14 +0200
Commit:     Ján Tomko <jtomko>
CommitDate: 2013-06-24 14:18:14 +0200

    qemu: check if block I/O limits fit into long long
    
    We can only pass values up to LLONG_MAX through JSON
    and QEMU checks if the int64_t number is not negative
    at startup since 1.5.0.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=974010

git describe: v1.0.6-120-gd3c8788
Comment 4 hyao@redhat.com 2013-06-28 05:46:24 UTC 
Reproduce the bug with same version 
#rpm -qa libvirt qemu-kvm kernel
qemu-kvm-1.5.0-2.el7.x86_64
libvirt-1.0.6-1.el7.x86_64
kernel-3.9.0-0.55.el7.x86_64
Comment 5 Shanzhi Yu 2013-07-03 02:41:40 UTC 
verify this bug with libvirt-1.1.0-1.el7.x86_64.

Steps:
1. prepare one running guest.

2. Set iotune total_bytes_sec
# virsh blkdeviotune kvm-rhel6.3-x86_64-qcow2-virtio vda --total-bytes-sec 12212221112000930000
error: Unable to change block I/O throttle
error: numerical overflow: block I/O throttle limit value must be less than 9223372036854775807

3. Set iotune total_bytes_sec with option --config
#virsh blkdeviotune kvm-rhel6.3-x86_64-qcow2-virtio hda --total-bytes-sec 12212221112000930000 --config
error: Unable to change block I/O throttle
error: numerical overflow: block I/O throttle limit value must be less than 9223372036854775807
4. check in the inactive dumpxml
# virsh dumpxml kvm-rhel6.3-x86_64-qcow2-virtio --inactive |grep -A 5 disk
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='none'/>
      <source file='/var/lib/libvirt/images/kvm-rhel6.3-x86_64-qcow2.img'/>
      <target dev='hda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </disk>
......
The error is clear, so verify this bug.
Comment 6 Ludek Smid 2014-06-13 12:41:21 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.