From: Sylvain Bauza <sylvain.bauza@digimind.com>
To: kvm@vger.kernel.org
Subject: Win2003 disk corruption with kvm-1.0. and virtio
Date: Tue, 12 Feb 2013 15:30:37 +0100 [thread overview]
Message-ID: <511A520D.4@digimind.com> (raw)
Hi,
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.
Thanks for your inputs,
-Sylvain Bauza
next reply other threads:[~2013-02-12 14:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 14:30 Sylvain Bauza [this message]
2013-02-13 7:21 ` Win2003 disk corruption with kvm-1.0. and virtio 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
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=511A520D.4@digimind.com \
--to=sylvain.bauza@digimind.com \
--cc=kvm@vger.kernel.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