Bug 865340 - RFE: Do not enable the ballooning device
Summary: RFE: Do not enable the ballooning device
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 1.0 (Essex)
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Daniel Berrangé
QA Contact: Yaniv Kaul
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-11 09:20 UTC by Yaniv Kaul
Modified: 2023-09-18 10:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-17 15:18:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-28806 0 None None None 2023-09-18 09:59:29 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.