From: Kevin Wolf <kwolf@redhat.com>
To: sparsh mittal <sparsh0mittal@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] delvm causes disk corruption
Date: Mon, 28 Nov 2011 11:02:59 +0100 [thread overview]
Message-ID: <4ED35C53.1000806@redhat.com> (raw)
In-Reply-To: <CAF9M4Zj=svbKK1FQ5boCG_OuH9cXrPkbDXxKQRFhNdhkraubWQ@mail.gmail.com>
Am 25.11.2011 23:54, schrieb sparsh mittal:
> Hello
> I am using qemu-0.14, as a part of marss cycle-accurate simulator.
>
> When I use delvm for deleting a snapshot, it corrupts the whole image.
> After it, the image no longer boots.
>
> Is there a solution to it (a patch or a recent version that solves it).
> Please let me know, I would be grateful.
Please try if commit 35d7ace7 fixes it. The 0.15.0 release contains this
fix. (The fix is about loadvm, but you probably used that, too)
If it doesn't help, please describe in more details what you do between
image creation and the visible corruption. You can use 'qemu-img check'
in order to detect corruption as early as possible.
Kevin
prev parent reply other threads:[~2011-11-28 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 22:54 [Qemu-devel] delvm causes disk corruption sparsh mittal
2011-11-28 10:02 ` 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=4ED35C53.1000806@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sparsh0mittal@gmail.com \
/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).