public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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: Wed, 25 Jul 2007 06:18:59 +0300	[thread overview]
Message-ID: <46A6C123.6060403@qumranet.com> (raw)
In-Reply-To: <46A50352.7060003-g4dUTk+gKbW4mfPA/iJWtA@public.gmane.org>

Simon Gao wrote:
> Avi Kivity wrote:
>   
>> Simon Gao wrote:
>>     
>>> 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?
>>>
>>>   
>>>       
>> Yes and yes.  That's even more true for upstream qemu as well -- you
>> can run a 64-bit guest on a non-64-bit capable cpu.
>>
>>     
> I still had to change "x86_64" to "i386" in configure file. If I don't,
> then guest os will hang after initial boot image splash. This happened
> to kvm-31, kvm-32, kvm-33. The guest OSes worked fine with kvm-28.
>
> Is there some parameter I should pass to make? or when I start guest OS
> using qemu-system_x86_64 under 32bit Linux?
>
>   

It should just work.  Is there anything in dmesg when the guest hangs? 
What guest is that?

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


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

      parent reply	other threads:[~2007-07-25  3:18 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
     [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 [this message]

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=46A6C123.6060403@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