9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Andreas Eriksen <andreer@pvv.ntnu.no>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Running Plan 9 on Xen 3.2
Date: Tue, 30 Jun 2009 00:19:06 +0200	[thread overview]
Message-ID: <BA018666-2016-49DE-BEA6-2C629D5E5770@pvv.ntnu.no> (raw)

Using the precompiled PAE kernel from sources in xen 3.2 on debian
lenny gives the message

Error: (2, 'Invalid kernel', 'elf_xen_addr_calc_check: ERROR:
ELF_PADDR_OFFSET set, VIRT_BASE unset\n')

Does this mean Plan 9 is not compatible with Xen 3.2, or does it just
need a recompile or some other quick fix?
I would answer this question myself but unfortunately it seems a lot
of the source files are no longer world readable after pae support was
added (which is great by the way, thanks!).



             reply	other threads:[~2009-06-29 22:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 22:19 Andreas Eriksen [this message]
2009-06-30  7:57 ` Richard Miller

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=BA018666-2016-49DE-BEA6-2C629D5E5770@pvv.ntnu.no \
    --to=andreer@pvv.ntnu.no \
    --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).