From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Ben Collins <ben.collins-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Real mode emulation
Date: Fri, 12 Jan 2007 18:46:21 +0200 [thread overview]
Message-ID: <45A7BB5D.30501@qumranet.com> (raw)
In-Reply-To: <1168613687.5332.83.camel@gullible>
Ben Collins wrote:
> Being able to boot Ubuntu's liveCD from KVM is fairly important to me at
> this point.
>
> We use a bootsplash, and I don't think that's going to change.
Nor should you -- that's a kvm bug, and guests need not work around it.
> We do
> have alternate install CD's, but they don't boot to a live session,
> where people can test things (plus virtualization technologies like KVM
> provide us with a quick and dirty test bed for liveCD boot/install).
>
> What all is involved in doing the x86_emulate.c changes for real mode?
> Some docs, and maybe a bit of explanation on where these changes need to
> be made.
>
>
There's some details in
http://www.mail-archive.com/kvm-devel%40lists.sourceforge.net/msg00626.html
In addition to the x86_emulate.c changes listed there, you'd need to
change vmx_vcpu_run() to call the emulator in guest real mode, instead
of using VT.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2007-01-12 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 14:54 Real mode emulation Ben Collins
2007-01-12 16:46 ` 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=45A7BB5D.30501@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=ben.collins-GeWIH/nMZzLQT0dZR+AlfA@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