From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: kvm-31 configure file bug Date: Sun, 22 Jul 2007 10:56:06 +0300 Message-ID: <46A30D96.5010606@qumranet.com> References: <46A247DA.7060503@schrodinger.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: Simon Gao Return-path: In-Reply-To: <46A247DA.7060503-g4dUTk+gKbW4mfPA/iJWtA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Simon Gao wrote: > Hi, > > I found there is a bug with configure file shipped with kvm-31. Here is > the part of configure file: > > =============================== > target_cpu() { > if [[ $(uname -m) = i?86 ]]; then > echo x86_64 > else > uname -m > fi > } > =============================== > > !?86 will match i386, i586 and i686. On my machine, "uname -m" returns > i686, which is obviously a 32bit kernel. Assigning to x86_64 breaks kvm > and installs qemu-system-x86_64, instead of qemu. > > That's by design. We compile qemu to support a 64-bit target so that live migration works between 32-bit and 64-bit hosts. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/