On 01/29/2014 07:52 PM, Daniel P. Berrange wrote:
This patch is used to add dump_memory_format to qemu.conf and make the specified format as the default dump format of 'virsh dump --memory-only'. But when "--compress" is specified with dump command, the format configured by dump_memory_format will be overrided. dump_memory_format can one of elf, kdump-zlib, kdump-lzo and kdump-snappy. And elf is the default value. I think it is pretty horribly misleading to applications if they leave out the VIR_DUMP_COMPRESS flag when invoking the API but
On Wed, Jan 29, 2014 at 10:15:36AM +0800, Qiao Nuohan wrote: libvirt then asks for compression anyway. If an application is only able to cope with uncompressed format then they are screwed by the host level setting which they can't see.
Setting in qemu.conf can also be uncompressed format. The problem is when qemu.conf is set to compressed format, but application can only deal with uncompressed format, then "virsh dump" *need an option* to make qemu dump an uncompressed core. Maybe I misunderstand your comments, please correct me. Thanks!
Daniel
-- Regards Qiao Nuohan