WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] 2.6.18 to 2.6.18-8

On Wed, 2007-06-06 at 12:05 -0700, Tom Mornini wrote:
> On Jun 6, 2007, at 7:27 AM, Jason Ward wrote:
> 
> > The message below mentions an earlier post about moving from 2.6.18 to
> > 2.6.18-8.  I searched the archives and was unable to find the  
> > earlier post.
> > Does anyone know where I can find that post and/or the instructions  
> > on how
> > to change the kernel version that xen uses?
> 
> I believe I was part of that conversation.
> 
> We just tried to duplicate those instructions with 3.1.0 and, while the
> patches apply, we cannot build successfully. :-(
> 
> I know I'd *love* to see an *official* 3.1.0/2.6.18.8 release. :-)

You can clone the linux-2.6 Mercurial repository from kernel.org and
serve it locally, its not hard to revert to version x and then diff from
Y to present to see what changed. Or if your comfy with git, you could
get to it a little quicker. 

You'd then need to adjust patches/* in your xen tree accordingly where
you can so they 'just work', then manually apply the hunks that won't.
That is a painful, frustrating process because you have to project how
Xen would have patched differently based on what they did in your
current version.

Unless its just a few minor things that changed, your end result can
only be buggy, its better to wait for xen-devel to jump. If you have to
edit the patches beyond a few lines, count on the end result being
buggy.

If its something like.. a function somewhere was changed to take less
arguments, you'd probably be ok.

They are about to get rid of the sparse tree anyway. When that happens
you can just build your dom-u kernels like you would any other. I
figured something big was about to change when 3.1 didn't hop kernels.

Best,
--Tim




_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>