From: Paolo Bonzini <pbonzini@redhat.com>
To: Zhang Haoyu <zhanghy@sangfor.com.cn>,
Kashyap Chamarthy <kashyapc@fedoraproject.org>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Fam Zheng <famz@redhat.com>
Subject: Re: [question] incremental backup a running vm
Date: Mon, 26 Jan 2015 10:29:24 +0100 [thread overview]
Message-ID: <54C608F4.4020905@redhat.com> (raw)
In-Reply-To: <201501260907583380898@sangfor.com.cn>
On 26/01/2015 02:07, Zhang Haoyu wrote:
> Hi, Kashyap
> I've tried ‘drive_backup’ via QMP,
> but the snapshots were missed to backup to destination,
> I think the reason is that backup_run() only copy the
> guest data regarding qcow2 image.
Yes, that's the case.
QEMU cannot still access internal snapshots while the file is open.
External snapshots are opened read-only, and can be copied with "cp"
while QEMU is running.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Zhang Haoyu <zhanghy@sangfor.com.cn>,
Kashyap Chamarthy <kashyapc@fedoraproject.org>
Cc: Fam Zheng <famz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [question] incremental backup a running vm
Date: Mon, 26 Jan 2015 10:29:24 +0100 [thread overview]
Message-ID: <54C608F4.4020905@redhat.com> (raw)
In-Reply-To: <201501260907583380898@sangfor.com.cn>
On 26/01/2015 02:07, Zhang Haoyu wrote:
> Hi, Kashyap
> I've tried ‘drive_backup’ via QMP,
> but the snapshots were missed to backup to destination,
> I think the reason is that backup_run() only copy the
> guest data regarding qcow2 image.
Yes, that's the case.
QEMU cannot still access internal snapshots while the file is open.
External snapshots are opened read-only, and can be copied with "cp"
while QEMU is running.
Paolo
next prev parent reply other threads:[~2015-01-26 9:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 10:32 [question] incremental backup a running vm Zhang Haoyu
2015-01-21 10:32 ` [Qemu-devel] " Zhang Haoyu
2015-01-21 10:39 ` Paolo Bonzini
2015-01-21 10:39 ` [Qemu-devel] " Paolo Bonzini
2015-01-22 23:29 ` Kashyap Chamarthy
2015-01-22 23:29 ` [Qemu-devel] " Kashyap Chamarthy
2015-01-26 1:07 ` Zhang Haoyu
2015-01-26 1:07 ` [Qemu-devel] " Zhang Haoyu
2015-01-26 9:29 ` Paolo Bonzini [this message]
2015-01-26 9:29 ` Paolo Bonzini
2015-01-26 11:13 ` Zhang Haoyu
2015-01-26 11:13 ` [Qemu-devel] " Zhang Haoyu
2015-01-26 11:28 ` Paolo Bonzini
2015-01-26 11:28 ` [Qemu-devel] " Paolo Bonzini
2015-01-26 12:25 ` Zhang Haoyu
2015-01-26 12:25 ` [Qemu-devel] " Zhang Haoyu
2015-01-23 11:09 ` Kashyap Chamarthy
2015-01-23 11:09 ` Kashyap Chamarthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54C608F4.4020905@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=kashyapc@fedoraproject.org \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=zhanghy@sangfor.com.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.