diff mbox

[aws,PATCHv2] UBUNTU: [Config] AWS: CONFIG_XEN_BALLOON=n

Message ID 20170301214852.13881-1-dan.streetman@canonical.com
State New
Headers show

Commit Message

Dan Streetman March 1, 2017, 9:48 p.m. UTC 
BugLink: http://bugs.launchpad.net/bugs/1668129

Disable XEN_BALLOON, as ballooning is not used by AWS and it causes
problems when the guest uses the memory in the balloon region; e.g.
for DMA with a hypervisor-provided NVMe device, because the hypervisor
is not expecting DMA to/from the physical pages in the ballooned region.

Signed-off-by: Dan Streetman <dan.streetman@canonical.com>
---
 debian.aws/config/config.common.ubuntu | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

Comments

Kamal Mostafa March 1, 2017, 10:14 p.m. UTC | #1 
Builds and boots okay on an AWS instance.  ACK for [AWS].

 -Kamal
Kamal Mostafa March 1, 2017, 10:24 p.m. UTC | #2 
(also acked by bjf via irc).

Applied to [aws].

 -Kamal
diff mbox

Patch

diff --git a/debian.aws/config/config.common.ubuntu b/debian.aws/config/config.common.ubuntu
index 5456c6b..d546b71 100644
--- a/debian.aws/config/config.common.ubuntu
+++ b/debian.aws/config/config.common.ubuntu
@@ -5424,9 +5424,7 @@  CONFIG_XEN_ACPI=y
 CONFIG_XEN_ACPI_PROCESSOR=y
 CONFIG_XEN_AUTO_XLATE=y
 CONFIG_XEN_BACKEND=y
-CONFIG_XEN_BALLOON=y
-CONFIG_XEN_BALLOON_MEMORY_HOTPLUG=y
-CONFIG_XEN_BALLOON_MEMORY_HOTPLUG_LIMIT=512
+# CONFIG_XEN_BALLOON is not set
 CONFIG_XEN_BLKDEV_BACKEND=m
 CONFIG_XEN_BLKDEV_FRONTEND=y
 CONFIG_XEN_COMPAT_XENFS=y
@@ -5448,10 +5446,8 @@  CONFIG_XEN_PRIVCMD=m
 CONFIG_XEN_PVH=y
 CONFIG_XEN_PVHVM=y
 CONFIG_XEN_SAVE_RESTORE=y
-CONFIG_XEN_SCRUB_PAGES=y
 CONFIG_XEN_SCSI_BACKEND=m
 CONFIG_XEN_SCSI_FRONTEND=m
-CONFIG_XEN_SELFBALLOONING=y
 CONFIG_XEN_SYMS=y
 CONFIG_XEN_SYS_HYPERVISOR=y
 CONFIG_XEN_TMEM=m