Bug 865340

Summary:	RFE: Do not enable the ballooning device
Product:	Red Hat OpenStack	Reporter:	Yaniv Kaul <ykaul>
Component:	openstack-nova	Assignee:	Daniel Berrangé <berrange>
Status:	CLOSED WONTFIX	QA Contact:	Yaniv Kaul <ykaul>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.0 (Essex)	CC:	apevec, jkt, markmc
Target Milestone:	---	Keywords:	Improvement
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-17 15:18:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yaniv Kaul 2012-10-11 09:20:27 UTC

Description of problem:
Currently, we enable the ballooning device, although we don't use it. It only takes a PCI slot, and provides no value whatsoever. 

(-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 in the QEMU command line)

Version-Release number of selected component (if applicable):
Essex

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 3 Daniel Berrangé 2012-12-17 15:18:55 UTC

Even if the balloon device isn't used for ballooning memory, it can still be used to access guest OS memory statistics, which does provide value. I don't believe typical cloud deployment is going to be running into the PCI device slot limit for virtio disks, and even if it did, we would be better off using virtio-scsi to increase the max disk limit, rather than dropping virtio balloon which merely gains you 1 extra disk.