Xen users - Aug 2005 - Has 2.4 kernel support ended on xen?

Hi

I was just wondering whether the xen team has stopped supporting the 2.4 kernel?

Basically the reason why I ask is becuase everytime I''ve tried to
build the 2.4 xen kernel under xen 3.0 (unstable) I keep getting
errors (usually about usb) so it made me wonder whether the xen
patches are being maintained.

Anyone have any insight into this?

Thanks
Shaz

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

> I was just wondering whether the xen team has stopped 
> supporting the 2.4 kernel?
It''s always been a low priority activity, but the intention is for Xen
3
to be able to support mainstream Linux 2.4 as a domU, but not as a dom0.
> Basically the reason why I ask is becuase everytime I''ve 
> tried to build the 2.4 xen kernel under xen 3.0 (unstable) I 
> keep getting errors (usually about usb) so it made me wonder 
> whether the xen patches are being maintained.
I think that''s actually quite a trivial fix. In fact, I seem to recall
fixing the same error at some point a few weeks, ago, so it may just be
a case of a mercurial accident causing something to be resurrected. 

Patches welcome :-)  We could even have a 2.4 port maintainer...

Thanks,
Ian
> Anyone have any insight into this?
> 
> Thanks
> Shaz
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 8/2/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
wrote:
> 
> > I was just wondering whether the xen team has stopped
> > supporting the 2.4 kernel?
> 
> It''s always been a low priority activity, but the intention is for
Xen 3
> to be able to support mainstream Linux 2.4 as a domU, but not as a dom0.
> 
> > Basically the reason why I ask is becuase everytime I''ve
> > tried to build the 2.4 xen kernel under xen 3.0 (unstable) I
> > keep getting errors (usually about usb) so it made me wonder
> > whether the xen patches are being maintained.
> 
> I think that''s actually quite a trivial fix. In fact, I seem to
recall
> fixing the same error at some point a few weeks, ago, so it may just be
> a case of a mercurial accident causing something to be resurrected.
> 
> Patches welcome :-)  We could even have a 2.4 port maintainer...
> 
Hey thanks for the reply.

I''d love to maintain something like that, but I don''t know how
to
program well in C. Although I''vw written basic C programs I''ve
never
dealt with a complex C program. Is there a way to just build the 2.4
xenU kernel, without the xen0 kernel?

Many Thanks 
Shaz

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

> I''d love to maintain something like that, but I don''t
know how to
> program well in C. Although I''vw written basic C programs
I''ve never
> dealt with a complex C program. Is there a way to just build the 2.4
> xenU kernel, without the xen0 kernel?
Is it actually trying to build a xen0 kernel?  It shouldn''t be!

On my system the build failed with a load of timer related errors - I assume 
this is due to the new timer API but I haven''t looked into that stuff
yet.

Cheers,
Mark

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

> > I''d love to maintain something like that, but I
don''t know how to
> > program well in C. Although I''vw written basic C programs 
> I''ve never 
> > dealt with a complex C program. Is there a way to just 
> build the 2.4 
> > xenU kernel, without the xen0 kernel?
> 
> Is it actually trying to build a xen0 kernel?  It shouldn''t be!
> 
> On my system the build failed with a load of timer related 
> errors - I assume this is due to the new timer API but I 
> haven''t looked into that stuff yet.
Yep, Steve fixed the USB problem (by removing it from the build), but
the recent changes to the time API are more tricky. Someone is going to
need to look at the 2.6 diffs and apply some thought...

Ian 

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

> > On my system the build failed with a load of timer related
> > errors - I assume this is due to the new timer API but I
> > haven''t looked into that stuff yet.
>
> Yep, Steve fixed the USB problem (by removing it from the build), but
Should only matter if the USB frontend was configured in though (Shahzad, were 
you trying to build this?).  Somehow the USB config options survived the 
removal of the code, they should be ditched until the 2.6 USB backend is 
merged.
> the recent changes to the time API are more tricky. Someone is going to
> need to look at the 2.6 diffs and apply some thought...
I''m nosing through it - I hadn''t looked at the new time API. 
Looks like it
could take a while.

Cheers,
Mark

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

> Patches welcome :-)  We could even have a 2.4 port maintainer...
Hmmmmm.  I''ve seen less rotten things in student kitchens than the 2.4
tree in
-unstable.  Something tells me that this hasn''t been built in a long
while...

Since I''ve already started playing with this I''ll probably fix
up the 2.4 port
and stick an HG tree online for people to test.  I''m not volunteering
to be
the official maintainer, just yet though ;-) so it''d be nice if we
could have
a build daemon that tries all the ports and all the architectures and screams 
via e-mail if something breaks the build.  Hopefully that''ll irritate
people
enough to avoid a huge build up of mouldy code!

Shahzad: would you be willing to test the fixed 2.4 on your box?

Cheers,
Mark

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

> Hmmmmm.  I''ve seen less rotten things in student kitchens 
> than the 2.4 tree in -unstable.  Something tells me that this 
> hasn''t been built in a long while...
I spent half an hour fixing it up a couple of months back, so its not
too far out of date.
 
> Since I''ve already started playing with this I''ll
probably
> fix up the 2.4 port and stick an HG tree online for people to 
> test.  I''m not volunteering to be the official maintainer, 
> just yet though ;-) so it''d be nice if we could have a build 
> daemon that tries all the ports and all the architectures and 
> screams via e-mail if something breaks the build.  Hopefully 
> that''ll irritate people enough to avoid a huge build up of 
> mouldy code!
The nightly build infrastructure already does this, though I''m afraid I
disabled the email complaints about the 2.4 build being broken some
months back.

Ian

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

On 8/2/05, Mark Williamson <mark.williamson@cl.cam.ac.uk>
wrote:
> > I''d love to maintain something like that, but I
don''t know how to
> > program well in C. Although I''vw written basic C programs
I''ve never
> > dealt with a complex C program. Is there a way to just build the 2.4
> > xenU kernel, without the xen0 kernel?
> 
> Is it actually trying to build a xen0 kernel?  It shouldn''t be!
> 
> On my system the build failed with a load of timer related errors - I
assume
> this is due to the new timer API but I haven''t looked into that
stuff yet.
> 
> Cheers,
> Mark
> 
Hi 

I''m more than willing to test it out. Just let me know when you want
me to test it and I''ll start straight away. I appreciate your help in
this.

Thanks
Shahzad

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

> I spent half an hour fixing it up a couple of months back, so its not
> too far out of date.
There were breakages all over the place - all due to changes in the last 
couple of months, which makes sense now!  It''s rather impressive just
how
quickly it''s diverged and how many things broke.  Once I''ve
ported Xenbus
I''ll hopefully be done...  It''s an educational glimpse into
all the recent
changes anyhow ;-)
> > Since I''ve already started playing with this I''ll
probably
> > fix up the 2.4 port and stick an HG tree online for people to
> > test.  I''m not volunteering to be the official maintainer,
> > just yet though ;-) so it''d be nice if we could have a build
> > daemon that tries all the ports and all the architectures and
> > screams via e-mail if something breaks the build.  Hopefully
> > that''ll irritate people enough to avoid a huge build up of
> > mouldy code!
>
> The nightly build infrastructure already does this, though I''m
afraid I
> disabled the email complaints about the 2.4 build being broken some
> months back.
Can''t say I entirely blame you :-)  Where do the e-mails go?  It seems
like
they could usefully go to a (separate?) list, if they''re only once
daily.  Of
course if they can go on the web like the regression test results
that''d also
be cool.

Cheers,
Mark

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