[Xen-users] Re: [Xen-devel] Attempt to load kernel 2.6.40-4.fc15.x86_64 under Xen 4.1.1 on Fedora 15

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

1. Ubuntu's 11.10 kernel 3.0.0-7-generic  under stock Xen 4.1.1 (Ubuntu) works fine on the same box. ( miltibooting)

2. Video Radeon HD4650.  Xen 4.0.1 & 2.6.32.X worked fine also.

Boris.


--- On Tue, 8/2/11, Pasi Kärkkäinen <pasik@xxxxxx> wrote:

From: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] Attempt to load kernel 2.6.40-4.fc15.x86_64 under Xen 4.1.1 on Fedora 15
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Ian Campbell" <Ian.Campbell@xxxxxxxxxx>, "jim burns" <jim_burn@xxxxxxxxxxxxx>, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>, "M A Young" <m.a.young@xxxxxxxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Date: Tuesday, August 2, 2011, 3:55 PM

On Tue, Aug 02, 2011 at 12:37:19PM -0700, Boris Derzhavets wrote:
>    After yum install xen my environment on F15 is :-
>
>    [root@fedora15 ~]# uname -a
>    Linux fedora15 2.6.40-4.fc15.x86_64 #1 SMP Fri Jul 29 18:46:53 UTC 2011
>    x86_64 x86_64 x86_64 GNU/Linux
>
>    [root@fedora15 ~]# rpm -qa|grep xen
>    xen-runtime-4.1.1-2.fc15.x86_64
>    xen-libs-4.1.1-2.fc15.x86_64
>    xen-4.1.1-2.fc15.x86_64
>    xen-licenses-4.1.1-2.fc15.x86_64
>    xen-hypervisor-4.1.1-2.fc15.x86_64
>
>    Attempt to load via grub entry :-
>
>    title Xen 4.1.1 Fedora (2.6.40-4.fc15.x86_64)
>            root (hd1,0)
>            kernel  /xen-4.1.1.gz
>            module  /vmlinuz-2.6.40-4.fc15.x86_64 ro
>    root=/dev/mapper/vg_fedora15-lv_root nomodeset  LANG=en_US.UTF-8
>    SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb
>            module  /initramfs-2.6.40-4.fc15.x86_64.img
>
>    is just the same as with rebuilt  kernel 3.0.0-1.fc15.x86_64 . I've
>    already done it.
>
>    Black screen and no GDM login screen.
>

3.0.0 does not yet have vga text console support,
although kms should work at least on some graphics cards.

Try setting up a serial console and see where it fails / what it's doing.

-- Pasi


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users