virt-manager changes the value of 'Maximum allocation' of CPU improperly

Solution Verified - Updated -

Issue

  • virt-manager changes the value of "Maximum allocation" of CPU improperly when a guest OS starts up after changing the value of "Change allocation".
  • Due to this behavior, "Change allocation" can't be set up to the number of "Host CPUs".
  • Step to Reproduce:
    1. Check that a guest OS is stopping.
# virsh list --inactive
<Stopped guest(s) appear.>

2. Open "virtual hardware details" of the stopped guest OS on virt-manager.

3. Change the value of "Change allocation" to other value.

4. Click "Apply" button.

5. Start up the guest OS

6. Check the value of "Maximum allocation" of CPU on "virtual hardware details"
<"Maximum allocation" should be changed to some value.>

Environment

  • Red Hat Enterprise Linux 6
  • virt-manager-0.8.4-8.el6.noarch

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content