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

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



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


Reply to: