From: Parag Warudkar <kernel-stuff-Wuw85uim5zDR7s880joybQ@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Solaris 10 U2 installation failure
Date: Wed, 3 Jan 2007 21:02:44 +0000 (UTC) [thread overview]
Message-ID: <loom.20070103T215402-599@post.gmane.org> (raw)
In-Reply-To: 459B6B91.7070509@qumranet.com
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.
Thanks for your patience.
Parag
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-01-03 21:02 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 [this message]
[not found] ` <loom.20070103T215402-599-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-01-04 9: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=loom.20070103T215402-599@post.gmane.org \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.