(apologies for responding to myself) On 08/13/13 18:51, Laszlo Ersek wrote: > On 08/13/13 18:03, Andreas Färber wrote: >> Hi, >> >> Am 13.08.2013 15:30, schrieb Juerg Haefliger: >>> I'm writing/extending a little tool (courtesy of Andrew @pikewerks) >>> that dumps the RAM pages from a savevm file to a raw memory dump file >>> so that it can be analysed using tools that require a raw dump as >>> input. >> >> Can't you just use QEMU's guest-memory-dump API? Either directly or >> after loadvm'ing it. > > That used to suffer from the exact same problem Juerg described, but I > fixed it for 1.6.
... note that the savevm file format doesn't need fixing; it is meant for internal consumption only (ie. guest RAM saved in ram_addr_t space, then loaded back into ram_addr_t space). It is not meant for external tools that expect guest-phys addresses (= hwaddr). Laszlo
