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/
Home Products Support Community News


Re: [Xen-users] Latest Xen Kernel

To: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Latest Xen Kernel
From: Paul Schulze <avlex@xxxxxxx>
Date: Fri, 18 Jul 2008 15:14:11 +0200
Delivery-date: Fri, 18 Jul 2008 06:15:43 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:mime-version:in-reply-to :references:content-type:message-id:content-transfer-encoding:from :subject:date:to:x-pgp-agent:x-mailer:sender; bh=x9YoB+0i8LzWLLIBN0hGfdBiWuYq6yCk4XwrSCJ+Pb8=; b=Cmh8ypU6Vn+29mQlawCOWO4mHL7nBjC3ykzMdgVBm9s507q74mVHBa1KhXEgRkzufz ELXb26BSriOhuV3ejTJevBQ2GyJ+vHHIeXoBCI4m843EjvkCGDMSFdPQUxHKu//ORPrm lzv/+xWC2fTPUvTnhSU0CsACkAh92r+znaXR8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:content-type:message-id :content-transfer-encoding:from:subject:date:to:x-pgp-agent:x-mailer :sender; b=wmKPfidSIkSxWaOGn2BG7BoAJMR8MqjBonLx5mXOP5U04O7yhxZhvTtRgUYdiM0byO cEurujWKmkmQWsLkB6vNKCU/GX1mREa6EkbVD8xj/7UY8QNs6t1kEAaaA6JWISLDGN9O qj0jdv/JWzL5hOsWToj+8x5pcorPHmqz1de+w=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1216354115.5537.80.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4bca5f6c0807162002o459a1f64qf23e089bc286f579@xxxxxxxxxxxxxx> <1216267814.5537.23.camel@xxxxxxxxxxxxxxxxxxxxx> <0D462589-FA51-479D-892F-18D5D57BFAEB@xxxxxxx> <20080717100729.GR3771@xxxxxxxxxxxxxxx> <4bca5f6c0807171415y62400bedscd10f37820ed06f0@xxxxxxxxxxxxxx> <F35D5C8C-9576-4D1C-8128-261771D64AFC@xxxxxxx> <1216354115.5537.80.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hash: SHA1

Hi Chris,

I wasn't planning on releasing it separately, since it is might cause problems along the way (use at your own risk), but here is a patch I created for IPCop Experimental: http://www.solaris-net.org/ipcop-xen/ 31-ipcop-xen-patches.patch . It (hopefully) contains all the necessary patches for a vanilla kernel They were taken from the Ubuntu linux-image-2.6.24-18-xen source package and altered to prevent rejects and stuff. I mostly got rid of incompatible .orig and .rej files that already exist after applying the patch, not the best way to go, but it shouldn't create a problem. It also contains a patch to fix a build error, when building a DomU-only kernel. However, the resulting kernel might not be stable.

I've had random crashes of my IPCop DomU which might be the result of me ripping these out. I also noticed, that a resulting DomU-only kernel locks up when started as the first VM after booting the Dom0 (BUG() in pci_dma_xen-32.c i think) and a few other minor problems and kernel BUG()s that might or might not cause the crashes. I'm currently trying to debug this, however, it could also be a problem specific to my NICs and the sundance driver (for my D-Link DFE-580TX) not appreciating the PCI passthrough, so if someone tests these, please let me know if you experience the same problems.

To get the patches, you will need to do the following:
$ wget http://www.solaris-net.org/ipcop-xen/31-ipcop-xen- patches.patch -O - | patch -p3

Now you need a vanilla linux- tree, either from the full package or linux-2.6.24 and patch- I have only tested the later, since I am building it in the IPCop build environment together with the other stuff. Here is the order in which the patches should be applied:
0) patch- (if necessary)
1) linux-2.6.24-io-delay.patch
2) linux-
3) linux-2.6.24-xen-dev-mem-fix.patch
4) linux-2.6.24-xen-io-delay-fix.patch
5) linux-2.6.24-xen-net-fix.patch
6) linux-2.6.24-xen-domu-build-fix.patch
I trust you know what to do from here.

Oh and I checked the Debian patches earlier. Tim was right, the Debian kernel 2.6.25 uses PVOPS instead of a forward-port of the original kernel 2.6.18 Xen patches. Too bad, guess I will have to look for another set of patches against a more recent kernel too, if I can't fix this one. As he said, the git archive might be the way to go there, I'll let you know if I find something there.



- --
Paul Schulze
Public Key: http://solaris-net.dyndns.org/keys/key_avlex.asc

"Making mistakes is human,
but to really fuck things up you need Computers"

Am 18.07.2008 um 06:08 schrieb Tim Post:


On Fri, 2008-07-18 at 00:08 +0200, Paul Schulze wrote:
Hi Chris,

You can try, but it isn't all that easy to isolate the necessary
patches from the Debian source and I am not quiet sure if the patches
in Debian are even forward-ported. As I said, I haven't tried yet (I
probably will in the next week, because my IPCop DomU is acting up),
but I think I saw something that looked like Xenbus and PCIFront last
time I grepped through the patches. You better check before you put
some serious work in there.

What he might have to do is check out a specific kernel revision by its tag from kernel.ubuntu.com , then install the debhelper packages to use
the Debian build system

For instance , git-clone [url] 2.6.25.x (the version being a tag)
debian/rules custom-prepare-xen
cd debian/build

The kernel he wants will be in custom-source-xen which can be copied
anywhere else, or he could build it in the sparse tree custom-buld-xen
for testing.

That may be the best way to go, since it would be relatively easy to
re-generate .deb packages for that kernel so that it can be re-used.

I'm pretty sure 2.6.25.x (or later, up to .26-rc series) can be found in
the intrepid git tree.

The people on the Ubuntu kernel mailing list are very helpful and
tolerant, I'm sure they could give better help.

This will get him a newer kernel that can be used for dom-0 and dom-u,
with the device pass through that he needs.


Version: GnuPG v1.4.1 (Darwin)


Xen-users mailing list

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