Re: kvm-31 configure file bug

[Simon Gao <gao-g4dUTk+gKbW4mfPA/iJWtA@public.gmane.org>]

Avi Kivity wrote:
> 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
>> , 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.
>
>
So from kvm-31 and on, qemu command will become qemu-system-x86_64 no
matter host system is 32bit or 64bit?  So it's possible to compile 64bit
kvm qemu with only 32bit libraries?

Simon


-------------------------------------------------------------------------
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/