From: Kevin Wolf <kwolf@suse.de>
To: me@jasonmartens.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Add Intel VT support to QEMU?
Date: Mon, 19 Jan 2009 10:13:07 +0100 [thread overview]
Message-ID: <49744423.4050102@suse.de> (raw)
In-Reply-To: <49737609.8000101@jasonmartens.com>
Jason Martens schrieb:
> Hello Everyone
> I'm a part of a school group, and we are looking at adding Intel VT
> support to QEMU for a class project. We would be implementing support
> for VT guests, so that other VMMs that rely on VT could be run/debugged
> using QEMU. We are not familiar with QEMU code (yet!), so we are
> looking for some feedback from all of you experts.
>
> 1. Has this been attempted before, or is there any existing code for
> this? I saw some posts about a year ago that perhaps someone started on
> it, but nothing after that.
I've started to implement it once, but haven't come very far. The very
basic instructions are implemented, but that's it. IIRC you could load
the KVM modules but it wouldn't run anything.
If you like I can try to rebase my code on the current SVN version and
send you a patch series.
> 2. What would be required to implement this? Any suggestions on where
> to start looking would be appreciated. Obviously, the Intel VT docs are
> going to be necessary. Are there other things that you recommend we
> look at before we start?
What I used was only the Intel docs and partly the KVM sources.
Kevin
next prev parent reply other threads:[~2009-01-19 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 18:33 [Qemu-devel] Add Intel VT support to QEMU? Jason Martens
2009-01-18 22:22 ` Jamie Lokier
2009-01-18 22:46 ` Alexey Eremenko
2009-01-18 23:28 ` Alexander Graf
2009-01-19 9:13 ` Kevin Wolf [this message]
2009-01-22 15:48 ` Jason Martens
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=49744423.4050102@suse.de \
--to=kwolf@suse.de \
--cc=me@jasonmartens.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).