Pkg xen devel - Oct 2013 - Bug#726827: xen-utils-4.1: Xen doesn't start on a laptop with Nvidia Optimus graphics

Package: xen-utils-4.1
Version: 4.1.4-4
Severity: important
Tags: patch

Dear Maintainer,

   * What led up to the situation?
Trying to start Xen on a Asus X53S laptop (which has dual Intel + Nvidia
Geforce 610M Optimus graphics card)

xend.log contains:
[2013-10-19 17:14:26 4239] INFO (SrvDaemon:332) Xend Daemon started
[2013-10-19 17:14:26 4239] INFO (SrvDaemon:336) Xend changeset: unavailable.
[2013-10-19 17:14:27 4239] ERROR (SrvDaemon:349) Exception starting xend
(Looped capability chain: 0000:01:00.0)
Traceback (most recent call last):
  File
"/usr/lib/xen-4.1/bin/../lib/python/xen/xend/server/SrvDaemon.py",
line
341, in run
    servers = SrvServer.create()
  File
"/usr/lib/xen-4.1/bin/../lib/python/xen/xend/server/SrvServer.py",
line
258, in create
    root.putChild('xend', SrvRoot())
  File
"/usr/lib/xen-4.1/bin/../lib/python/xen/xend/server/SrvRoot.py", line
40, in __init__
    self.get(name)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/web/SrvDir.py", line
84, in get
    val = val.getobj()
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/web/SrvDir.py", line
52, in
getobj
    self.obj = klassobj()
  File
"/usr/lib/xen-4.1/bin/../lib/python/xen/xend/server/SrvNode.py", line
30, in __init__
    self.xn = XendNode.instance()
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendNode.py", line
1181, in
instance
    inst = XendNode()
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendNode.py", line
159, in
__init__
    self._init_PPCIs()
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendNode.py", line
282, in
_init_PPCIs
    for pci_dev in PciUtil.get_all_pci_devices():
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/util/pci.py", line 474,
in
get_all_pci_devices
    return map(PciDevice, get_all_pci_dict())
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/util/pci.py", line 699,
in
__init__
    self.get_info_from_sysfs()
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/util/pci.py", line
1269, in
get_info_from_sysfs
    self.find_capability(0x11)
  File "/usr/lib/xen-4.1/bin/../lib/python/xen/util/pci.py", line
1236, in
find_capability
    ('Looped capability chain: %s' % self.name))
PciDeviceParseError: Looped capability chain: 0000:01:00.0
[2013-10-19 17:14:27 4238] INFO (SrvDaemon:220) Xend exited with status 1.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Searching for the error message (Looped capability chain: 0000:01:00.0) led to
this page:
http://martin.schinz.de/blog/2012/03/31/fixing-xen-daemon-on-a-laptop-with-
nvidia-optimus-graphics/
which contains a fix and a link to the same bug that was fixed on Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=767742

I edited the file /usr/lib/xen-4.1//lib/python/xen/util/pci.py as indicated in
these 2 pages

   * What was the outcome of this action?

Xen was then able to start.





-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500,
'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xen-utils-4.1 depends on:
ii  e2fslibs          1.42.8-1
ii  libc6             2.17-93
ii  libgnutls26       2.12.23-8
ii  libncurses5       5.9+20130608-1
ii  libpci3           1:3.2.0-3
ii  libtinfo5         5.9+20130608-1
ii  libuuid1          2.20.1-5.5
ii  libxen-4.1        4.1.4-4
ii  libxenstore3.0    4.3.0-3
ii  python            2.7.5-5
ii  python2.7         2.7.5-8
ii  xen-utils-common  4.1.4-4
ii  zlib1g            1:1.2.8.dfsg-1

Versions of packages xen-utils-4.1 recommends:
ii  bridge-utils                                   1.5-6
pn  qemu-keymaps                                   <none>
pn  qemu-utils                                     <none>
ii  xen-hypervisor-4.1-amd64 [xen-hypervisor-4.1]  4.1.4-4

Versions of packages xen-utils-4.1 suggests:
pn  xen-docs-4.1  <none>

-- no debconf information

Hello,

Same problem here with Optimus graphics, same patch made things work for
me too, 

ii  xen-utils-4.3            4.3.0-3           amd64             XEN
administrative tools


Samuel