From: Sylvain Bauza <sylvain.bauza@digimind.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Win2003 disk corruption with kvm-1.0. and virtio
Date: Wed, 13 Feb 2013 10:53:14 +0100 [thread overview]
Message-ID: <511B628A.3040005@digimind.com> (raw)
In-Reply-To: <20130213090317.GA12049@stefanha-thinkpad.redhat.com>
Hi Stefan,
As per documentation, Nova (Openstack Compute layer) is doing a
'qemu-img convert -s' against a running instance.
http://docs.openstack.org/trunk/openstack-compute/admin/content/creating-images-from-running-instances.html
Do you think it could be our root cause ?
Btw, I tested cache=writethrough and I observed image corruption after
some time ('qemu-img check' returns errors)
Thanks for your input,
-Sylvain
Le 13/02/2013 10:03, Stefan Hajnoczi a écrit :
> On Tue, Feb 12, 2013 at 03:30:37PM +0100, Sylvain Bauza wrote:
>> We currently run Openstack Essex hosts with KVM-1.0 (Ubuntu 12.04)
>> instances with qcow2,virtio,cache=none
>>
>> For Linux VMs, no trouble at all but we do observe filesystem
>> corruption and inconsistency (missing DLLs, CHKDSK asked by
>> EventViewer, failure at reboot) with some of our Windows 2003 SP2
>> 64b images.
>>
>> At first boot, stress tests (CrystalDiskMark 3.0.2 and intensive
>> CHKDSK) don't show up problems. It is only appearing 6 or 12h later.
>>
>> Do you have any idea on how to prevent it ? Is cache=writethrough an
>> acceptable solution ? We don't want to leave qcow2 image format as
>> it does allow to do live snapshots et al.
> How are you taking live snapshots? qemu-img should not be used on a
> disk image that is currently open by a running guest, it may lead to
> corruption.
>
> Stefan
next prev parent reply other threads:[~2013-02-13 9:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 14:30 Win2003 disk corruption with kvm-1.0. and virtio Sylvain Bauza
2013-02-13 7:21 ` Philipp Hahn
2013-02-13 9:56 ` Sylvain Bauza
2013-02-13 16:03 ` weber
2013-02-14 5:27 ` Michael Tokarev
2013-02-14 8:23 ` Sylvain Bauza
2013-02-13 9:03 ` Stefan Hajnoczi
2013-02-13 9:53 ` Sylvain Bauza [this message]
2013-02-14 8:15 ` Stefan Hajnoczi
2013-02-14 10:11 ` Sylvain Bauza
2013-03-12 15:48 ` Sylvain Bauza
2013-03-12 21:10 ` Jorge Armando Medina
2013-02-14 8:17 ` Stefan Hajnoczi
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=511B628A.3040005@digimind.com \
--to=sylvain.bauza@digimind.com \
--cc=kvm@vger.kernel.org \
--cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.