On Thu, Apr 23, 2009 at 10:49 PM, Nigel Gamble <nigel@xxxxxxx> wrote:
> On Feb 24, 2009, at 1:51 PM, Andrew Lyon wrote:
>> On Tue, Feb 24, 2009 at 9:22 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
>>> Boris Derzhavets wrote:
>>>> X-Server fails to start on GeForce 8500 GT
>>>> Attempting "startx" i get a trace back.
>>>> Does it mean , that a proper NVIDIA driver is just not available for the
>>>> most recent
>>>> 2.6.29-rc5 ?
>>> Are you using the nvidia binary driver? I would be surprised if it
>>> out of the box; if changes need to be made to the binary parts, it may
>>> be fixable at all.
>> I believe the current driver works with Xen because somebody outside
>> of nvidia contributed a patch, I use the nvidia binary driver with Xen
>> 3.2.1 and my custom dom0 kernel which is 126.96.36.199 patched with
>> openSUSE Xen patches rebased to apply to vanilla, it works very well
>> but when pv_ops is merged into mainline the nvidia driver will
>> probably work when it is running on the bare metal but not under Xen
>> Having said that the patch for Xen support only touched the open
>> source parts of the driver, as soon as the current problems with hvm
>> on pv_ops are fixed I will be testing pv_ops and nvidia driver and I
>> will attempt to fix any problems, my C skills are improving so I might
>> be able to figure it out.
> Did you ever figure this out? I've just hit the same problem. It looks
> like the source code part of the Nvidia kernel module has the code necessary
> to work on an old Xen Linux, but if it detects CONFIG_PARAVIRT set for a
> pv_ops kernel, it gives up an doesn't attempt to work with Xen at all.
hvm is still not working with pv_ops dom0 so I've not looked at it.
With a traditional patched Xen dom0 kernel you can use
IGNORE_XEN_PRESENCE=y to bypass the CONFIG_PARAVIRT check.
Xen-devel mailing list