Pkg xen devel - May 2010 - Bug#580500: xen-hypervisor-3.4-i386: Hypervisor fails to populate sysfs, causing xend to fail

Package: xen-hypervisor-3.4-i386
Version: 3.4.3~rc3-2
Severity: important
Tags: sid

After booting into the xen kernel, xm cannot run because xend is not running
(the sysfs hypervisor is not populated)

# dpkg -l | grep xen
ii  libc6-xen                                                2.10.2-6
GNU C Library: Shared libraries [Xen version]
ii  libxenstore3.0                                           3.4.3~rc3-2
Xenstore communications library for Xen
ii  linux-headers-2.6.32-5-common-xen                        2.6.32-12
Common header files for Linux 2.6.32-5-xen
ii  linux-headers-2.6.32-5-xen-686                           2.6.32-12
Header files for Linux 2.6.32-5-xen-686
ii  linux-image-2.6.32-5-xen-686                             2.6.32-12
Linux 2.6.32 for modern PCs, Xen dom0 support
ii  nvidia-kernel-2.6.32-5-xen-686                           190.53-4+2.6.32-12
NVIDIA binary kernel module for Linux 2.6.32-5-xen-686
ii  xen-docs-3.4                                             3.4.3~rc3-2
Documentation for Xen
ii  xen-hypervisor-3.4-i386                                  3.4.3~rc3-2
The Xen Hypervisor on i386
ii  xen-linux-system-2.6.32-5-xen-686                        2.6.32-12
Xen system with Linux 2.6.32 on modern PCs
rc  xen-shell                                                1.8-3
Console based Xen administration utility
ii  xen-utils-3.4                                            3.4.3~rc3-2
XEN administrative tools
ii  xen-utils-common                                         3.4.2-4
XEN administrative tools - common files
ii  xenstore-utils                                           3.4.3~rc3-2
Xenstore utilities for Xen
ii  xenwatch                                                 0.5.4-2
Virtualization utilities, mostly for Xen


# uname -r
2.6.32-5-xen-686


# xm list
WARNING!  Can't find hypervisor information in sysfs!
Error: Unable to connect to xend: No such file or directory. Is xend running?


# xend
WARNING!  Can't find hypervisor information in sysfs!
ERROR Internal error: Could not obtain handle on privileged command interface
(2 = No such file or directory)
Traceback (most recent call last):
  File "/usr/lib/xen-default/bin/xend", line 38, in <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib/xen-3.4/lib/python/xen/xend/server/SrvDaemon.py",
line 26, in
<module>
    import relocate
  File "/usr/lib/xen-3.4/lib/python/xen/xend/server/relocate.py", line
28, in
<module>
    from xen.xend import XendDomain
  File "/usr/lib/xen-3.4/lib/python/xen/xend/XendDomain.py", line 35,
in
<module>
    from xen.xend import XendOptions, XendCheckpoint, XendDomainInfo
  File "/usr/lib/xen-3.4/lib/python/xen/xend/XendCheckpoint.py", line
20, in
<module>
    from xen.xend import balloon, sxp, image
  File "/usr/lib/xen-3.4/lib/python/xen/xend/image.py", line 46, in
<module>
    xc = xen.lowlevel.xc.xc()
xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain
handle on
privileged command interface (2 = No such file or directory)')



-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (800, 'testing'), (700,
'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-xen-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

xen-hypervisor-3.4-i386 depends on no packages.

Versions of packages xen-hypervisor-3.4-i386 recommends:
ii  xen-utils-3.4                3.4.3~rc3-2 XEN administrative tools

Versions of packages xen-hypervisor-3.4-i386 suggests:
ii  xen-docs-3.4                 3.4.3~rc3-2 Documentation for Xen

-- no debconf information

On Thu, May 06, 2010 at 07:24:32AM -0500, QuadCEM wrote:
> After booting into the xen kernel, xm cannot run because xend is not
running
> (the sysfs hypervisor is not populated)
Please show the complete kernel log.

Bastian

-- 
Murder is contrary to the laws of man and God.
		-- M-5 Computer, "The Ultimate Computer", stardate 4731.3

I've attached the kernel log from the most recent session
-------------- next part --------------
A non-text attachment was scrubbed...
Name: log.log
Type: text/x-log
Size: 48463 bytes
Desc: not available
URL:
<http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20100506/5ff7e17c/attachment-0001.bin>

Your message dated Fri, 7 May 2010 10:25:47 +0200
with message-id <20100507082547.GA20055 at wavehammer.waldi.eu.org>
and subject line Re: [Pkg-xen-devel] Bug#580500: xen-hypervisor-3.4-i386:
Hypervisor fails to populate sysfs, causing xend to fail
has caused the Debian Bug report #580500,
regarding xen-hypervisor-3.4-i386: Hypervisor fails to populate sysfs, causing
xend to fail
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
580500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580500
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: QuadCEM <quadcem at gmail.com>
Subject: xen-hypervisor-3.4-i386: Hypervisor fails to populate sysfs,
 causing xend to fail
Date: Thu, 06 May 2010 07:24:32 -0500
Size: 5084
URL:
<http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20100507/98d1f47c/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Bastian Blank <waldi at debian.org>
Subject: Re: [Pkg-xen-devel] Bug#580500: xen-hypervisor-3.4-i386:
	Hypervisor fails to populate sysfs, causing xend to fail
Date: Fri, 7 May 2010 10:25:47 +0200
Size: 1660
URL:
<http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20100507/98d1f47c/attachment-0001.eml>