From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <1a7597633da77b82fa24e0f2d456398f@hamnavoe.com>
To: 9fans@9fans.net
From: Richard Miller <9fans@hamnavoe.com>
Date: Mon, 12 Oct 2009 15:24:40 +0100
In-Reply-To: <26F7BB92-E55B-4E9E-BDB5-813DB9F63A10@pvv.ntnu.no>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Plan 9 Xen -- Follow up on previous 9fans topic
Topicbox-Message-UUID: 8537f736-ead5-11e9-9d60-3106f5b1d025

/n/sources/xen/xen3 is now updated (source and pre-built kernels) to
be compatible with Xen 3.2 - tested (thanks to Alex and Andreas) with:

  Xen 3.2.1 (debian package xen-linux-system-2.6.26-2-xen-686)
  XenServer 5.5

It also still boots on Xen 3.0.2.

I have to retract my remarks about Xen API churn: this time it was
only necessary to massage the ELF boot file format, and compensate
for one typo in Xen's 3.2 include headers; no kernel logic changes
were needed.  There may be lots of new API we aren't using, but
it appears our legacy approach is still supported.