From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263747AbTJCNOg (ORCPT ); Fri, 3 Oct 2003 09:14:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263748AbTJCNOg (ORCPT ); Fri, 3 Oct 2003 09:14:36 -0400 Received: from www.wireboard.com ([216.151.155.101]:18137 "EHLO varsoon.wireboard.com") by vger.kernel.org with ESMTP id S263747AbTJCNOf (ORCPT ); Fri, 3 Oct 2003 09:14:35 -0400 To: John Bradford Cc: Keir Fraser , karim@opersys.com, linux-kernel@vger.kernel.org Subject: Re: [Xen-devel] Re: [ANNOUNCE] Xen high-performance x86 virtualization References: <200310031047.h93AlSWB000506@81-2-122-30.bradfords.org.uk> From: Doug McNaught Date: 03 Oct 2003 09:14:08 -0400 In-Reply-To: John Bradford's message of "Fri, 3 Oct 2003 11:47:28 +0100" Message-ID: User-Agent: Gnus/5.0806 (Gnus v5.8.6) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org John Bradford writes: > I think we might be talking about different things - what I meant was > if you run a kernel compiled to support Xen on X86 natively without > Xen, is there a big performance penalty, not if you run a single VM in > Xen? My understanding from reading the paper is that you can't do this--'x86-xen' is a separate "architecture" and won't boot on the bare metal. -Doug