From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gilles PIETRI Subject: Re: KVM-86 not exposing 64 bits CPU anymore, NICE Date: Thu, 04 Jun 2009 10:02:35 +0200 Message-ID: <4A277F9B.8040207@gilouweb.com> References: <4A2775C6.9030503@gilouweb.com> <20090604074627.GA13140@psychosis.jim.sh> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: kvm@vger.kernel.org To: Jim Paris Return-path: Received: from smtp1-g21.free.fr ([212.27.42.1]:53455 "EHLO smtp1-g21.free.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757390AbZFDICm (ORCPT ); Thu, 4 Jun 2009 04:02:42 -0400 In-Reply-To: <20090604074627.GA13140@psychosis.jim.sh> Sender: kvm-owner@vger.kernel.org List-ID: Le 04/06/2009 09:46, Jim Paris a =E9crit : > Gilles PIETRI wrote: >> Hi, >> >> I'm quite pissed off. I just upgraded to kvm-86 on a host that has =20 >> worked nicely on kvm-78 for quite some time. But since I was fearing= the =20 >> qcow2 corruption issues, I wanted to upgrade kvm-86. After testing t= he =20 >> performance, I decided to switch. How stupid that was. That was real= ly =20 >> putting too much trust in KVM. >> >> Now I can't have 64 bits CPUs on my guests. >> My host is running a 2.6.27.7 kernel, and is x86_64 enabled. >> Until the upgrade, guests were running x86_64 fine. >> Now, it says long mode can't be used or something like that, and I c= an =20 >> only have 32 bits guests. >=20 > Please see > http://www.mail-archive.com/kvm@vger.kernel.org/msg15757.html > http://www.mail-archive.com/kvm@vger.kernel.org/msg15769.html >=20 > -jim Gonna check that, thanks a lot, this didn't get on my radar.. Regards, Gilles