[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] Re: [CFR 2/10] qmp: memsave command
From: |
Anthony Liguori |
Subject: |
[Qemu-devel] Re: [CFR 2/10] qmp: memsave command |
Date: |
Wed, 16 Jun 2010 13:49:18 -0500 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100423 Lightning/1.0b1 Thunderbird/3.0.4 |
On 06/16/2010 10:45 AM, Stefan Hajnoczi wrote:
memsave
-------
Save to disk virtual memory dump starting at 'val' of size 'size'.
Arguments:
- "val": the starting address (json-int)
s/val/address/
- "size": the memory size, in bytes (json-int)
The number of bytes to dump.
- "filename": file path (json-string)
We really ought to return this memory as a Base64 encoded blob.
Example:
-> { "execute": "memsave",
"arguments": { "val": 10,
"size": 100,
"filename": "/tmp/virtual-mem-dump" } }
<- { "return": {} }
Note: Depends on the current CPU.
Ought to take a cpu_id and avoid the silliness of current CPU.
What happens if the virtual address range is non-existent? What if it's
only partially mapped?
Regards,
Anthony Liguori
- [Qemu-devel] [CFR 0/10] QMP specification review (Part 2), Stefan Hajnoczi, 2010/06/16
- [Qemu-devel] [CFR 2/10] qmp: memsave command, Stefan Hajnoczi, 2010/06/16
- [Qemu-devel] [CFR 6/10] qmp: migrate command, Stefan Hajnoczi, 2010/06/16
- [Qemu-devel] [CFR 5/10] qmp: migrate_set_speed command, Stefan Hajnoczi, 2010/06/16
- [Qemu-devel] [CFR 7/10] qmp: netdev_add command, Stefan Hajnoczi, 2010/06/16
- [Qemu-devel] [CFR 9/10] qmp: pmemsave command, Stefan Hajnoczi, 2010/06/16