From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: text/plain; charset=windows-1252; format=flowed; delsp=yes
Mime-Version: 1.0 (Apple Message framework v1076)
From: Andreas Eriksen <andreer@pvv.ntnu.no>
In-Reply-To: <81cf0fca2b48d803c459094074a13c2e@hamnavoe.com>
Date: Mon,  5 Oct 2009 00:57:27 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <26F7BB92-E55B-4E9E-BDB5-813DB9F63A10@pvv.ntnu.no>
References: <81cf0fca2b48d803c459094074a13c2e@hamnavoe.com>
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
Topicbox-Message-UUID: 7ded28a2-ead5-11e9-9d60-3106f5b1d025

>> 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 =20
XenServer 5.0r3, but unfortunately it failed with roughly the same =20
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 =20
xenelf in the makefile, like this:

XENELF=3D'LOADER=3Dgeneric,XEN_VER=3Dxen-3.0,ELF_PADDR_OFFSET=3D0,\
	VIRT_BASE=3D'$KZERO',VIRT_ENTRY=3D'$KTZERO',PAE=3D'$PAE

Now I may be way off here, but I though that perhaps the tab character =20=

in front of
VIRT_BASE here may cause it to not be recognized by xenelf. I joined =20
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 =20=

at random trying
to figure all of this out :-)

=96 Andreas=