On Tue, Aug 18, 2009 at 11:43:38AM -0700, Jeremy Fitzhardinge wrote:
> Hi all,
> I know I've been a bit quiet lately; I've been working through a number
> of relatively small but time-consuming bugs while trying to stabilize
> The plan is:
> * make sure rebase/master is fairly functional and somewhat stable
> * rename rebase/* to xen/*
> * use it as the baseline dom0 and domU kernel in xen-unstable
> rebase/mster is currently up to 2.6.31-rc6, and I intend to track
> mainline fairly closely (probably no more closely than the -rc level).
> It also has some new features:
> * better acpi power management (ported from 2.6.18)
> * MCE (also from 2.6.18)
> * microcode updater (I forget whether that's in xen-tip/master)
> rebase/master is mostly working for me now, but I would be interested in
> getting some more testing (both success and bug reports welcomed). Once
> it seems to work, I'll do the rename and we'll work from there.
> What does this mean for you?
> * If you're itching to test something, test rebase/master
> * If you're doing some new development, base it on rebase/master (or
> if you don't have any strong dependencies on other Xen pieces,
> base it on mainline)
> o also, tell me if you're working on something, even if it
> isn't ready yet, so I know who's doing what
I just built and booted the latest 2.6.31-rc6 based tree on Xen 3.4.1.
I'm using 32bit PAE dom0 (and Xen) as usual.
Seems to work. I'll play some more with it tomorrow, install new guests etc.
> It would also useful to do regression testing on plain, unpatched,
> mainline, to make sure that any real bugfixes get merged promptly.
Same kernel also booted OK on baremetal without Xen.
Xen-devel mailing list