summaryrefslogtreecommitdiff
path: root/qemu-monitor.hx
diff options
context:
space:
mode:
authorAdam Litke <agl@us.ibm.com>2010-01-26 14:17:35 -0600
committerAnthony Liguori <aliguori@us.ibm.com>2010-01-26 17:08:03 -0600
commit605dbb9c7d45e148ad324fd2be6d67c424426ff4 (patch)
tree89b9362c879d319b5061424035e3dbead9555e70 /qemu-monitor.hx
parent7a70c9da4f4e92d71a3438fb51fd939b79e5dc7c (diff)
downloadqemu-605dbb9c7d45e148ad324fd2be6d67c424426ff4.tar.gz
qemu-605dbb9c7d45e148ad324fd2be6d67c424426ff4.tar.bz2
qemu-605dbb9c7d45e148ad324fd2be6d67c424426ff4.zip
virtio: Add memory statistics reporting to the balloon driver
When using ballooning to manage overcommitted memory on a host, a system for guests to communicate their memory usage to the host can provide information that will minimize the impact of ballooning on the guests. The current method employs a daemon running in each guest that communicates memory statistics to a host daemon at a specified time interval. The host daemon aggregates this information and inflates and/or deflates balloons according to the level of host memory pressure. This approach is effective but overly complex since a daemon must be installed inside each guest and coordinated to communicate with the host. A simpler approach is to collect memory statistics in the virtio balloon driver and communicate them directly to the hypervisor. Signed-off-by: Adam Litke <agl@us.ibm.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'qemu-monitor.hx')
-rw-r--r--qemu-monitor.hx3
1 files changed, 2 insertions, 1 deletions
diff --git a/qemu-monitor.hx b/qemu-monitor.hx
index 415734a464..b51bb47f25 100644
--- a/qemu-monitor.hx
+++ b/qemu-monitor.hx
@@ -891,7 +891,8 @@ ETEXI
.params = "target",
.help = "request VM to change it's memory allocation (in MB)",
.user_print = monitor_user_noop,
- .mhandler.cmd_new = do_balloon,
+ .mhandler.cmd_async = do_balloon,
+ .async = 1,
},
STEXI