Bug 545119

Summary:	[RFE] Add 'default-vcpus' / 'max-vcpus' options to VMM
Product:	Red Hat Enterprise Linux 5	Reporter:	Michal Novotny <minovotn>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED WONTFIX	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.5	CC:	areis, berrange, clalance, crobinso, jwest, minovotn, riek, sghosh, smayhew, tao, virt-maint, xen-maint
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	545118	Environment:
Last Closed:	2011-04-19 19:02:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	545118
Bug Blocks:	554476

Description Michal Novotny 2009-12-07 16:27:17 UTC

+++ This bug was initially created as a clone of Bug #545118 +++

+++ This bug was initially created as a clone of Bug #453042 +++

BZ #545118 introduces request for adding default-vcpus and max-vcpus options in libvirt API to allow number of initial and maximum vcpus set up and not to allocate all the vcpus to the guest at the boot time. Since it is going to be added to be libvirt (see RFE at BZ #545118) we need an interface to add it to virt-manager as well since now virt-manager is showing just maximum allocation set according to the HV it uses but the maximum allocation should be set to one from the HV configuration for this particular guest.

Comment 4 RHEL Program Management 2010-08-09 18:29:47 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 6 RHEL Program Management 2011-01-11 20:49:18 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 7 RHEL Program Management 2011-01-12 15:16:46 UTC

This request was erroneously denied for the current release of
Red Hat Enterprise Linux.  The error has been fixed and this
request has been re-proposed for the current release.

Comment 8 Cole Robinson 2011-01-13 19:25:14 UTC

This is upstream now:

http://hg.fedorahosted.org/hg/virt-manager/rev/5bdc66e596cc

Though not sure what the dev effort will look like for a backport, the codebases are pretty different now.

Comment 9 Cole Robinson 2011-03-10 21:55:07 UTC

Since we are pretty late in the RHEL5 cycle, I'm hesitant about adding this to virt-manager, since it would basically require a reimplementation since the relevant 5.6 code is 2 years old.

How exactly does the customer want to use this functionality? Is it more important to set this value at install time or for existing guests? Is virt-manager support really necessary or is editing the XML by hand with 'virsh edit' sufficient? Is the customer using xen or kvm?

Comment 11 Cole Robinson 2011-04-19 19:02:20 UTC

Okay, since a private comment indicated that the virsh functionality is sufficient for RHEL5, closing this as WONTFIX.