From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sylvain Bauza Subject: Re: Win2003 disk corruption with kvm-1.0. and virtio Date: Thu, 14 Feb 2013 09:23:37 +0100 Message-ID: <511C9F09.8080707@digimind.com> References: <511A520D.4@digimind.com> <201302130821.16157.hahn@univention.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: kvm@vger.kernel.org To: Philipp Hahn Return-path: Received: from mail-wg0-f42.google.com ([74.125.82.42]:38502 "EHLO mail-wg0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756328Ab3BNIXy (ORCPT ); Thu, 14 Feb 2013 03:23:54 -0500 Received: by mail-wg0-f42.google.com with SMTP id 12so4917286wgh.3 for ; Thu, 14 Feb 2013 00:23:53 -0800 (PST) In-Reply-To: <201302130821.16157.hahn@univention.de> Sender: kvm-owner@vger.kernel.org List-ID: Hi, Latest updates, I tried using : - cache=3Dwritethrough / kvm-1.0 : errors in qcow2 - cache=3Dnone/kvm-1.3 : no errors using 'qemu-img check', but=20 EventViewer is complaining I have to admit I'm lost. I cannot understand what is causing this=20 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=20 pc-1.3 -enable-kvm -m 2048 -smp 1,sockets=3D1,cores=3D1,threads=3D1 -na= me=20 instance-0000004f -uuid 26801166-aa03-4bbc-b062-da47168a664c=20 -nodefconfig -nodefaults -chardev=20 socket,id=3Dcharmonitor,path=3D/var/lib/libvirt/qemu/instance-0000004f.= monitor,server,nowait=20 -mon chardev=3Dcharmonitor,id=3Dmonitor,mode=3Dcontrol -rtc base=3Dutc=20 -no-shutdown -boot c -drive=20 file=3D/var/lib/nova/instances/instance-0000004f/disk,if=3Dnone,id=3Ddr= ive-virtio-disk0,format=3Dqcow2,cache=3Dnone=20 -device=20 virtio-blk-pci,bus=3Dpci.0,addr=3D0x4,drive=3Ddrive-virtio-disk0,id=3Dv= irtio-disk0=20 -netdev tap,fd=3D21,id=3Dhostnet0,vhost=3Don,vhostfd=3D22 -device=20 virtio-net-pci,netdev=3Dhostnet0,id=3Dnet0,mac=3Dfa:16:3e:7a:a1:61,bus=3D= pci.0,addr=3D0x3=20 -chardev=20 file,id=3Dcharserial0,path=3D/var/lib/nova/instances/instance-0000004f/= console.log=20 -device isa-serial,chardev=3Dcharserial0,id=3Dserial0 -chardev=20 pty,id=3Dcharserial1 -device isa-serial,chardev=3Dcharserial1,id=3Dseri= al1=20 -usb -device usb-tablet,id=3Dinput0 -vnc 192.168.1.155:2 -k fr -vga cir= rus=20 -device virtio-balloon-pci,id=3Dballoon0,bus=3Dpci.0,addr=3D0x5 Last try, I googled and found that virtio network can be buggy. I will=20 try to switch back to another driver and see. By the way, all these Windows instances do have virtio SCSI drivers up=20 to date. Le 13/02/2013 08:21, Philipp Hahn a =E9crit : > 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=3Dnone > The default answer is to update your qemu-kvm version: 1.0 is very ol= d, 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