On Wed, Feb 04, 2009 at 06:29:57PM +0200, Pasi Kärkkäinen wrote: > On Wed, Feb 04, 2009 at 01:35:23PM +0100, Jan ONDREJ (SAL) wrote: > > On Wed, Feb 04, 2009 at 01:29:39PM +0100, Gerd Hoffmann wrote: > > > Jan ONDREJ (SAL) wrote: > > > > [root@note ~]# file /boot/xen-3.3.gz /boot/xen/vmlinux /boot/xen/initrd.img /boot/xen/bzImage > > > > /boot/xen-3.3.gz: gzip compressed data, from Unix, last modified: Tue Feb 3 12:36:39 2009, max compression > > > > /boot/xen/vmlinux: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped > > > > > > "stripped". This probably is the problem. > > > > > > > /boot/xen/initrd.img: gzip compressed data, from Unix, last modified: Wed Feb 4 12:00:01 2009, max compression > > > > /boot/xen/bzImage: Linux kernel x86 boot executable RO-rootFS, swap_dev 0x2, Normal VGA > > > > > > Try this one instead of vmlinux (unstripped vmlinux should work too). > > > > Already tryed both of them. Stripped, unstripped vmlinux, gzip compressed > > vmlinux, bzImage. Always same problem. > > > > I've been using gzipped vmlinux pv_ops dom0 kernel successfully. > > I still haven't tried that new bzImage support .. will try that today or tomorrow. > I can confirm that bzImage pv_ops dom0 kernels boot OK with xen 3.3.1-3. I'm running on x86-32 (PAE) and I was using arch/x86/boot/bzImage from 2.6.29-rc3-tip as a dom0 kernel. -- Pasi -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
