By running "sh NVIDIA-Linux-x86_64-185.18.14-pkg2.run -x"
i was able to get some extraction in folder bellow. It's hard for me to decide could it be patched similar schema in http://fluxcoil.net/doku.php/xen/docs
for xenified kernel or no.
Kernels 2.6.29.4 , 2.6.30.1 xenified via rebased patch set from Andy
do contain patched driver for GeForce 8000 series . It just works fine.

Nvidia driver extraction :-

root@SeverUbuntuJaunty:/usr/src/NVIDIA-Linux-x86_64-185.18.14-pkg2# ls -CR
.:
LICENSE nvidia-installer pkg-history.txt usr

./usr:
bin include lib lib32 share src X11R6

./usr/bin:
makeself.sh nvidia-bug-report.sh nvidia-smi tls_test
mkprecompiled nvidia-settings nvidia-xconfig tls_test_dso.so

./usr/include:
cuda GL vdpau

./usr/include/cuda:
cudaGL.h cuda.h

./usr/include/GL:
glext.h gl.h glxext.h glx.h

./usr/include/vdpau:
vdpau.h vdpau_x11.h

./usr/lib:
libcuda.so.185.18.14 libGL.so.185.18.14 libvdpau_nvidia.so.185.18.14 tls
libGLcore.so.185.18.14 libnvidia-cfg.so.185.18.14 libvdpau.so.185.18.14
libGL.la libnvidia-tls.so.185.18.14 libvdpau_trace.so.185.18.14

./usr/lib/tls:
libnvidia-tls.so.185.18.14

./usr/lib32:
libcuda.so.185.18.14 libGL.la libnvidia-tls.so.185.18.14 libvdpau.so.185.18.14 tls
libGLcore.so.185.18.14 libGL.so.185.18.14 libvdpau_nvidia.so.185.18.14 libvdpau_trace.so.185.18.14

./usr/lib32/tls:
libnvidia-tls.so.185.18.14

./usr/share:
applications doc man pixmaps

./usr/share/applications:
nvidia-settings.desktop

./usr/src:
nv

./usr/src/nv:
conftest.sh Makefile.kbuild nv.h nv-memdbg.h nvtypes.h os-agp.h README cpuopsys.h Makefile.nvidia nv-i2c.c nv-misc.h nv-vm.c os-interface.c rmretval.h gcc-version-check.c nvacpi.c nv-kernel.o nvreadme.h nv-vm.h os-interface.h
makefile nv.c nv-linux.h nv-reg.h os-agp.c os-registry.c

./usr/X11R6:
lib

./usr/X11R6/lib:
libXvMCNVIDIA.a libXvMCNVIDIA.so.185.18.14 modules

./usr/X11R6/lib/modules:
drivers extensions libnvidia-wfb.so.185.18.14

./usr/X11R6/lib/modules/drivers:
nvidia_drv.so

./usr/X11R6/lib/modules/extensions:
libglx.so.185.18.14

Boris.

--- On Tue, 7/14/09, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:

From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-users] pv_ops kernel and nvidia binary driver
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxx, "Michael Ralston" <michael@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Tuesday, July 14, 2009, 3:52 PM

On 07/11/09 23:03, Boris Derzhavets wrote:
> A while ago Jeremy responded the same question.
> Per Jeremy:- unmodified binary Nvidia driver would crash under Xen.
> Modified driver should in the pvops kernel.
>
> It's also my major concern as well.
>
> Boris
>
> --- On *Sun, 7/12/09, Michael Ralston /<michael@xxxxxxxxxxxxx>/* wrote:
>
>
> From: Michael Ralston <michael@xxxxxxxxxxxxx>
> Subject: [Xen-users] pv_ops kernel and nvidia binary driver
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Date: Sunday, July 12, 2009, 1:48 AM
>
> Just wondering what it will take to get the nvidia binary driver
> working on a pv_ops kernel.
>
> It makes it difficult to debug without the source to the nvidia
> driver, but I think it should be possible to get it to work without
> changing the binary driver. If the dom0 kernel had access to all the
> resources that a bare metal kernel did, then it should work right?
>

The problem comes down to whether the nvidia driver assumes the kernel's
(pseudo-)physical addresses are really machine physical or not. If it
doesn't do the appropriate conversions between physical and machine
addresses using the standard Linux DMA API (or similar), then it will
end up misprogramming the hardware and reading/writing random memory.
There's not a lot we can do about that if that happens within the binary
part of the nvidia driver. If the binary code calls out to the
source-available parts of the driver to do those conversions, then it
would be possible to fix there.

There are other potential pitfalls the nvidia driver could be falling
into, but that's the most likely.

J

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