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/
Home Products Support Community News


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 13:07:26 -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 13:08:08 -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=VNtA8xfZiMVkZq+9IzGUpiNiRDkGvw/0JtQUWLfZmSA=; b=xWCW6L/pEJLtZhQ+eTqwP6X42l/5+BJ1qFLgHpKV0p8RZuuqhR3l+Xx1DC9Ccsxa1J D+aeQBTBTV/Dhfx9/rW7AMoRNAI6i3gn7x2s8tcMc3+1Eb1qmPChn4zTJjfpB9pruKUB LG0TpKGKIEm+Q3XNlgRNoa5QoDVWvh9wCATMk=
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=SvQRYVte1/22Z8BKCQ+67hom1xy5dH7srIDeV/9o1Zk5eWajwiaz3uIKyMA0NZMjJ2 I/WFz/4JxSHsvk+51DbGkZtwsPPWllFbI5u3HRnp9VZbbwUjdjFiJHZTGIxAKK2Gw7z1 OnotkVeT52PUmKP46k0Sj3meKa3heJe97K+oI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48920B4F.7010608@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> <ed123fa30807311148q6460d2d8nb012f1b4edeb042f@xxxxxxxxxxxxxx> <48920B4F.7010608@xxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Jul 31, 2008 at 11:58 AM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
Grant McWilliams wrote:
> 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.

Yes, that sounds like an inherently unstable configuration.  I don't
know anything about how VBox operates internally, but whatever pagetable
management scheme they're using will quite likely not work under Xen
without a lot of care.  The best we can do in that case is try to make
sure that VBox doesn't attempt to come up.

If they don't rely on VT/SVM, then it may work from within a Xen hvm
domain, but I don't know what benefit that would have.  What were you
trying to achieve by running VBox in dom0?


I wasn't really trying to run VBox in the dom0. I'd been running the Xen kernel so long that I'd forgotten which
kernel I was on. Like I said when you start VMware the guest OS just doesn't run which gives you a second
to ponder why. VBox uses VT/SVM if you check a box in the config. It was not checked when it
crashed the server.

Depending on the application I use VBox or Xen for virtualization projects. VBox acts as an HVM most of the time
so it's great for those times I'm virtualizing a product that I have no control over. Xen is best for environments
that I do have control over.

Grant McWilliams
Xen-users mailing list