On Wednesday 23 January 2008 05:26:26 Curt Sampson wrote:
> On 2008-01-23 15:23 +1100 (Wed), Daniel Carosone wrote:
> > On Wed, Jan 23, 2008 at 09:41:23AM +0900, Curt Sampson wrote:
> > > Given that 3.1.2 starts with a messed-up VGA console (it goes into
> > > 50 line mode, and the top-half and bottom-half lines are arranged
> > > somewhat weirdly, as if it thinks it's a 25-line console)
> >
> > This part, at least, is simply a matter of a boot option (passed via
> > grub) telling xen to use 25-line mode.  Or potentially compileing a
> > dom0 kernel that uses 50-line mode, but I didn't try that.
>
> If I recall correctly, even the xen kernel output appears to "broken" in
> this 50-line mode, and it comes up in 25-line mode on other machines. I
> looked about for options related to this, and didn't see any. And xen
> 3.2.0 comes up in 25-line mode. So this really looks like a Xen bug, not
> proper behaviour, to me.

I would call this a "missing feature". :-)

@Manuel:
I like the idea to keep xenkernel3 and xentools3 (or rename them to
xenkernel31/xentools31) and create new packages for Xen 3.2.x 
(xenkernel32/xentools32).

That scheme should scale:

xenkernel31/xentools31 => Xen 3.1.x series (for NetBSD 3.1/4.0 and current)
xenkernel32/xentools32 => Xen 3.2.x series (for NetBSD 5.0 and current)
xenkernel33/xentools33 => Xen 3.3.x series (not yet released)
etc.

The packages xenkernel31/xentools31 will be removed from pkgsrc
when NetBSD 4.0 is no longer supported.

BTW: There will be a Xen 3.1.3 bugfix release. 1st release candidate is tagged
in the mercurial repository.

Christoph