public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Chris Stromblad <chris.stromblad-yx4YqRIVDag@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: How can I help?
Date: Sun, 25 Feb 2007 11:39:01 +0200	[thread overview]
Message-ID: <45E15935.6040500@qumranet.com> (raw)
In-Reply-To: <1172395971.4235.3.camel-ZMyy6FxXMJExPFx/aqb610B+6BGkLq7r@public.gmane.org>

Chris Stromblad wrote:
> Few years ago I did a fair bit of x86 programming, but with the more
> recent CPUs and all the new instructions, I'd probably be bit out of it.
> Then again, wouldn't hurt having a look at it... who knows, maybe in a
> few years I could actually do something ;)
>
>   

x86 experience definitely helps.  You might want to download the latest 
Intel and AMD documentation and check out the relevant chapters.  For 
Intel, that's chapters 20-25 in the software developer's manual, volume 3B.

Actually knowing all the instructions isn't that important; it's the 
general quirkiness of the arch that needs to be understood.


> The problem.
>
> Basically I get the problem immediately when attempting to boot from an
> ISO image (the installation step). The image is a UBUNTU x86_64
> installation disk. Pretty much instantly when I attempt to boot the
> window flashes by and in the original window I get the CPU reg dump with
> the exception 12.
>   

Ok.  That's definitely the real-mode emulation problem we have on 
Intel.  You might try installing using qemu, and disabling any boot 
loader splashscreens (I don't know the exact syntax required), and 
restarting under kvm.

-- 
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-02-25  9:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-24 17:51 How can I help? Chris Stromblad
     [not found] ` <1172339519.7845.8.camel-ZMyy6FxXMJExPFx/aqb610B+6BGkLq7r@public.gmane.org>
2007-02-25  5:25   ` Avi Kivity
     [not found]     ` <45E11DE2.1060909-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-25  9:32       ` Chris Stromblad
     [not found]         ` <1172395971.4235.3.camel-ZMyy6FxXMJExPFx/aqb610B+6BGkLq7r@public.gmane.org>
2007-02-25  9:39           ` Avi Kivity [this message]
     [not found]             ` <45E15935.6040500-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-25  9:59               ` Chris Stromblad
2007-02-27 13:38               ` Chris Stromblad
     [not found]                 ` <1172583521.4170.11.camel-ZMyy6FxXMJExPFx/aqb610B+6BGkLq7r@public.gmane.org>
2007-02-27 13:47                   ` 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=45E15935.6040500@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=chris.stromblad-yx4YqRIVDag@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