Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1036492

Summary: [RFE] [OVIRT] [VDSM] Hot Plug CPU - Support dynamic virtual CPU allocation and deallocation
Product: [Retired] oVirt Reporter: Roy Golan <rgolan>
Component: vdsmAssignee: Roy Golan <rgolan>
Status: CLOSED DUPLICATE QA Contact: Haim <hateya>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: abaron, acathrow, ahoness, bazulay, bsarathy, byount, iheim, juzhang, jwang, knoel, lpeer, mgoldboi, pablo.iranzo, rbinkhor, rgolan, rnelson, rshutt, sherold, sputhenp, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 833102
: 1036764 1036767 1036768 1036770 (view as bug list) Environment:
Last Closed: 2013-12-12 08:42:03 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: 533138, 562886    
Bug Blocks: 790582, 806907, 833102, 962051, 990116, 1036764, 1036767, 1036768, 1036770, 1036777    

Description Roy Golan 2013-12-02 06:55:54 UTC
oVirt VDSM should support dynamically add/remove virtual CPUs to/from a guest that has this capability

WIKI: www.ovirt.org/Hot_plug_cpu

libvirt's api is setVcpus which is used for both add/remove. 
The guest is configured from the start with some max number of CPUs, and the initial number, the one which was used up till now set as "current". e.g

n: number of CPUs set to start the VM with
m: maximum number of CPUs a guest can have

old:
<vcpu>n</vcpu>

new:
<vcpu current="n" placement="static">m</vcpu>


new api verb:

setNumberOfCpus <vmId> <numberOfCpus>


A seperate RFE will be open for ovirt-engine

Comment 1 Itamar Heim 2013-12-07 20:40:08 UTC
*** Bug 1036767 has been marked as a duplicate of this bug. ***

Comment 2 Itamar Heim 2013-12-12 08:42:03 UTC

*** This bug has been marked as a duplicate of bug 1036764 ***