From mboxrd@z Thu Jan 1 00:00:00 1970 From: "David S. Ahern" Subject: Re: KVM and the OOM-Killer Date: Thu, 13 May 2010 12:55:59 -0600 Message-ID: <4BEC4B3F.2000109@cisco.com> References: <4BEBEE8F.9050508@jrcs.co.uk> <4BEBF2F8.7020507@redhat.com> <4BEC0121.2020700@jrcs.co.uk> <4BEC044D.4070004@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Avi Kivity , kvm@vger.kernel.org To: James Stevens Return-path: Received: from sj-iport-6.cisco.com ([171.71.176.117]:6220 "EHLO sj-iport-6.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757281Ab0EMS4D (ORCPT ); Thu, 13 May 2010 14:56:03 -0400 In-Reply-To: <4BEC044D.4070004@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: >> Not sure I like the idea of running a 64bit user space kernel on top >> of a 32bit host, prefer to re-install. >> >> Can I just replace my kernel with a 64bit one, or do I have to >> re-install the host O/S ? > > You can run 32-bit userspace with a 64-bit kernel, or reinstall, > whichever you prefer. > > I once upgraded a 32-bit Fedora install to 64-bit, but that takes some > tinkering. > You can just install a 64-bit kernel. For rpm based systems you have to "unpack" the rpm using rpm2cpio. The modules.dep file cannot be updated -- need to generate that elsewhere -- and mkinitrd needs to be modified to not try to strip modules (s,strip,true,). That's all I had to do to plop a 64-bit kernel onto a 32-bit install. David