xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "kevin.zhang@octlink.com" <kevin.zhang@octlink.com>
To: xen-devel <xen-devel@lists.xen.org>
Subject: Live Snapshot problem: Xen 4.4+ with qcow2 disk
Date: Fri, 18 Jul 2014 18:26:33 +0800	[thread overview]
Message-ID: <20140718182632758532107@octlink.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 826 bytes --]

Hi all,

    Today, I tried to test whether Live Snapshot schema can be adopted to qemu-xen with qcow2 disk image as
what we do with qemu-xen-traditional using vhd disk image.
    My live snapshot procedure is as follow:
( my vm1 is currently running with qcow2 disk file 1.qcow2 ) 
 1. xl pause vm1
 2. mv 1.qcow2 snap.qcow2
 3. qemu-img create  -b snap.qcow2 -f qcow2 1.qcow2
 4. xl unpause vm1

   However, as I unpaused vm1, the write operation still went to snap.qcow2 instead of  the newly created snapshot file 1.qcow2.
I remember that xen 4.0 also had similar problem if we did vhd live snapshot, and the problem was fixed in xen 4.1.
   My question is : whether the failure of making live qcow2 snapshot is a known bug, or  whether I've missed some key operations to make it work.





Best Regards

[-- Attachment #1.2: Type: text/html, Size: 5019 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

             reply	other threads:[~2014-07-18 10:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 10:26 kevin.zhang [this message]
2014-07-18 10:48 ` Live Snapshot problem: Xen 4.4+ with qcow2 disk Ian Campbell
     [not found] <398fa5bc.15f8b.14749fb03bf.Coremail.zhangpei210@163.com>
2014-07-18 15:05 ` kevin.zhang
2014-07-18 15:25   ` Ian Campbell

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=20140718182632758532107@octlink.com \
    --to=kevin.zhang@octlink.com \
    --cc=xen-devel@lists.xen.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).