From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: 32-bit qemu + 64-bit kvm be a problem? Date: Wed, 10 Mar 2010 12:07:21 +0200 Message-ID: <4B976F59.2010200@redhat.com> References: <5d649bdb1003100159i7edb6b62u24bf0e934d2a94bf@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Neo Jia Return-path: Received: from mx1.redhat.com ([209.132.183.28]:49536 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751537Ab0CJKHY (ORCPT ); Wed, 10 Mar 2010 05:07:24 -0500 In-Reply-To: <5d649bdb1003100159i7edb6b62u24bf0e934d2a94bf@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: On 03/10/2010 11:59 AM, Neo Jia wrote: > hi, > > I have to keep a 32-bit qmeu user space to work with some legacy > library I have but still want to use 64-bit host Linux to explore > 64-bit advantage. > > So I am wondering if I can use a 32-bit qemu + 64-bit kvm-kmod > configuration. It's fully supported. It's less well tested that 64/64 or 32/32, so please report any bugs. > Will there be any limitation or drawback for this > configuration? I already get one that we can't assign guest physical > memory more than 2047 MB. > That is the only limitation AFAIK. -- error compiling committee.c: too many arguments to function