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.

Description of problem:
Suggest to improve the error message when set improper vcpu current number using virsh edit.

Version-Release number of selected component (if applicable):
libvirt-3.9.0-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. modify the vcpu current number more than the max vcpu number.

# virsh edit rhel7
...
<vcpu placement='static' current='9'>8</vcpu>
...

error: unsupported configuration: maxvcpus must not be less than current vcpus (9 < 8)
Failed. Try again? [y,n,i,f,?]: 


Actual results:
looks like the two numbers are reversed. Also they don't make much sense in the format they are in. The message should be changed.

Expected results:
How about
"error: unsupported configuration: current vcpus must be less than maxvcpus
Failed. Try again? [y,n,i,f,?]: "

Additional info:

Fixed upstream:

commit 50712e14f40ffdac8a71ce9ef091e4e7bd822585
Author: Peter Krempa <pkrempa>
Date:   Fri Nov 3 09:31:30 2017 +0100

    conf: Fix message when maximum vCPU count is less than current
    
    Reword the message and drop the numbers (which were reversed) from it
    so that it actually makes sense.

Test on libvirt-3.9.0-2.el7.x86_64, the error message is sensible, verify this bug

# virsh edit rhel
error: unsupported configuration: maximum vCPU count must not be less than current vCPU count
Failed. Try again? [y,n,i,f,?]: ==> press 'i'
error: unsupported configuration: maximum vCPU count must not be less than current vCPU count
Failed. Try again? [y,n,f,?]:  ==> press 'f'
error: unsupported configuration: maximum vCPU count must not be less than current vCPU count
Failed. Try again? [y,n,f,?]:

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:0704