Bug 1308746 - [RFE] PAPR Hash Page Table resizing (RHEV)
Summary: [RFE] PAPR Hash Page Table resizing (RHEV)
Keywords:
Status: CLOSED DUPLICATE of bug 1308744
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs
Version: 4.0.0
Hardware: ppc64le
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Scott Herold
QA Contact: Gil Klein
URL:
Whiteboard:
Depends On: 1305398 1308743
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-15 22:37 UTC by Karen Noel
Modified: 2016-02-15 22:40 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1308743
Environment:
Last Closed: 2016-02-15 22:40:31 UTC
oVirt Team: Virt


Attachments (Terms of Use)

Description Karen Noel 2016-02-15 22:37:03 UTC
RHEV should determine if the guest supports HPT resizing, then increase the default max size of memory.

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

In case libvirt requires changes to support HPT resizing. If no changes required, set this BZ to TestOnly.

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

Description of problem:

Allow the hash page table (HPT) of PAPR guests to be resized at runtime.

This is important for practical memory hotplug.  Without this the HPT needs to be sized for the guest's maximum possible memory - since RHEV wants to set that to 4T, this can result in a much bigger than necessary HPT which wastes host resources and can cause allocation failures.  With HV KVM the HPT is unswappable, contiguous host memory.

This BZ covers the qemu parts of this including TCG and PR KVM implementation of the necessary hypercalls, feature negotation with the guest and enabling the necessary KVM host pieces.

--- Additional comment from David Gibson on 2016-02-07 19:52:00 EST ---

An RFC has been posted upstream:

https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg05852.html

Comment 1 Karen Noel 2016-02-15 22:40:31 UTC

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


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