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: Wed, 13 Feb 2013 10:56:53 +0100 [thread overview]
Message-ID: <511B6365.9050605@digimind.com> (raw)
In-Reply-To: <201302130821.16157.hahn@univention.de>
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
next prev parent reply other threads:[~2013-02-13 9:57 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 [this message]
2013-02-13 16:03 ` weber
2013-02-14 5:27 ` Michael Tokarev
2013-02-14 8:23 ` Sylvain Bauza
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=511B6365.9050605@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