aboutsummaryrefslogtreecommitdiff
path: root/tests
diff options
context:
space:
mode:
authorMartin Kletzander <mkletzan@redhat.com>2012-08-15 09:59:24 +0200
committerMartin Kletzander <mkletzan@redhat.com>2012-09-20 16:41:07 +0200
commitff2d5a3d8acded54dd1e7a660ca72f5f04c9235d (patch)
tree12010f20b6b16879e224f5d6ff7fe2ced714444a /tests
parentAdd support for limiting guest coredump (diff)
downloadlibvirt-ff2d5a3d8acded54dd1e7a660ca72f5f04c9235d.tar.gz
libvirt-ff2d5a3d8acded54dd1e7a660ca72f5f04c9235d.tar.bz2
libvirt-ff2d5a3d8acded54dd1e7a660ca72f5f04c9235d.zip
qemu: add support for dump-guest-core option
The "dump-guest-core' option is new option for the machine type (-machine pc,dump-guest-core) that controls whether the guest memory will be marked as dumpable. While testing this, I've found out that the value for the '-M' options is not parsed correctly when additional parameters are used. However, when '-machine' is used for the same options, it gets parsed as expected. That's why this patch also modifies the parsing and creating of the command line, so both '-M' and '-machine' are recognized. In QEMU's help there is only mention of the 'machine parameter now with no sign of the older '-M'.
Diffstat (limited to 'tests')
-rw-r--r--tests/qemuhelptest.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/tests/qemuhelptest.c b/tests/qemuhelptest.c
index a3d9656fd..079aef8fd 100644
--- a/tests/qemuhelptest.c
+++ b/tests/qemuhelptest.c
@@ -846,7 +846,8 @@ mymain(void)
QEMU_CAPS_VIRTIO_SCSI_PCI,
QEMU_CAPS_BLOCKIO,
QEMU_CAPS_SCSI_DISK_WWN,
- QEMU_CAPS_SECCOMP_SANDBOX);
+ QEMU_CAPS_SECCOMP_SANDBOX,
+ QEMU_CAPS_DUMP_GUEST_CORE);
return ret == 0 ? EXIT_SUCCESS : EXIT_FAILURE;
}