[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#594986: marked as done (xen-linux-system-2.6.32-5-xen-686: Can't find hypervisor information in sysfs!)

Your message dated Tue, 31 Aug 2010 11:33:15 +0200
with message-id <20100831093315.GB3176@wavehammer.waldi.eu.org>
and subject line Re: Bug#594986: xen-linux-system-2.6.32-5-xen-686: Can't find hypervisor information in sysfs!
has caused the Debian Bug report #594986,
regarding xen-linux-system-2.6.32-5-xen-686: Can't find hypervisor information in sysfs!
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@bugs.debian.org
immediately.)


-- 
594986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594986
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xen-linux-system-2.6.32-5-xen-686
Version: 2.6.32-20
Severity: important

Hi,

# xm new --help_config
WARNING!  Can't find hypervisor information in sysfs!

# uname -a 
Linux mysqueeze-2 2.6.32-5-xen-686 #1 SMP Thu Aug 12 18:09:47 UTC 2010 i686 GNU/Linux

This is the same bug that:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580500

In that bug you comment:
"
> [    0.000000] Booting paravirtualized kernel on bare hardware

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

This is the same message which appear in my machine in syslog (I'm attaching dmesg output).

Maybe dropping a note in /usr/share/doc/xen*/README.Debian would be a good idea about how to solve this issue.

In my environment (cleaner squeeze install), installing xen-linux-system-2.6.32-5-xen-686 adds 4 boot entries to grub menu.

First entry (default entry) will give me this message error. But if I boot with third entry (which talk about booting xen kernel and 4.0 xen flavour) then xm commands start working, but the same message (Booting paravirtualized kernel on bare hardware) is shown too in dmesg.

So, which is the "user error" in this case ?

Thank you very much!

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

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

Versions of packages xen-linux-system-2.6.32-5-xen-686 depends on:
ii  linux-image-2.6.32-5-xen-686 2.6.32-20   Linux 2.6.32 for modern PCs, Xen d
ii  xen-hypervisor-4.0-i386 [xen 4.0.1~rc6-1 The Xen Hypervisor on i386

xen-linux-system-2.6.32-5-xen-686 recommends no packages.

xen-linux-system-2.6.32-5-xen-686 suggests no packages.

-- no debconf information

Attachment: dmesg-xen.gz
Description: GNU Zip compressed data


--- End Message ---
--- Begin Message --- 
On Tue, Aug 31, 2010 at 10:45:22AM +0200, Javier Barroso wrote:
> "
> > [    0.000000] Booting paravirtualized kernel on bare hardware
> The kernel does not run on Xen. Closing as user error.
> "
> This is the same message which appear in my machine in syslog (I'm attaching dmesg output).

So you are not running on Xen.

> Maybe dropping a note in /usr/share/doc/xen*/README.Debian would be a good idea about how to solve this issue.

Which problem? That you can't read what Grub wants to tell you?

> First entry (default entry) will give me this message error. But if I boot with third entry (which talk about booting xen kernel and 4.0 xen flavour) then xm commands start working, but the same message (Booting paravirtualized kernel on bare hardware) is shown too in dmesg.

No, it looks more like this in the correct case.
| [    0.000000] Booting paravirtualized kernel on Xen
| [    0.000000] Xen version: 4.0.1-rc3 (preserve-AD) (dom0)

Bastian

-- 
... The prejudices people feel about each other disappear when they get
to know each other.
		-- Kirk, "Elaan of Troyius", stardate 4372.5

--- End Message ---
Reply to: