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 1098040 - No warning shows when changing the maximum vcpu for a running guest
Summary: No warning shows when changing the maximum vcpu for a running guest
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-manager
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Giuseppe Scrivano
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1098035
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-15 06:57 UTC by tingting zheng
Modified: 2015-03-05 10:06 UTC (History)
6 users (show)

Fixed In Version: virt-manager-1.1.0-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1098035
Environment:
Last Closed: 2015-03-05 10:06:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0427 0 normal SHIPPED_LIVE virt-manager bug fix and enhancement update 2015-03-05 14:38:46 UTC

Description tingting zheng 2014-05-15 06:57:24 UTC 
The bug can be also reproduced on rhel7,so cloned the bug.
+++ This bug was initially created as a clone of Bug #1098035 +++

Description
No warning shows when changing the maximum vcpu for a running guest

Version:
virt-manager-0.9.0-22.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Launch virt-manager.
2.Open a running guest console,"Show virtual hardware details"->"Processor"->"CPUs"->"Maximum allocation",change the maximum vcpu,eg:change the maximum allocation from 4 to 1,then click "Apply".
3.After step 2,the maximum vcpu didn't change and no warning like "These changes will take effect after the next guest shutdown" show.

Actual results：
As step 3 shows.

Expected results:
Step 3:warning shows like "These changes will take effect after the next guest shutdown".

Additional info:
1.When change the maximum memory for a running guest,there is warning for users that the change will take effect after the next guest shutdown.
2.# virt-manager --debug
(virt-manager:24968): GSpice-WARNING **: Warning no automount-inhibiting implementation available
2014-05-14 01:59:59,110 (libvirtobject:135): Redefining 'rhel6.5' with XML diff:
--- Original XML
+++ New XML
@@ -3,7 +3,7 @@
   <uuid>0832dea3-6be4-bbad-f9b2-af965d880695</uuid>
   <memory unit="KiB">524288</memory>
   <currentMemory unit="KiB">524288</currentMemory>
-  <vcpu placement="static" current="1">4</vcpu>
+  <vcpu placement="static" current="1">1</vcpu>
   <os>
     <type arch="x86_64" machine="rhel6.5.0">hvm</type>
     <boot dev="hd"/>
Comment 2 Giuseppe Scrivano 2014-06-17 15:29:21 UTC 
patch upstream:

commit 4ac49a1d66b12ae6f7d50ec4f368ff3d770e6b42
Author: Giuseppe Scrivano <gscrivan>
Date:   Tue Jun 17 14:13:30 2014 +0200

    virt-manager: split EDIT_VCPUS and EDIT_MAXVCPUS
    
    Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1098040
    
    Signed-off-by: Giuseppe Scrivano <gscrivan>
Comment 4 tingting zheng 2014-09-11 06:46:47 UTC 
Tested pass with:
virt-manager-1.1.0-1.el7.noarch

Steps pls refer to the description.
After change the maximum/current allocation of vcpu of a running guest,there is error shows:
Some changes may require a guest shutdown to take effect.

After shutdown the guest,the change will take effect.

Refer to the above comments,move the bug to VERIFIED.
Comment 6 errata-xmlrpc 2015-03-05 10:06:38 UTC 
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://rhn.redhat.com/errata/RHBA-2015-0427.html
Note You need to log in before you can comment on or make changes to this bug.