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: Re: [9fans] Plan 9 Xen -- Follow up on previous 9fans topic
Date: Mon,  5 Oct 2009 00:57:27 +0200	[thread overview]
Message-ID: <26F7BB92-E55B-4E9E-BDB5-813DB9F63A10@pvv.ntnu.no> (raw)
In-Reply-To: <81cf0fca2b48d803c459094074a13c2e@hamnavoe.com>

>> The kernel did not compile against the most recent sources.
>
> I've fixed this so it compiles again with current kernel source.
> Haven't tried booting it on anything, though.


I successfully compiled against Xen 3.4.1 and tried to boot it on  
XenServer 5.0r3, but unfortunately it failed with roughly the same  
error as the precompiled kernel on sources:

elf_xen_addr_calc_check: ERROR: ELF_PADDR_OFFSET set, VIRT_BASE unset

When compiling, I can see that VIRT_BASE is given as an argument to  
xenelf in the makefile, like this:

XENELF='LOADER=generic,XEN_VER=xen-3.0,ELF_PADDR_OFFSET=0,\
	VIRT_BASE='$KZERO',VIRT_ENTRY='$KTZERO',PAE='$PAE

Now I may be way off here, but I though that perhaps the tab character  
in front of
VIRT_BASE here may cause it to not be recognized by xenelf. I joined  
it into one line,
and I am rewarded with a different error message:

"xc_dom_alloc_segment: segment start isn't page aligned".

I really don't know if this is better or worse. I'm just poking around  
at random trying
to figure all of this out :-)

– Andreas


  reply	other threads:[~2009-10-04 22:57 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 [this message]
2009-10-05  9:01       ` Richard Miller
2009-10-12 14:24       ` Richard Miller
     [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=26F7BB92-E55B-4E9E-BDB5-813DB9F63A10@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).