From: Ben Sanders <ben.m.sanders+kvm@gmail.com>
To: kvm@vger.kernel.org
Subject: ESX on KVM requirements
Date: Mon, 8 Jun 2009 16:10:28 -0700 [thread overview]
Message-ID: <148df4af0906081610r321bfe54m61f776cd65620ff@mail.gmail.com> (raw)
I'm looking to reproduce the results of Alexander Graf earlier this
year when he said that he was able to get ESX to run a ReactOS guest
all on top of KVM. More information on that can be found here:
http://kerneltrap.org/mailarchive/linux-kvm/2009/1/5/4600354/thread
So far, I can only boot esx into service console mode, not regular
mode or debug mode without a kernel panic (in ESX). I've enabled
nesting, both in the module and in the kvm command on v86, using the
-cpu phenom option as well.
First question is about cpu type. I've been using some dual core AMD
cpu's with svm enabled, but I'm wondering if I actually need a phenom
cpu for all of this to work. I was under the impression that KVM/QEMU
could emulate a different CPU if the features didn't exist.
Second question is about the host OS. Are the nesting features in KVM
only supported in an x86 OS? or should x86_64 work as well? I've
tried each (in varying degrees), but if one implementation wouldn't
work (like emulating a phenom, an x86_64 processor on an x86 host OS),
I'd like to know so I can stay away from that. Also, I've been using
Ubuntu 8.10 and 9.04, but if there's some reason I should switch to a
different distribution, I'd like to know that as well.
Thanks for your help
next reply other threads:[~2009-06-08 23:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 23:10 Ben Sanders [this message]
2009-06-14 11:57 ` ESX on KVM requirements Avi Kivity
2009-06-14 15:56 ` Alexander Graf
[not found] ` <148df4af0906181819l7afefdc8tbbbc2769a17fc201@mail.gmail.com>
2009-06-19 8:30 ` Alexander Graf
2009-06-25 2:04 ` Ben Sanders
2009-06-26 8:38 ` Alexander Graf
2009-07-01 17:49 ` Ben Sanders
2009-07-28 21:24 ` Ben Sanders
2009-07-28 21:39 ` Alexander Graf
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=148df4af0906081610r321bfe54m61f776cd65620ff@mail.gmail.com \
--to=ben.m.sanders+kvm@gmail.com \
--cc=kvm@vger.kernel.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