From: Csaba Henk <csaba-ml@creo.hu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qcow2 images going corrupt
Date: Tue, 8 May 2007 16:15:28 +0000 (UTC) [thread overview]
Message-ID: <slrnf418de.td.csaba-ml@beastie.creo.hu> (raw)
Hi,
I'm running qemu 0.9.0 on a Linux host.
I'm using a qcow2 image. I run qemu in daemon mode. When I'm to finish my
session with the guest, I go to the monitor, do a "savevm whatever",
"commit all", "q".
What I see that the image becomes corrupt very often (qemu-img sees it
as a raw image). (I do the "commit all" only because I suffer and I don't
have any better idea in mind -- I guess it shouldn't have an effect on
the correctness of disk handling).
Any idea what's wrong? Or a fault-proof way of leaving qemu?
I can upload an example corrupt image if someone would like to analyze
it. 1.6G gzipped.
Csaba
next reply other threads:[~2007-05-08 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 16:15 Csaba Henk [this message]
2007-05-08 19:16 ` [Qemu-devel] qcow2 images going corrupt Thiemo Seufer
2007-05-09 12:47 ` [Qemu-devel] " Csaba Henk
[not found] ` <8B924B0C-001F-11DC-B4CF-0005025B95B5@hotmail.com>
2007-05-12 0:27 ` C.W. Betts
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=slrnf418de.td.csaba-ml@beastie.creo.hu \
--to=csaba-ml@creo.hu \
--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).