WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Re: [Xen-devel] State of Xen in upstream Linux

To: Alexey Eremenko <al4321@xxxxxxxxx>
Subject: Re: [Xen-users] Re: [Xen-devel] State of Xen in upstream Linux
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Thu, 31 Jul 2008 11:28:37 -0700
Cc: Virtualization Mailing List <virtualization@xxxxxxxxxxxxxx>, Grant McWilliams <grantmasterflash@xxxxxxxxx>, "Daniel P. Berrange" <berrange@xxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 31 Jul 2008 11:29:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7fac565a0807311119p55e534f1hc15005aea46671a2@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <48910C99.10606@xxxxxxxx> <20080731090845.GH23888@xxxxxxxxxx> <ed123fa30807311054p4965f43bod78dafa6626c9c2d@xxxxxxxxxxxxxx> <4891FFBA.1020702@xxxxxxxx> <7fac565a0807311119p55e534f1hc15005aea46671a2@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (X11/20080501)
Alexey Eremenko wrote:
> Jeremy: Mr. Grant speaking about the future where Linux (2.6.28?)
> mainline kernel will support Xen Dom0, not kernel 2.6.27, which only
> improves Xen DomU.
>
> And I agree with Grant, that if Linux mainline will have Dom0
> included, that may cause problems for all kinds of drivers.

The intention is that a single kernel will be equally functional in all
modes of operation.  If the kernel has dom0 capabilities, then they will
only come into play when actually running under Xen; when booting
natively, they will have no effect on anything else.  Naturally, running
under Xen is likely incompatible with any other in-kernel virtualization
system, so we need to make sure that they don't get in the way.  That's
easy to arrange for kvm, but I'm not sure about VirtualBox as it is
out-of-tree (though full source is available, right?).

    J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel