I have succeeded in getting a fedora based kernel to build with Dom0 patches added. The steps were roughly as follows; 1. Start from kernel-2.6.28-0.106.rc6.git4.fc11.src.rpm 2. Create a patch from http://xenbits.xen.org/paravirt_ops/patches.hg/ changeset 2238 by concatenating those patches listed in the series file (excluding those commented out) together. 3. Edit kernel.spec to revert to plain rc6 (which the pvops patches seem currently to be based on though some patches from rc8 seem to be included in the x86/x86.patch file), add the combined patch, and increase the fuzz factor to 2 so it applies. 4. Make several edits to the source files and configuration options to get it to compile on F10. Some of these, such as the couple I have so far reported on http://bugzilla.redhat.org/ (476456 and 476457), are due to code problems that show up because the F10 compiler seems to be a bit better at checking for errors. If anyone wants to inspect it, the source rpm generated is at http://compsoc.dur.ac.uk/~may/xen/kernel-2.6.28-0.106.rc6.fc10.src.rpm It is completely untested beyond the fact that it compiles for me, so I have no idea if a kernel built from it will actually boot. Michael Young
On Mon, Dec 15, 2008 at 7:07 PM, M A Young <m.a.young@durham.ac.uk> wrote:> I have succeeded in getting a fedora based kernel to build with Dom0 patches > added. The steps were roughly as follows; >Cool.> 1. Start from kernel-2.6.28-0.106.rc6.git4.fc11.src.rpm > 2. Create a patch from http://xenbits.xen.org/paravirt_ops/patches.hg/ > changeset 2238 by concatenating those patches listed in the series file > (excluding those commented out) together. > 3. Edit kernel.spec to revert to plain rc6 (which the pvops patches seem > currently to be based on though some patches from rc8 seem to be included in > the x86/x86.patch file), add the combined patch, and increase the fuzz > factor to 2 so it applies. > 4. Make several edits to the source files and configuration options to get > it to compile on F10. Some of these, such as the couple I have so far > reported on http://bugzilla.redhat.org/ (476456 and 476457), are due to code > problems that show up because the F10 compiler seems to be a bit better at > checking for errors. >Is there any useful information that you could add to the following? http://wiki.xensource.com/xenwiki/XenParavirtOps Thanks, Todd> If anyone wants to inspect it, the source rpm generated is at > http://compsoc.dur.ac.uk/~may/xen/kernel-2.6.28-0.106.rc6.fc10.src.rpm > It is completely untested beyond the fact that it compiles for me, so I have > no idea if a kernel built from it will actually boot. > > Michael Young > > -- > Fedora-xen mailing list > Fedora-xen@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen >-- Todd Deshane http://todddeshane.net http://runningxen.com
On Tue, Dec 16, 2008 at 12:07:30AM +0000, M A Young wrote:> I have succeeded in getting a fedora based kernel to build with Dom0 > patches added. The steps were roughly as follows; > > 1. Start from kernel-2.6.28-0.106.rc6.git4.fc11.src.rpm > 2. Create a patch from http://xenbits.xen.org/paravirt_ops/patches.hg/ > changeset 2238 by concatenating those patches listed in the series file > (excluding those commented out) together. > 3. Edit kernel.spec to revert to plain rc6 (which the pvops patches seem > currently to be based on though some patches from rc8 seem to be included > in the x86/x86.patch file), add the combined patch, and increase the fuzz > factor to 2 so it applies. > 4. Make several edits to the source files and configuration options to get > it to compile on F10. Some of these, such as the couple I have so far > reported on http://bugzilla.redhat.org/ (476456 and 476457), are due to > code problems that show up because the F10 compiler seems to be a bit > better at checking for errors. > > If anyone wants to inspect it, the source rpm generated is at > http://compsoc.dur.ac.uk/~may/xen/kernel-2.6.28-0.106.rc6.fc10.src.rpm > It is completely untested beyond the fact that it compiles for me, so I > have no idea if a kernel built from it will actually boot. >You might also need xen-unstable (3.4), or at least the tools from it. Or backport the pv_ops memory ballooning support into older xen tools version. See: http://lists.xensource.com/archives/html/xen-devel/2008-12/msg00469.html -- Pasi
On Fri, Dec 19, 2008 at 12:25:01AM +0000, M A Young wrote:> On Tue, 16 Dec 2008, Pasi Kärkkäinen wrote: > > >On Tue, Dec 16, 2008 at 12:07:30AM +0000, M A Young wrote: > >>If anyone wants to inspect it, the source rpm generated is at > >>http://compsoc.dur.ac.uk/~may/xen/kernel-2.6.28-0.106.rc6.fc10.src.rpm > >>It is completely untested beyond the fact that it compiles for me, so I > >>have no idea if a kernel built from it will actually boot. > >> > > > >You might also need xen-unstable (3.4), or at least the tools from it. > >Or backport the pv_ops memory ballooning support into older xen tools > >version. > > Thanks, I have built myself an rpm starting from xen-3.3.0-1.fc10.src.rpm, > with the resulting source RPM at > http://compsoc.dur.ac.uk/~may/xen/xen-3.4.0-0.fc10.dev18926.0.src.rpm > if anyone else is interested. >>From rawhide buildlog/changelog:xen-3.3.0-2.fc11 ---------------- * Wed Dec 17 17:00:00 2008 Gerd Hoffmann <kraxel@redhat.com> - 3.3.0-2 - build and package stub domains (pvgrub, ioemu). - backport unstable fixes for pv_ops dom0. So you could use that too. -- Pasi
On Fri, 19 Dec 2008, Pasi K?rkk?inen wrote:> From rawhide buildlog/changelog: > > xen-3.3.0-2.fc11 > ---------------- > * Wed Dec 17 17:00:00 2008 Gerd Hoffmann <kraxel@redhat.com> - 3.3.0-2 > - build and package stub domains (pvgrub, ioemu). > - backport unstable fixes for pv_ops dom0. > > So you could use that too.Yes, I spotted that a few minutes after I had uploaded that SRPM and posted about it, and I have rebuilt that version for F10 on the machine I was going to test it on. Unfortunately the kernel I posted doesn''t build for i686 PAE (it does for x86_64), so I might have to change my plans or come up with a revised kernel. Michael Young