From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: ESX on KVM requirements Date: Sun, 14 Jun 2009 14:57:55 +0300 Message-ID: <4A34E5C3.9040305@redhat.com> References: <148df4af0906081610r321bfe54m61f776cd65620ff@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, Alexander Graf To: Ben Sanders Return-path: Received: from mx2.redhat.com ([66.187.237.31]:35119 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751153AbZFNL6S (ORCPT ); Sun, 14 Jun 2009 07:58:18 -0400 In-Reply-To: <148df4af0906081610r321bfe54m61f776cd65620ff@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: Ben Sanders wrote: > 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. > > No, kvm (mostly) doesn't emulate cpu features. I don't know why -cpu phenom is required. Copying Alex. > 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. > x86 generally means i386 and x86_64. Both should work, and x86_64 is recommended. -- error compiling committee.c: too many arguments to function