9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: stella@plan9.jp
To: 9fans@cse.psu.edu
Subject: [9fans] Xen and new venti
Date: Tue,  4 Mar 2008 08:15:03 +0900	[thread overview]
Message-ID: <584660ba70c012aa7f0600bb63b6d803@plan9.jp> (raw)

Hi,
I'm trying to install plan9 under Xen 3.2.0 with venti
but the kernel avaiable on the web is too old to support nventi.
I decided to try to compile it but there were some troubles I was able to fix
(with the help of #plan9). Now there's a problem (or two) I do not know
how to solve; I must inform you that I'm not an expert of both plan9 and C.
This is what I did:

9fs sources
cpr /n/sources/xen/xen3/9 /sys/src/9
cd /sys/src/9/xen3

then I got /usr/local/xen from my xen installation and put it under xen-public
I edited xenpcf to remove il support

mk

I had a problem of type in xendat.h fixed by replacing
uint8 with uint at line 1540

mk

I had some other problems which I fixed by
1) adding void	mfence(void); into fns.h
2) editing line 286 in sdxen.c to look like
	 xenbio(SDunit* unit, int lun, int write, void* data, long nb, uvlong bno)
3) adding /$objtype/lib/libip.a\ to LIB in mkfile
4) adding in l.s
TEXT mfence(SB), $0
	BYTE $0x0f
	BYTE $0xae
	BYTE $0xf0
	RET

mk now gives two errors which I do not know how to fix:
...omissis...
size 9xenpcf
v4parsecidr: undefined: memcpy in v4parsecidr
_strayintrx: _ctype: not defined
mk: 8c -FVw '-DKERNDATE='`{date ...  : exit status=rc 7851: 8l 7855: error

any idea?
Thank you

S.


             reply	other threads:[~2008-03-03 23:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-03 23:15 stella [this message]
2008-03-04  0:52 ` erik quanstrom
2008-03-04 21:38   ` stella
2008-03-04 22:18     ` Richard Miller
2008-03-04 22:26       ` erik quanstrom
2008-03-05  0:18 stella
2008-03-05  0:37 ` erik quanstrom
2008-03-05  8:10   ` stella
2008-03-08 20:11 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=584660ba70c012aa7f0600bb63b6d803@plan9.jp \
    --to=stella@plan9.jp \
    --cc=9fans@cse.psu.edu \
    /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).