[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH V3 07/22] cpr
|
From: |
Stefan Hajnoczi |
|
Subject: |
Re: [PATCH V3 07/22] cpr |
|
Date: |
Wed, 12 May 2021 17:19:02 +0100 |
On Fri, May 07, 2021 at 05:25:05AM -0700, Steve Sistare wrote:
> To use the restart mode, qemu must be started with the memfd-alloc machine
> option. The memfd's are saved to the environment and kept open across exec,
> after which they are found from the environment and re-mmap'd. Hence guest
> ram is preserved in place, albeit with new virtual addresses in the qemu
> process. The caller resumes the guest by calling cprload, which loads
> state from the file. If the VM was running at cprsave time, then VM
> execution resumes. cprsave supports any type of guest image and block
> device, but the caller must not modify guest block devices between cprsave
> and cprload.
Does QEMU's existing -object memory-backend-file on tmpfs or hugetlbfs
achieve the same thing?
signature.asc
Description: PGP signature
[PATCH V3 03/22] oslib: qemu_clr_cloexec, Steve Sistare, 2021/05/07
[PATCH V3 05/22] machine: memfd-alloc option, Steve Sistare, 2021/05/07
[PATCH V3 01/22] as_flat_walk, Steve Sistare, 2021/05/07
[PATCH V3 02/22] qemu_ram_volatile, Steve Sistare, 2021/05/07
[PATCH V3 07/22] cpr, Steve Sistare, 2021/05/07
- Re: [PATCH V3 07/22] cpr,
Stefan Hajnoczi <=
[PATCH V3 11/22] vfio-pci: refactor for cpr, Steve Sistare, 2021/05/07
[PATCH V3 14/22] vhost: reset vhost devices upon cprsave, Steve Sistare, 2021/05/07