Debian Bug report logs - #500175
nvidia-kernel-source: Please support compilation against non-paravirt ops style Xen kernels

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Ian Campbell <ijc@hellion.org.uk>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: nvidia-kernel-source: Please support compilation against non-paravirt ops style Xen kernels

Date: Thu, 25 Sep 2008 19:44:35 +0100

[Message part 1 (text/plain, inline)]

Package: nvidia-kernel-source
Version: 173.14.09-5.0.hellion1
Severity: wishlist
Tags: patch

The nvidia kernel source is currently patched to remove the Xen special casing
in order to allow it to build and run against a kernel which has both
CONFIG_PARAVIRT=y and CONFIG_XEN=y but is running natively. (I think this was
due to #481485, #482305, #496173 etc)

The kernel team are proposing to enable a patch to support the old-style (i.e.
non-CONFIG_PARAVIRT) CONFIG_XEN in order to regain domain0 and 64 bit support
for Lenny. See http://lists.debian.org/debian-kernel/2008/09/msg00742.html and
http://lists.alioth.debian.org/pipermail/pkg-xen-devel/2008-September/002044.html
This will unfortunately break the compilation of the current nvidia kernel
source against these kernels.

I have updated the xen.patch to support both CONFIG_PARAVIRT-Xen (running Xen)
and Legacy-Xen. I have tested with 2.6.26-1-amd64 (CONFIG_PARAVIRT running on
native, pkg version 2.6.26-5) as well as 2.6.26-1-xen-amd64 (Legacy-Xen,
running as a Xen domain 0, pkg version 2.6.26-7~snapshot.12252) and
2.6.18.8-xen (Legacy-Xen, running as a Xen domain 0, my own build). I also
build tested against 2.6.26-1-686 but can't reboot that machine at the moment
since it's running a long running test.

I've filed this bug as a wishlist preemptively before the kernel is uploaded,
once the kernel goes in presumably the priority will increase.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages nvidia-kernel-source depends on:
ii  debhelper                     7.0.17     helper programs for debian/rules
ii  dpatch                        2.0.30     patch maintenance system for Debia
ii  make                          3.81-5     The GNU version of the "make" util
ii  sed                           4.1.5-8    The GNU sed stream editor

Versions of packages nvidia-kernel-source recommends:
ii  devscripts                   2.10.35     scripts to make the life of a Debi
ii  kernel-package               11.001-0.1  A utility for building Linux kerne
ii  nvidia-glx                   173.14.09-5 NVIDIA binary Xorg driver

nvidia-kernel-source suggests no packages.

-- no debconf information

[xen.patch (text/x-diff, attachment)]

Message #10 received at 500175@bugs.debian.org (full text, mbox, reply):

From: Andreas Beckmann <debian@abeckmann.de>

To: 500175@bugs.debian.org

Subject: Re: nvidia-kernel-source: Please support compilation against non-paravirt ops style Xen kernels

Date: Fri, 14 May 2010 15:01:59 +0200

On Thursday, 25. September 2008 20:44:35 Ian Campbell wrote:
> Package: nvidia-kernel-source
> Version: 173.14.09-5.0.hellion1
> -- System Information:
> Debian Release: lenny/sid
>  APT prefers unstable
>Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/1 CPU core)

Is this issue still present with the current driver (195.36.24-1 entered 
testing today) and kernel versions (2.6.32-*) in testing/unstable?
The module builds for all kernel flavors of 2.6.32 in Debian (normal, openvz, 
vserver, xen) without needing a patch at all (all old patches that did not 
apply for a long time have been removed from the package source). But so far 
we don't have any reports about someone actually running the nvidia module on 
any of the "virtualized" kernels successfully.


Andreas

Message #17 received at 500175@bugs.debian.org (full text, mbox, reply):

From: Andreas Beckmann <debian@abeckmann.de>

To: 500175@bugs.debian.org, 500175-submitter@bugs.debian.org

Subject: Re: nvidia-kernel-source: Please support compilation against non-paravirt ops style Xen kernels

Date: Wed, 25 Aug 2010 05:57:00 +0200

Is this issue still present with the current driver (195.36.31-2 entered
unstable yesterday) and kernel versions (2.6.32-5-*) in testing/unstable?
The module builds for all kernel flavors of 2.6.32 in Debian (normal,
openvz, vserver, xen) without needing a patch at all (all old patches that
did not apply for a long time have been removed from the package source).
But so far we don't have any reports about someone actually running the
nvidia module on any of the "virtualized" kernels successfully.


Andreas

Message #27 received at 500175-done@bugs.debian.org (full text, mbox, reply):

From: Andreas Beckmann <debian@abeckmann.de>

To: 500175-done@bugs.debian.org

Subject: Re: nvidia-kernel-source: Please support compilation against non-paravirt ops style Xen kernels

Date: Sun, 28 Nov 2010 20:34:12 +0100

On Wednesday, 25. August 2010 05:57:00 Andreas Beckmann wrote:
> Is this issue still present with the current driver (195.36.31-2 entered
> unstable yesterday) and kernel versions (2.6.32-5-*) in testing/unstable?
> The module builds for all kernel flavors of 2.6.32 in Debian (normal,
> openvz, vserver, xen) without needing a patch at all (all old patches that
> did not apply for a long time have been removed from the package source).
> But so far we don't have any reports about someone actually running the
> nvidia module on any of the "virtualized" kernels successfully.

Since we haven't heard from the submitter since we asked for more information 
a few months ago, I assume the problem does no longer exist and I'm closing 
this report now.
If the problem is still reproducible with current driver versions (195.36.31-6 
in testing/unstable or 260.19.21-1 in experimental), feel free to reopen this 
bug report.


Andreas

Send a report that this bug log contains spam.