Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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
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 2Giuseppe Scrivano
2014-05-15 08:59:25 UTC
it looks like a minor issue to address for RHEL-6.6, closing as WONTFIX. Please reopen if you disagree.
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"/>