This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] XEN BUG i387.c159 at XEN4.01 on debian squeeze

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] XEN BUG i387.c159 at XEN4.01 on debian squeeze
From: Lukrativ - Armin Krämer <a.kraemer@xxxxxxxxxxxx>
Date: Fri, 1 Oct 2010 16:13:47 +0200
Delivery-date: Fri, 08 Oct 2010 08:38:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: ActhcvB4alajn8EgQkSnQeOqBHPRSQ==


we´ve got a bad problem here. We installed a new server with debian squeeze sw-raid and lvm. We´ve installed the the actual xen-linux-system-2.6.32-5-xen-amd64” system with grub2 but get an XEN BUG. We´ve tried alot, tested grub-legacy version but cannot get the XEN kernel to boot up.

The XEN BUG occurs a  second after grub boots the kernel and there are no outputs at the serial console with debugging on.

It only shows : xen BUG i387.c159 and reboots ore stays there if we add “noreboot” to the configuration parameter.

Here´s the grub config, thats sadly all i have:

          insmod raid

          insmod mdraid

          insmod part_msdos

          insmod part_msdos

          insmod ext2

            Insmod lvm

          set root='(md0)'

          search --no-floppy --fs-uuid --set 58aa026a-7737-4e68-b7f3-1e3f2b8e89d0

          echo    'Loading Linux 2.6.32-5-xen-amd64 ...'

          multiboot       /xen-4.0-amd64.gz placeholder

          module  /vmlinuz-2.6.32-5-xen-amd64 placeholder root=/dev/mapper/vg1--system-lv1--sys--root ro single

          echo    'Loading initial ramdisk ...'

          module  /initrd.img-2.6.32-5-xen-amd64


May someone can give me an answer what causes this?


Greetings Armin



Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>