Re: [libvirt-users] Understanding the contents of virsh dump --memory-only

On Tue, Aug 01, 2017 at 10:22:43PM -0400, Arnabjyoti Kalita wrote: You are running a QEMU machine and the dump is generated by qemu, so they would be able to explain to much further detail, I'm sure. Anyway, here goes my try. Just to be clear, this is the memory of the machine with kernel and several other things loaded. I'm not sure what are all the segments, but since the dump acts as something you can use to debug the guest OS using the crash utility, which is somehow enhanced gdb for this purpose, IIRC, then I guess it's the MMU mapping of everything in the guest OS. My guess is that those are the addresses from the MMU. Each segment has it's own vaddr <-> paddr mapping. It depends on what you mean by loading. You wouldn't be starting that binary as any other program, it's rather a dump as you would have with a coredump. Physical address is probably just the location in the guest machine, so the thing with paddr 0 would be seabios or something BIOS-related, etc. If you want precise answers and not guesses, I would suggest the qemu mailing list or any other related list. libvirt is not the best choice here unless someone from the other communities replies here. HTH, Martin