Re: [Xen-users] HVM help please - wrong GRUB entry?

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Tue, 2012-06-26 at 22:26 +0100, Shane Johnson wrote:
> On Tue, Jun 26, 2012 at 3:10 PM, Alexandre Kouznetsov <alk@xxxxxxxxxx> wrote:
> > Hello.
> >
> > Can you please show your grub.cfg, and the output of "ls -l /boot"?
> > Specify what section of your grub.cfg is used when the "not an ELF binary"
> > error occur.
> >
> > --
> > Alexandre Kouznetsov
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxx
> > http://lists.xen.org/xen-users
> 
> ls -l /boot
> -rw-r--r-- 1 root root  2007679 Jun  3 16:44 System.map-3.2.0-0.bpo.2-amd64
> -rw-r--r-- 1 root root  2024845 Jun  3 17:15 System.map-3.2.0-0.bpo.2-rt-amd64
> -rw-r--r-- 1 root root  2052633 Jun 21 15:02 System.map-3.2.18
> -rw-r--r-- 1 root root   129015 Jun  3 16:44 config-3.2.0-0.bpo.2-amd64
> -rw-r--r-- 1 root root   128580 Jun  3 17:15 config-3.2.0-0.bpo.2-rt-amd64
> -rw-r--r-- 1 root root   128623 Jun 21 13:21 config-3.2.18
> drwxr-xr-x 3 root root     4096 Jun 26 14:04 grub
> -rw-r--r-- 1 root root 11186911 Jun 25 16:13 initrd.img-3.2.0-0.bpo.2-amd64
> -rw-r--r-- 1 root root 11305992 Jun 25 16:13 initrd.img-3.2.0-0.bpo.2-rt-amd64
> -rw-r--r-- 1 root root 11133522 Jun 25 16:21 initrd.img-3.2.18
> -rw-r--r-- 1 root root  2695559 Jun 25 16:18 
> initrd.img-vmlinuz-3.2.18-xen-amd64
> -rw-r--r-- 1 root root  2846608 Jun  3 16:41 vmlinuz-3.2.0-0.bpo.2-amd64
> -rw-r--r-- 1 root root  2895120 Jun  3 17:13 vmlinuz-3.2.0-0.bpo.2-rt-amd64
> -rw-r--r-- 1 root root  2937200 Jun 26 14:08 vmlinuz-3.2.18
> -rw-r--r-- 1 root root 11733424 Jun 26 14:07 vmlinuz-3.2.18-new
> -rw-r--r-- 1 root root   678554 Jun  9  2011 xen-4.0-amd64.gz
> 
> Entry that causes panic -

Is it just this one or are others faulty too?

Do the bpo kernels work? What about the 2.6.32-xen kernel from Squeeze
proper (as an experiment).

I think you can ignore any concerns about pciback hiding here -- your
failure is well before that would make any difference.

[...]
>       module  /boot/vmlinuz-3.2.18 placeholder root=/dev/mapper/vg-base ro
> quiet xen-pciback.hide=(05.00.0)(05:00.1)

What does
        file /boot/vmlinuz-3.2.18 
say?

What about this using the attached bzexplode:
        ./bzexplode /boot/vmlinuz-3.2.18 | file -

and then, depending on the type of compression that reports:
        ./bzexplode /boot/vmlinuz-3.2.18 | zcat | file -

(exchange zcat for the appropriate FOOcat, although if it isn't gzip
then that would be a good thing to fix first).

>       echo    'Loading initial ramdisk ...'
>       module  /boot/initrd.img-3.2.18
> 
> Full boot.cfg attached.
>

Attachment: bzexplode.c
Description: Text Data

Attachment: bzexplode
Description: application/executable

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users