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

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

 




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.

marko

Am 2013-02-13 10:56, schrieb Sylvain Bauza:
Hi Philipp,

Indeed. Qemu-kvm.1.0 is pretty old but this version is the stable one
for Ubuntu Precise (12.04 LTS).
No backport is available for later versions, I need to install by hand.

Do you know if qemu-1.3 (with KVM support) is fully compatible with
qemu-kvm.1.0 ?
As I'm relying on Openstack Nova for upper hypervisor layer, it needs
to be 100% matching.

Thanks,
-Sylvain


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

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

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