diff options
| author | Jason Baron <jbaron@redhat.com> | 2012-08-02 15:44:16 -0400 |
|---|---|---|
| committer | Anthony Liguori <aliguori@us.ibm.com> | 2012-08-16 13:41:15 -0500 |
| commit | ddb97f1debbb6be8d871f3b565f7b8befebf0f4f (patch) | |
| tree | a81ce727e2c5f9d058d156b0754bdbaaafd00d25 /block.c | |
| parent | 3c4a4d0dcbf4269e125f92df06816db1c1e86d20 (diff) | |
| download | qemu-ddb97f1debbb6be8d871f3b565f7b8befebf0f4f.zip qemu-ddb97f1debbb6be8d871f3b565f7b8befebf0f4f.tar.gz qemu-ddb97f1debbb6be8d871f3b565f7b8befebf0f4f.tar.bz2 | |
memory: add -machine dump-guest-core=on|off
Add a new '[,dump-guest-core=on|off]' option to the '-machine' option. When
'dump-guest-core=off' is specified, guest memory is omitted from the core dump.
The default behavior continues to be to include guest memory when a core dump is
triggered. In my testing, this brought the core dump size down from 384MB to 6MB
on a 2GB guest.
Is anything additional required to preserve this setting for migration or
savevm? I don't believe so.
Changelog:
v3:
Eliminate globals as per Anthony's suggestion
set no dump from qemu_ram_remap() as well
v2:
move the option from -m to -machine, rename option dump -> dump-guest-core
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'block.c')
0 files changed, 0 insertions, 0 deletions