All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark McLoughlin <markmc@redhat.com>
To: Gilles PIETRI <contact+dev@gilouweb.com>
Cc: kvm@vger.kernel.org
Subject: Re: KVM-86 not exposing 64 bits CPU anymore, NICE
Date: Thu, 04 Jun 2009 10:27:48 +0100	[thread overview]
Message-ID: <1244107668.2824.5.camel@blaa> (raw)
In-Reply-To: <4A2775C6.9030503@gilouweb.com>

On Thu, 2009-06-04 at 09:20 +0200, Gilles PIETRI wrote:

> I'm quite pissed off. I just upgraded to kvm-86 on a host that has 
> worked nicely on kvm-78 for quite some time. But since I was fearing the 
> qcow2 corruption issues, I wanted to upgrade kvm-86. After testing the 
> performance, I decided to switch. How stupid that was. That was really 
> putting too much trust in KVM.

Jim has already responded with details on the first for the particular
issue, but speaking more generally ...

The kvm-XX releases are snapshots of the development tree. They do not
go to through the kind of stabilisation cycle you would expect from a
new kernel release, for example.

If you want a KVM version you can trust, use the latest qemu-kvm-0.x.y
release with the stock version of kvm.ko that comes with your kernel or,
if you need particular new features, the latest kvm-kmod-2.6.z release.

Cheers,
Mark.


      parent reply	other threads:[~2009-06-04  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04  7:20 KVM-86 not exposing 64 bits CPU anymore, NICE Gilles PIETRI
2009-06-04  7:46 ` Jim Paris
2009-06-04  8:02   ` Gilles PIETRI
2009-06-04  8:00 ` Alexey Eromenko
2009-06-04  9:27 ` Mark McLoughlin [this message]

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=1244107668.2824.5.camel@blaa \
    --to=markmc@redhat.com \
    --cc=contact+dev@gilouweb.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.