On Thursday, February 1, 2018 5:56 PM, Peter Maydell
wrote:
On 1 February 2018 at 12:19, sridhar kulkarni via Qemu-devel
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 debugge
On Tuesday, January 30, 2018 5:25 PM, Peter Xu wrote:
On Tue, Jan 30, 2018 at 10:34:31AM +, sridhar kulkarni via Qemu-devel
wrote:
> Hi,
> I am new bee to snapshot feature and how to use it correctly. My requirement
> is simple, in that I want to snapshot the running VM
Hi,
I am new bee to snapshot feature and how to use it correctly. My requirement is
simple, in that I want to snapshot the running VM and save the snapshot file.
Using the snapshot file, I want to boot the VM directly to snapshot state.I
came across the qemu monitors "savevm" and "loadvm" comman
I am working on creating a snapshot for ARM based VM running on A7. We don't
use disk images, so to save the snapshot I am passing "-drive if=none,
format=qcow2, file=/home/sridhar/qemu_disk_images/dummy.qcow2" as dummy disk to
save the snapshot.
Then from qemu monitor, I run the "savevm" comman
We have two applications running on real custom board with custom asic and has
two arm cores. Each application runs on different core, and uses shared memory
for inter application high bandwidth transferss. The trigger for this RPC
mailbox communication where each core can send interrupt to othe
Hi,
I am working on a requirement where I need to have shared memory IPC between
two guest VM's running different OS. Both VM's use vexpress-A9 boards. I came
across the "ivshmem" implementation and have some questions. Whether the
"ivshmem" implementation can be used on qemu-system-arm? I under
