Debian Bug report logs - #580500
xen-hypervisor-3.4-i386: Hypervisor fails to populate sysfs, causing xend to fail

Package: grub-common; Maintainer for grub-common is GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>; Source for grub-common is src:grub2.

Reported by: QuadCEM <quadcem@gmail.com>

Date: Thu, 6 May 2010 12:27:02 UTC

Severity: important

Tags: jessie, sid

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, quadcem@gmail.com, quadcem@gmail.com, Debian Xen Team <pkg-xen-devel@lists.alioth.debian.org>:
Bug#580500; Package xen-hypervisor-3.4-i386. (Thu, 06 May 2010 12:27:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to QuadCEM <quadcem@gmail.com>:
New Bug report received and forwarded. Copy sent to quadcem@gmail.com, quadcem@gmail.com, Debian Xen Team <pkg-xen-devel@lists.alioth.debian.org>. (Thu, 06 May 2010 12:27:05 GMT) Full text and rfc822 format available.

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

From: QuadCEM <quadcem@gmail.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: xen-hypervisor-3.4-i386: Hypervisor fails to populate sysfs, causing xend to fail
Date: Thu, 06 May 2010 07:24:32 -0500
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




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Xen Team <pkg-xen-devel@lists.alioth.debian.org>:
Bug#580500; Package xen-hypervisor-3.4-i386. (Thu, 06 May 2010 13:51:06 GMT) Full text and rfc822 format available.

Acknowledgement sent to Bastian Blank <waldi@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Xen Team <pkg-xen-devel@lists.alioth.debian.org>. (Thu, 06 May 2010 13:51:06 GMT) Full text and rfc822 format available.

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

From: Bastian Blank <waldi@debian.org>
To: QuadCEM <quadcem@gmail.com>, 580500@bugs.debian.org
Subject: Re: [Pkg-xen-devel] Bug#580500: xen-hypervisor-3.4-i386: Hypervisor fails to populate sysfs, causing xend to fail
Date: Thu, 6 May 2010 15:47:25 +0200
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




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Xen Team <pkg-xen-devel@lists.alioth.debian.org>:
Bug#580500; Package xen-hypervisor-3.4-i386. (Fri, 07 May 2010 04:51:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to QuadCEM <quadcem@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Xen Team <pkg-xen-devel@lists.alioth.debian.org>. (Fri, 07 May 2010 04:51:03 GMT) Full text and rfc822 format available.

Message #15 received at 580500@bugs.debian.org (full text, mbox):

From: QuadCEM <quadcem@gmail.com>
To: 580500@bugs.debian.org
Subject: xen-hypervisor-3.4-i386: Hypervisor fails to populate sysfs, causing xend to fail
Date: Thu, 06 May 2010 23:48:58 -0500
[Message part 1 (text/plain, inline)]
I've attached the kernel log from the most recent session
[log.log (text/x-log, attachment)]

Reply sent to Bastian Blank <waldi@debian.org>:
You have taken responsibility. (Fri, 07 May 2010 08:27:11 GMT) Full text and rfc822 format available.

Notification sent to QuadCEM <quadcem@gmail.com>:
Bug acknowledged by developer. (Fri, 07 May 2010 08:27:11 GMT) Full text and rfc822 format available.

Message #20 received at 580500-done@bugs.debian.org (full text, mbox):

From: Bastian Blank <waldi@debian.org>
To: 580500-done@bugs.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
On Thu, May 06, 2010 at 11:48:58PM -0500, QuadCEM wrote:
> [    0.000000] Booting paravirtualized kernel on bare hardware

The kernel does not run on Xen. Closing as user error.

Bastian




Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Sat, 05 Jun 2010 07:30:06 GMT) Full text and rfc822 format available.

Bug unarchived. Request was from Micah Anderson <micah@riseup.net> to control@bugs.debian.org. (Thu, 18 Nov 2010 17:33:10 GMT) Full text and rfc822 format available.

Did not alter fixed versions and reopened. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Thu, 18 Nov 2010 17:33:10 GMT) Full text and rfc822 format available.

Bug reassigned from package 'xen-hypervisor-3.4-i386' to 'grub-common'. Request was from Micah Anderson <micah@riseup.net> to control@bugs.debian.org. (Thu, 18 Nov 2010 17:33:11 GMT) Full text and rfc822 format available.

