aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMartin Kletzander <mkletzan@redhat.com>2012-08-15 09:51:58 +0200
committerMartin Kletzander <mkletzan@redhat.com>2012-09-20 16:41:07 +0200
commit78f3666fe929428016ce55694094f65efb0b9a0f (patch)
treef6289e9b43fc1a41f408424621aae11bad6b4865 /docs/formatdomain.html.in
parentQEMU Tests for reboot-timeout (diff)
downloadlibvirt-78f3666fe929428016ce55694094f65efb0b9a0f.tar.gz
libvirt-78f3666fe929428016ce55694094f65efb0b9a0f.tar.bz2
libvirt-78f3666fe929428016ce55694094f65efb0b9a0f.zip
Add support for limiting guest coredump
Sometimes when guest machine crashes, coredump can get huge due to the guest memory. This can be limited using madvise(2) system call and is being used in QEMU hypervisor. This patch adds an option for configuring that in the domain XML and related documentation.
Diffstat (limited to 'docs/formatdomain.html.in')
-rw-r--r--docs/formatdomain.html.in12
1 files changed, 9 insertions, 3 deletions
diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in
index a403ba8c5..f05350e80 100644
--- a/docs/formatdomain.html.in
+++ b/docs/formatdomain.html.in
@@ -515,9 +515,15 @@
However, the value will be rounded up to the nearest kibibyte
by libvirt, and may be further rounded to the granularity
supported by the hypervisor. Some hypervisors also enforce a
- minimum, such as
- 4000KiB. <span class='since'><code>unit</code> since
- 0.9.11</span></dd>
+ minimum, such as 4000KiB.
+
+ In the case of crash, optional attribute <code>dumpCore</code>
+ can be used to control whether the guest memory should be
+ included in the generated coredump or not (values "on", "off").
+
+ <span class='since'><code>unit</code> since 0.9.11</span>,
+ <span class='since'><code>dumpCore</code> since 0.10.2
+ (QEMU only)</span></dd>
<dt><code>currentMemory</code></dt>
<dd>The actual allocation of memory for the guest. This value can
be less than the maximum allocation, to allow for ballooning