On 06/02/2012 12:20 PM, NoxDaFox wrote: > > For what I know it's not possible to analyze memory contained in libvirt > snapshots taken through qemu savevm. qemu 'savevm' dumps in an internal migration format. But you can use the 'migrate' command to do a migration to disk, which at least some memory analysis tools have learned how to reconstruct guest memory from. There is also a pending patch to libvirt to learn to use qemu's new 'dump-guest-memory' command which creates an ELF file corresponding to guest memory at a given point in time. The idea is that virDomainCoreDump() API will map to both qemu monitor commands for dumping guest memory. With a bit more help from qemu, it may even someday be possible to take a memory snapshot while still allowing the guest to run, and libvirt's virDomainCoreDump() would gain a new flag to expose that capability. -- Eric Blake eblake@xxxxxxxxxx +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
