Re: [Qemu-devel] Savevm and loadvm not working

[sridhar kulkarni <sridhar_kulk@yahoo.com>]

 

    On Thursday, February 1, 2018 5:56 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
 

 On 1 February 2018 at 12:19, sridhar kulkarni via Qemu-devel
<qemu-devel@nongnu.org> wrote:
> I thought that RAM contents are not saved because of return value RAM_SAVE_CONTROL_NOT_SUPP. Now that you clarified about this, I debugged this further. After doing loadvm operation, I am getting following error,qemu-system-arm: error while loading state for instance 0x0 of device 'cpu'
> qemu-system-arm: Error -1 while loading VM state
> I figured out that, this error is because of following function returning FALSE. "write_raw_cp_reg" writes a value and "read_raw_cp_reg" reads the value back. There is mismatch between what we write and what is being read back, and hence function returns FALSE.
> Between I want to mention that, I am trying the snapshot on a VM which runs ARM 7 core. I am not sure if this snapshot feature is fully function for ARM targets.

It is supposed to work for ARM, and it does for
the CPUs I've tested it with. Which exact CPU
model are you using? (Do you really mean "ARM 7"?
We don't support that. We have ARMv7 architecture
CPUs like the cortex-a9 -- did you mean one of those?)

Are you using an unmodified upstream QEMU? We don't
have an "arm-machine" board model which is what your
command line is using with "-M arm-machine", so if
you're using a modified QEMU it's possible those
modifications haven't been written to support VM
state saving.

The next step in debugging would be to run QEMU under
gdb or add tracing printfs so that you can identify
which emulated system register it is that is causing the
failure.

Sorry I meant to say arm a7. We are using a custom board "arm-machine" which is based on Vexpress-a15 but we use a7 core. I learnt reading through web sources that A7 emulation is not supported in qemu. Is this causing this behaviour? But in general we are able to run all our code on this virtual board without any issues. While doing snapshot, this problem is seen.

thanks
-- PMM