From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark McLoughlin Subject: Re: KVM-86 not exposing 64 bits CPU anymore, NICE Date: Thu, 04 Jun 2009 10:27:48 +0100 Message-ID: <1244107668.2824.5.camel@blaa> References: <4A2775C6.9030503@gilouweb.com> Reply-To: Mark McLoughlin Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Gilles PIETRI Return-path: Received: from mx2.redhat.com ([66.187.237.31]:43560 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754287AbZFDJlf (ORCPT ); Thu, 4 Jun 2009 05:41:35 -0400 In-Reply-To: <4A2775C6.9030503@gilouweb.com> Sender: kvm-owner@vger.kernel.org List-ID: 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.