public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Parag Warudkar <kernel-stuff-Wuw85uim5zDR7s880joybQ@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Solaris 10 U2 installation failure
Date: Thu, 04 Jan 2007 11:18:35 +0200	[thread overview]
Message-ID: <459CC66B.1010904@qumranet.com> (raw)
In-Reply-To: <loom.20070103T215402-599-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>

Parag Warudkar wrote:
> Avi Kivity <avi@...> writes:
>
>
>   
>> 32-bin kvm userspace can run a 64-bit guest, if you're using a 64-bit os 
>> kernel, hence the 64-bit registers. Just ignore the 64-bit parts.
>>
>>     
>
> Didn't understand. Allow me to clarify a bit -
>
> I am running a 32-bit Host OS (Linux i386) on a purely 32-bit CPU (Core Duo). 
> Solaris installation will first check if the processor is 64-bit capable and
> only then install a 64-bit kernel. In that case, when Solaris asks KVM if the
> CPU is 64-bit, is KVM lying to it even though the host CPU on which it is
> running is NOT 64-bit capable and then emulating all AMD64 instructions without
> any help from the host CPU? That sounds more confusing!
>
> Even if it does something like that is there a way to tell KVM not to pretend
> like it is running a 64-bit CPU? I don't want to run Solaris in 64-bit mode as I
> am running on 32-bit host with just 512Mb of total memory.
>   

No, kvm doesn't pretend to be a 64-bit cpu when it isn't.

There are three cases wrt host bitness. Two are straightforward:

32-bit host: kvm pretends to be a 32-bit cpu whether the cpu supports 
long mode or not.
64-bit host: the cpu supports long mode, and we pass that on to the guest.

There is a third case: 64-bit host kernel but 32-bit qemu.  In that 
case, we also support 64-bit guests.

Because of that last case, 32-bit qemu is compiled with support for 
64-bit guests.  That means that even in a pure 32-bit environment, qemu 
has 64-bit registers (even though it can't make use of them).

If you're running a 32-bit environment, simply ignore r8-r15 and the 
high 32 bits of other registers.  That's what kvm.ko does :)

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

      parent reply	other threads:[~2007-01-04  9:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-30 19:19 Solaris 10 U2 installation failure Parag Warudkar
     [not found] ` <loom.20061230T201339-43-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2006-12-31 17:52   ` Avi Kivity
2006-12-31 22:06     ` Parag Warudkar
2006-12-31 22:26       ` Parag Warudkar
     [not found]         ` <loom.20061231T232415-117-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-01-01  8:18           ` Avi Kivity
2007-01-01 15:34             ` Parag Warudkar
     [not found]               ` <loom.20070101T163114-834-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-01-01 15:39                 ` Avi Kivity
     [not found]                   ` <45992B33.8070204-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-02 23:41                     ` digital tech support
2007-01-03  2:02             ` Parag Warudkar
     [not found]               ` <loom.20070103T030116-115-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-01-03  8:38                 ` Avi Kivity
2007-01-03 21:02                   ` Parag Warudkar
     [not found]                     ` <loom.20070103T215402-599-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-01-04  9: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=459CC66B.1010904@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kernel-stuff-Wuw85uim5zDR7s880joybQ@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