Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot

as guest physical or host > virtual address. > Thanks, > Pankaj > > Thanks > > > Junyan > > > From: Qemu-devel on > > behalf > > of Pankaj Gupta > > > Sent: Friday, June 8, 2018 7:59:24 AM > > > To: Junyan He > > >

Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot

area as guest physical or host virtual address. Thanks, Pankaj > Thanks > Junyan > From: Qemu-devel on behalf > of Pankaj Gupta > Sent: Friday, June 8, 2018 7:59:24 AM > To: Junyan He > Cc: Kevin Wolf; qemu block; qemu-devel@nongnu.org; Stefan Hajnoczi; Max Reitz >

Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot

AM To: Junyan He Cc: Kevin Wolf; qemu block; qemu-devel@nongnu.org; Stefan Hajnoczi; Max Reitz Subject: Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot Hi Junyan, AFAICU you are trying to utilize qcow2 capabilities to do incremental snapshot. As I understand

Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot

On Fri, Jun 08, 2018 at 05:02:58AM +, He, Junyan wrote: > I use the simple way to handle this, > 1. Separate the nvdimm region from ram when do snapshot. > 2. If the first time, we dump all the nvdimm data the same as ram, and enable > dirty log trace > for nvdimm kind region. > 3. If not the

Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot

Hi Junyan, AFAICU you are trying to utilize qcow2 capabilities to do incremental snapshot. As I understand NVDIMM device (being it real or emulated), its contents are always be backed up in backing device. Now, the question comes to take a snapshot at some point in time. You are trying to

Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot

Dear all: I just switched from graphic/media field to virtualization at the end of the last year, so I am sorry that though I have already try my best but I still feel a little dizzy about your previous discussion about NVDimm via block layer:) In today's qemu, we use the SaveVMHandlers

Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot

On Wed, May 30, 2018 at 06:07:19PM +0200, Kevin Wolf wrote: > Am 30.05.2018 um 16:44 hat Stefan Hajnoczi geschrieben: > > On Mon, May 14, 2018 at 02:48:47PM +0100, Stefan Hajnoczi wrote: > > > On Fri, May 11, 2018 at 07:25:31PM +0200, Kevin Wolf wrote: > > > > Am 10.05.2018 um 10:26 hat Stefan

Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot

Am 30.05.2018 um 16:44 hat Stefan Hajnoczi geschrieben: > On Mon, May 14, 2018 at 02:48:47PM +0100, Stefan Hajnoczi wrote: > > On Fri, May 11, 2018 at 07:25:31PM +0200, Kevin Wolf wrote: > > > Am 10.05.2018 um 10:26 hat Stefan Hajnoczi geschrieben: > > > > On Wed, May 09, 2018 at 07:54:31PM +0200,

Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot

On Mon, May 14, 2018 at 02:48:47PM +0100, Stefan Hajnoczi wrote: > On Fri, May 11, 2018 at 07:25:31PM +0200, Kevin Wolf wrote: > > Am 10.05.2018 um 10:26 hat Stefan Hajnoczi geschrieben: > > > On Wed, May 09, 2018 at 07:54:31PM +0200, Max Reitz wrote: > > > > On 2018-05-09 12:16, Stefan Hajnoczi

Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot

Hi yang, Alibaba made this proposal for NVDimm snapshot optimization, can you give some advice about this discussion? Thanks -Original Message- From: Stefan Hajnoczi [mailto:stefa...@gmail.com] Sent: Monday, May 14, 2018 9:49 PM To: Kevin Wolf Cc: Stefan Hajnoczi

Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot

On Fri, May 11, 2018 at 07:25:31PM +0200, Kevin Wolf wrote: > Am 10.05.2018 um 10:26 hat Stefan Hajnoczi geschrieben: > > On Wed, May 09, 2018 at 07:54:31PM +0200, Max Reitz wrote: > > > On 2018-05-09 12:16, Stefan Hajnoczi wrote: > > > > On Tue, May 08, 2018 at 05:03:09PM +0200, Kevin Wolf wrote:

Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot

Am 10.05.2018 um 10:26 hat Stefan Hajnoczi geschrieben: > On Wed, May 09, 2018 at 07:54:31PM +0200, Max Reitz wrote: > > On 2018-05-09 12:16, Stefan Hajnoczi wrote: > > > On Tue, May 08, 2018 at 05:03:09PM +0200, Kevin Wolf wrote: > > >> Am 08.05.2018 um 16:41 hat Eric Blake geschrieben: > > >>>

Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot

On Wed, May 09, 2018 at 07:54:31PM +0200, Max Reitz wrote: > On 2018-05-09 12:16, Stefan Hajnoczi wrote: > > On Tue, May 08, 2018 at 05:03:09PM +0200, Kevin Wolf wrote: > >> Am 08.05.2018 um 16:41 hat Eric Blake geschrieben: > >>> On 12/25/2017 01:33 AM, He Junyan wrote: > >> 2. Make the nvdimm

Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot

On 2018-05-09 12:16, Stefan Hajnoczi wrote: > On Tue, May 08, 2018 at 05:03:09PM +0200, Kevin Wolf wrote: >> Am 08.05.2018 um 16:41 hat Eric Blake geschrieben: >>> On 12/25/2017 01:33 AM, He Junyan wrote: >> 2. Make the nvdimm device use the QEMU block layer so that it is backed >>by a non-raw

Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot

On Tue, May 08, 2018 at 05:03:09PM +0200, Kevin Wolf wrote: > Am 08.05.2018 um 16:41 hat Eric Blake geschrieben: > > On 12/25/2017 01:33 AM, He Junyan wrote: > 2. Make the nvdimm device use the QEMU block layer so that it is backed >by a non-raw disk image (such as a qcow2 file representing

Re: [Qemu-devel] [Qemu-block] Some question about savem/qcow2 incremental snapshot

Am 08.05.2018 um 16:41 hat Eric Blake geschrieben: > On 12/25/2017 01:33 AM, He Junyan wrote: > > hi all: > > > > I am now focusing on snapshot optimization for Intel NVDimm kind > > memory. Different from the normal memory, the NVDimm may be 128G, 256G > > or even more for just one guest, and