From: Kevin Wolf <kwolf@redhat.com>
To: Kis Gellert <kis.gellert@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-img: Could not open '....qcow2': Could not read snapshots: File too large
Date: Mon, 7 Dec 2015 14:24:55 +0100 [thread overview]
Message-ID: <20151207132455.GC4191@noname.str.redhat.com> (raw)
In-Reply-To: <56654C56.7000600@gmail.com>
Am 07.12.2015 um 10:07 hat Kis Gellert geschrieben:
> Today one of my virtual machines failed starting.
> Previously , I might made a snapshot while VM running.
Never access disk images from more than one process at the same time
(except if all of them are read-only), it causes corruption. The proper
way of taking a snapshot of a running VM is the qemu monitor (i.e. in
your case through libvirt).
Your best bet for recovering at least some data is using either a
hex editor or tests/qemu-iotests/qcow2.py from the qemu source tree to
update the number of snapshots to 0 and then use qemu-img convert to
copy the data out.
Kevin
prev parent reply other threads:[~2015-12-07 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 9:07 [Qemu-devel] qemu-img: Could not open '....qcow2': Could not read snapshots: File too large Kis Gellert
2015-12-07 13:24 ` Kevin Wolf [this message]
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=20151207132455.GC4191@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=kis.gellert@gmail.com \
--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).