From: Sylvain Bauza <sylvain.bauza@digimind.com>
To: Philipp Hahn <hahn@univention.de>
Cc: kvm@vger.kernel.org
Subject: Re: Win2003 disk corruption with kvm-1.0. and virtio
Date: Thu, 14 Feb 2013 09:23:37 +0100 [thread overview]
Message-ID: <511C9F09.8080707@digimind.com> (raw)
In-Reply-To: <201302130821.16157.hahn@univention.de>
Hi,
Latest updates, I tried using :
- cache=writethrough / kvm-1.0 : errors in qcow2
- cache=none/kvm-1.3 : no errors using 'qemu-img check', but
EventViewer is complaining
I have to admit I'm lost. I cannot understand what is causing this
corruption, only appearing on some Windows instances...
Please find below the executable path :
117 13781 1 4 Feb13 ? 00:41:43 /usr/bin/kvm -S -M
pc-1.3 -enable-kvm -m 2048 -smp 1,sockets=1,cores=1,threads=1 -name
instance-0000004f -uuid 26801166-aa03-4bbc-b062-da47168a664c
-nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-0000004f.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc
-no-shutdown -boot c -drive
file=/var/lib/nova/instances/instance-0000004f/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none
-device
virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0
-netdev tap,fd=21,id=hostnet0,vhost=on,vhostfd=22 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:7a:a1:61,bus=pci.0,addr=0x3
-chardev
file,id=charserial0,path=/var/lib/nova/instances/instance-0000004f/console.log
-device isa-serial,chardev=charserial0,id=serial0 -chardev
pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1
-usb -device usb-tablet,id=input0 -vnc 192.168.1.155:2 -k fr -vga cirrus
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
Last try, I googled and found that virtio network can be buggy. I will
try to switch back to another driver and see.
By the way, all these Windows instances do have virtio SCSI drivers up
to date.
Le 13/02/2013 08:21, Philipp Hahn a écrit :
> Hello,
>
> On Tuesday 12 February 2013 15:30:37 Sylvain Bauza wrote:
>> We currently run Openstack Essex hosts with KVM-1.0 (Ubuntu 12.04)
>> instances with qcow2,virtio,cache=none
> The default answer is to update your qemu-kvm version: 1.0 is very old, qemu-
> kvm is fully merged into upstream qemu, which is currently preparing its 1.4
> release.
> There have been many fixes to qemi and the qcow2 handling: I know of at least
> one serious problem not fixed up to qemu-1.1.
>
> Sincerely
> Philipp
next prev parent reply other threads:[~2013-02-14 8:23 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 [this message]
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=511C9F09.8080707@digimind.com \
--to=sylvain.bauza@digimind.com \
--cc=hahn@univention.de \
--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