From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Plan 9 Xen -- Follow up on previous 9fans topic
Date: Mon, 12 Oct 2009 15:24:40 +0100 [thread overview]
Message-ID: <1a7597633da77b82fa24e0f2d456398f@hamnavoe.com> (raw)
In-Reply-To: <26F7BB92-E55B-4E9E-BDB5-813DB9F63A10@pvv.ntnu.no>
/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.
next prev parent reply other threads:[~2009-10-12 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 13:21 Jack Norton
2009-10-02 14:15 ` Andreas Eriksen
2009-10-02 21:41 ` Alex Lee
2009-10-03 10:06 ` Richard Miller
2009-10-04 22:57 ` Andreas Eriksen
2009-10-05 9:01 ` Richard Miller
2009-10-12 14:24 ` Richard Miller [this message]
[not found] <<26F7BB92-E55B-4E9E-BDB5-813DB9F63A10@pvv.ntnu.no>
2009-10-04 23:01 ` erik quanstrom
2009-10-04 23:22 ` Andreas Eriksen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1a7597633da77b82fa24e0f2d456398f@hamnavoe.com \
--to=9fans@hamnavoe.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).