From: Fam Zheng <famz@redhat.com>
To: lampahome <pahome.chen@mirlab.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Can I convert backing file to internal snapshot?
Date: Wed, 12 Sep 2018 15:44:02 +0800 [thread overview]
Message-ID: <20180912074402.GB11164@lemon.usersys.redhat.com> (raw)
In-Reply-To: <CAB3eZfvRJRR1k0X1MQivPMcLRNZR07yv1ZxBiDAkF3qOryK0UQ@mail.gmail.com>
On Wed, 09/12 15:35, lampahome wrote:
> I have two qcow2 A & B, and A is backing file of B.
>
> Can I convert both A&B to one image and containing data of both?
>
> ex:
> one new image will contain data of A and B. When I check it by qemu-img
> info, I can see one snapshot in the new image.
I believe it's possible to create an internal snapshot in A and then qemu-img
commit B to A. From here, the active content is B, and the snapshot is A.
Fam
next prev parent reply other threads:[~2018-09-12 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 7:35 [Qemu-devel] Can I convert backing file to internal snapshot? lampahome
2018-09-12 7:44 ` Fam Zheng [this message]
2018-09-14 4:23 ` lampahome
2018-09-14 6:05 ` Fam Zheng
2018-09-14 14:52 ` Eric Blake
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=20180912074402.GB11164@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=pahome.chen@mirlab.org \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).