In addition to this, what would be the best way to deal with the modules? I understand the original config doesn't use modules but i've added a few things to it and so have modules to deal with. Ideally 'make world' would install the modules to a folder which can be installed on the other domains later...
James
re: make world, is there a way to install my own .config's for the xen0 and xenU kernels rather than having it just use the defaults?
thanks
James
From: Ian Pratt
Sent: Mon 21/06/2004 4:16 AM
To: James Harper
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx; Ian.Pratt@xxxxxxxxxxxx
Subject: Re: [Xen-devel] domain0 no longer boots
> I recompiled the domain0 kernel and it appears to be running again.
> Maybe if I recompile the U kernel it might work too... I haven't had it
> working yet.
>
> I did have to change a link though... asm/keyboard.h linked to the
> sparse tree where it doesn't exist. I linked it to asm-i386/keyboard.h
> and it seems to work fine.
When using the unstable tree, its always wise to recompile
everything with 'make world' having done a bk pull: Certain
checkins in the unstable line do make changes to the hypervisor
API (we obviously don't do this in the stable series).
Keir checkedin a couple of important cleanups to the API
yesterday, which removed some changes in the sparse tree. As well
as rebuilding xen linux, it was necessary to redo the
'mkbuildtree'. "make world" will do this for you.
Ian