Re: Win2003 disk corruption with kvm-1.0. and virtio

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

 



[Please stop top-posting.  Thank you]

13.02.2013 20:03, weber@xxxxxxxxxxxxxxxxx wrote:

there are known problems, WHEN  I/O "native" and cache=writethrough.

On I/O "native" put cache to "none" otherwise your data can get broken.
Check Redhat Pages for that.

Which problem is that?

And what is "I/O native" ?  Maybe you mean "aio", not "I/O" ?

If the talk is about aio=native, that mode does not work for regular
files, it gets "downgraded" to aio=threads automatically.  So there
should be nothing to change already.

Please elaborate.

/mjt

--
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