SCIENTIFIC-LINUX-USERS Archives

March 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
virt-manager and CPU Maximum allocation bug
From:
Chuck Munro <[log in to unmask]>
Reply To:
[log in to unmask]
Date:
Sun, 20 Mar 2011 20:08:28 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (20 lines) 
Hello all,

I'm happily running SL-6 as a virtual machine host, but have a question 
regarding a known virt-manager GUI bug:

If I initially allocate some number of CPUs when creating a new guest 
OS, and later reduce the allocation using virt-manager, the new 
allocation also becomes the Maximum allocation upon restart, and cannot 
be increased.

In other words, after defining and running a new guest OS, I can't 
increase the number of CPUs allocated to it.  The workaround is to 
manually edit the guest's XML file and then 'define' it with virsh.

According to RedHat this is fixed in virt-manager 0.8.6-1.el6 (Bug 639695).

Will this be updated in SL any time soon?

Chuck

ATOM RSS1 RSS2