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-devel

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

To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Subject: Re: [Xen-users] Re: [Xen-devel] State of Xen in upstream Linux
From: "Grant McWilliams" <grantmasterflash@xxxxxxxxx>
Date: Thu, 31 Jul 2008 11:48:22 -0700
Cc: Alexey Eremenko <al4321@xxxxxxxxx>, Virtualization Mailing List <virtualization@xxxxxxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Daniel P. Berrange" <berrange@xxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 31 Jul 2008 11:49:02 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=BXt1fJVF3dFYu8MJ0JsBbjwIqmkivlMr/terzBKohkc=; b=AqXyc+Y7EyY5xB3rvKLIx76I988B+jdqoupdtQU2o6qQosvSTkNqRbB7ZU6BxL+pez vbSqkdCk2gEUZguQam9l9VmNlUW+w6RLNu10CsHDtYCiIBheFS3p5GIlorxv5d4PIY7J 3eGbaL9DBykV09yQ0fhbRFD4m6ZTQZk0fzs0k=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=HinIC+/pVBKroXqzEYIO3FCRYCiZczPGQ1OS2H8g6uUEnk8QWw1YiP24L2OfG5074V +LOPYBQYojJ+LDAIPDE5PnmihRGZOHOIo5+JcRaGLRDDOxYS3YMwrRhKC3MxTHGuN8p8 6+KP2/krrp3FwuByHexHgMCHsgTwtfMNuouKA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48920455.40204@xxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <48910C99.10606@xxxxxxxx> <20080731090845.GH23888@xxxxxxxxxx> <ed123fa30807311054p4965f43bod78dafa6626c9c2d@xxxxxxxxxxxxxx> <4891FFBA.1020702@xxxxxxxx> <7fac565a0807311119p55e534f1hc15005aea46671a2@xxxxxxxxxxxxxx> <48920455.40204@xxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

On Thu, Jul 31, 2008 at 11:28 AM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
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

Vbox OSE has full source available. I was working on a contract for a corporation and was in the stage
of deciding which virtualization platform to run and installed Vbox in a Xen system (running Xen). The installer
loaded the vbox driver (As well as set it up to load automatically) and sent the server into a continuous reboot. Unfortunately this was
in a Datacenter that I had no physical access to. The Vbox developers jumped all over me when I suggested that it was a bug.
When running Xen the VMware interface will come up and the driver will load but the VMs just don't start. It seems like
that would be a much better situation than causing the entire machine to crash. Seems like a Vbox problem. It was run in Dom0.

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