Win2003 disk corruption with kvm-1.0. and virtio

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux