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

[Jeremy Fitzhardinge <jeremy@goop.org>]

Grant McWilliams wrote:
> 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.

Yes.  It looks to me like the VBox kernel code is constructing its own
pagetable entries without using the normal kernel API to do so, and is
therefore not taking the pfn to mfn translation that must be done when
constructing pagetable entries.  The upshot is that it will use invalid
pagetables which are bound to crash the dom0 kernel.

There are two possible fixes: 1) make VBox Xen (or pvops) aware by
making sure it always uses the normal kernel APIs for constructing
pagetables, 2a) refuse to build with CONFIG_PARAVIRT enables, or 2b)
detect at runtime we're running on a non-native platform and refuse to
run.  2[ab] probably being easiest to implement.

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

Yes, I use kvm in a similar way.

    J