Bug No longer marked as found in versions xen-3/3.4.3~rc3-2. Request was from Micah Anderson <micah@riseup.net> to control@bugs.debian.org. (Thu, 18 Nov 2010 17:33:11 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#580500; Package grub-common. (Thu, 10 Feb 2011 15:24:06 GMT) Full text and rfc822 format available.

Acknowledgement sent to Heikki Levanto <heikki@indexdata.dk>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>. (Thu, 10 Feb 2011 15:24:07 GMT) Full text and rfc822 format available.

Message #35 received at 580500@bugs.debian.org (full text, mbox):

From: Heikki Levanto <heikki@indexdata.dk>
To: 580500@bugs.debian.org
Subject: Same here
Date: Thu, 10 Feb 2011 16:03:03 +0100
I have the same problem. 

I had a box running xen under Debian/Lenny (fairly plain installation). Upgraded
to squeeze today, and run into the same problem. Noticed that xen-3 was not upgraded
to xen-4. 
I uninstalled 
  xen-hypervisor-3.2-1-amd64 xen-linux-system-2.6.26-2-xen-amd64,
and installed 
  xen-linux-system-2.6-xen-amd64 linux-image-2.6.32-5-xen-amd64 
  xen-hypervisor-4.0-amd64 xen-linux-system-2.6-xen-amd64 
  xen-linux-system-2.6.32-5-xen-amd64 xen-utils-4.0
I also checked that any package that remotely sounds like xen has not version 4.


I respectfully submit that this is not an 'user error', but a problem with debian
upgrade scripts. Maybe somehow related to upgrading to grub2 at the same time, I don't
know.

-- 
Heikki Levanto    heikki at indexdata dot dk   "In Murphy We Turst"




Information forwarded to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#580500; Package grub-common. (Fri, 11 Feb 2011 09:51:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Heikki Levanto <heikki@indexdata.dk>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>. (Fri, 11 Feb 2011 09:51:03 GMT) Full text and rfc822 format available.

Message #40 received at 580500@bugs.debian.org (full text, mbox):

From: Heikki Levanto <heikki@indexdata.dk>
To: 580500@bugs.debian.org
Subject: workaround
Date: Fri, 11 Feb 2011 10:49:29 +0100
The problem seems to be that grub2 wants to boot the machine into a regular
linux kernel, and not the xen hypervisor.

There is a workaround at 
  http://wiki.debian.org/Xen#XenonTesting.2BAC8-SqueezeandonUnstable.2BAC8-SidasDom0.2CtocreateamultitudeofDomU.27s    

In short it is 
  mv -i /etc/grub.d/10_linux /etc/grub.d/50_linux
  update-grub2

This makes it prefer the hypervisor.

Another way is to
  apt-get remove --purge grub2 grub-pc
  apt-get autoremove
  apt-get install grub-legacy
  grub-install
  update-grub

and reboot - not before you have done all the steps above!


-- 
Heikki Levanto    heikki at indexdata dot dk   "In Murphy We Turst"




Information forwarded to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#580500; Package grub-common. (Tue, 22 Feb 2011 15:30:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Heikki Levanto <heikki@indexdata.dk>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>. (Tue, 22 Feb 2011 15:30:03 GMT) Full text and rfc822 format available.

Message #45 received at 580500@bugs.debian.org (full text, mbox):

From: Heikki Levanto <heikki@indexdata.dk>
To: 580500@bugs.debian.org
Subject: Re: workaround
Date: Tue, 22 Feb 2011 15:55:43 +0100
On Fri, Feb 11, 2011 at 10:49:29AM +0100, Heikki Levanto wrote:
> The problem seems to be that grub2 wants to boot the machine into a regular
> linux kernel, and not the xen hypervisor.
> 
> There is a workaround at 
>   http://wiki.debian.org/Xen#XenonTesting.2BAC8-SqueezeandonUnstable.2BAC8-SidasDom0.2CtocreateamultitudeofDomU.27s    

> In short it is 
>   mv -i /etc/grub.d/10_linux /etc/grub.d/50_linux
>   update-grub2
> 
> This makes it prefer the hypervisor.

Actually, that will give problems next time you upgrade grub. If nothing else, do a
  echo "#moved to 50_linux" > /etc/grub.d/10_linux
so that apt will warn you before (re)establishing 10_linux.

It would be more correct to edit the default line in /etc/alternatives/grub to 
point to the hypervisor you want to start. That is also the place to set up
boot parameters for the hypervisor and for the kernel it boots dom0 in.

-- 
Heikki Levanto    heikki at indexdata dot dk   "In Murphy We Turst"




Added tag(s) jessie. Request was from Julien Cristau <jcristau@debian.org> to control@bugs.debian.org. (Thu, 18 Apr 2013 17:39:41 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Sat Apr 19 02:16:33 2014; Machine Name: beach.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.