Björn Steinbrink wrote: >> >> I had no problems patching older 2.6.16 kernels with XEN and >> >> vserver, but with the more recent one, the latest available vserver >> >> patch for 2.6.16 (patch-2.6.16.20-vs2.0.2-rc22.diff) does not apply >> >> without dozens of rejects that I can't fix myself. >> > >> > I take it that you are actually volunteering to test >> > such a kernel with and without Xen meshed in ... >> >> I think I can't follow your thoughts here :) >> [..] > > It basically means "I would create a patch for you, iff you promise to > actually test it and give feedback etc.". > [..]
Now that's clear to me :) I've no problem testing such a patch, maybe some other users that haven't spoken up will find it useful. Currently I have a development system standing here that will make it quite easy to do some testing (the Debian problems on the one hand and a vserver patch for 2.6.16.x on the other) :) The fastest way to get the same XEN kernel I want to use is: - Get the XEN 3.0.4-1 source tarball from XEN Source - Download the incremental updates from 2.6.16.33 to 2.6.16.37 to patches/linux-2.6.16.33/ and add the files to the patches/linux-2.6.16.33/series file, so they are applyed automatically in the next step - Do a 'make prep-kernels' in the XEN source dir (the failed hunks in the Makefile can be ignored of course :)) -> Now you have a 2.6.16.37 ready made with XEN laying in linux-2.6.16.33-xen. If I could get a vserver patch against such a kernel, I would of course test it out and report back here (maybe not after a day or two, 'cause I tend to test things too much than too less). Regards, Markus _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
