From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Simon Gao <gao-g4dUTk+gKbW4mfPA/iJWtA@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: kvm-31 configure file bug
Date: Sun, 22 Jul 2007 10:56:06 +0300 [thread overview]
Message-ID: <46A30D96.5010606@qumranet.com> (raw)
In-Reply-To: <46A247DA.7060503-g4dUTk+gKbW4mfPA/iJWtA@public.gmane.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/
next prev parent reply other threads:[~2007-07-22 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 17:52 kvm-31 configure file bug Simon Gao
[not found] ` <46A247DA.7060503-g4dUTk+gKbW4mfPA/iJWtA@public.gmane.org>
2007-07-22 7:56 ` Avi Kivity [this message]
[not found] ` <46A30D96.5010606-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-22 20:19 ` Simon Gao
[not found] ` <46A3BBEF.2030400-g4dUTk+gKbW4mfPA/iJWtA@public.gmane.org>
2007-07-23 8:06 ` Avi Kivity
[not found] ` <46A46193.2060402-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-23 19:36 ` Simon Gao
[not found] ` <46A50352.7060003-g4dUTk+gKbW4mfPA/iJWtA@public.gmane.org>
2007-07-25 3:18 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46A30D96.5010606@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=gao-g4dUTk+gKbW4mfPA/iJWtA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox