On Tue, Nov 16, 2010 at 10:43:49AM -0800, Boris Derzhavets wrote:
> Today i've built vmlinuz-2.6.37-0.1.rc1.git8.xendom0.fc14.x86_64
> via Michael's
http://koji.fedoraproject.org/koji/taskinfo?taskID=2598434> and uncommented xen.pcifront.fixes.patch in kernel.spec, i.e.
>
> # Xen patches
> ApplyPatch xen.next-2.6.37.patch
> # ApplyPatch xen.upstream.core.patch
> ApplyPatch xen.pcifront.fixes.patch
> # ApplyPatch xen.pvhvm.fixes.patch
>
> as a fesult a got kernel wich runs pretty stable NFS client at Xen 4.0.1
> F14 Dom0 (2.6.32.25-172.xendom0.fc14.x86_64).
>
> I was able several times copied from NFS folder F14's ISO image (3.2 GB)
> to DomU and scp'ed it back and didn't get any kernel crashing on DomU.
Huh. I .. what? I am confused. I thought we established that the issue
was not related to Xen PCI front? You also seem to uncomment the
upstream.core.patches and the xen.pvhvm.patch - why?
>
> On Ubuntu 10.04 this kernel may be built as
2.6.37-rc1&git8 patched via
> xen.next-2.6.37.patch
> xen.pcifront.fixes.patch
> All required upstream patches may be taken (as well as 2 above)
> from
http://koji.fedoraproject.org/koji/taskinfo?taskID=2598434> I believe as soon as xen.pcifront.fixes.patch will be accepted by upstream
> NFS client issue on F14 will be gone
Ok, they are.. v2.6.37-rc2 which came out today has the fixes.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxhttp://lists.xensource.com/xen-devel
Home