From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <25c2223b56be202f15da4a4198616442@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Xen and new venti
From: Richard Miller <9fans@hamnavoe.com>
Date: Tue,  4 Mar 2008 22:18:22 +0000
In-Reply-To: <25df71d6e3a6916ef67ff72f3b2c7ff4@plan9.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 6eda2d4e-ead3-11e9-9d60-3106f5b1d025

> Hi,
> thanks to the suggestion erik gave me I was able to compile the kernel:
> I just needed to switch from memcpy to memmove into /sys/src/libip/parseip.c and recompile libip
> and then recompile also /sys/src/libc

I can't see why this should have been necessary - libc contains memcpy
already.  I have just updated /n/sources/xen/xen3 so it compiles with
the current Plan 9 kernel source (using Xen 3.0.2).  I made the other
changes you listed, but I didn't have to do anything about memcpy.

> I moved the kernels to the Xen machine but all of them crashes just after the message
> "Started domain plan9"
>
> Am I missing something?

The present Plan 9 xen kernel works with Xen 3.0.x; you said you are using Xen 3.2.0.
Xen is not known for the consistency of its interfaces from one release to the
next, so it is quite possible that some rewriting needs to be done on the Plan 9
side to deal with changes in Xen semantics.

Have you enabled verbose debugging messages on the Xen console?  You should see
some indication of why the plan9 guest crashed.