physical memory dump problem

physical memory dump problem

[Matteo Signorini]

Hi!

I have a problem with both kvm pmemsave and memsave functions.
(I know that both invoke the cpu_physical_memory_rw function)

I'm trying to dump a guest physical memory region (sys_call_table for example).
I know that , for example, the sys_call_table is stored at
0xffffffff8133c620 phys addr (found in System.map)
but if I try to run "pmemsave 0xffffffff8133c620 100 test" in kvm's monitor,
it doesn't find anything but a bunch of 0.
I've also tried with other kernel objects ( idt_table,
exit_exception_table, error_table)
addresses but the result was the same.

What am i doing wrong?
Is there a problem with memory page access rights?
What is the best way to make a dump of a guest kernel object?
I am using kvm version 85 on a dual core Amd cpu.

thanks,

Matteo

Re: physical memory dump problem

[Avi Kivity]

Matteo Signorini wrote:
> Hi!
>
> I have a problem with both kvm pmemsave and memsave functions.
> (I know that both invoke the cpu_physical_memory_rw function)
>
> I'm trying to dump a guest physical memory region (sys_call_table for example).
> I know that , for example, the sys_call_table is stored at
> 0xffffffff8133c620 phys addr (found in System.map)
>   

System.map lists virtual addresses, not physical addresses.  Try memsave 
instead.


-- 
error compiling committee.c: too many arguments to function