Fedora xen - Feb 2009 - bzImage dom0 kernel support in latest rawhide Xen packages

Hello!

For those interested in testing pv_ops dom0 kernels it seems latest Xen
packages in rawhide contain bzImage dom0 kernel support in Xen hypervisor.


rawhide report: 20090203 changes


xen-3.3.1-3.fc11
----------------
* Tue Feb  3 17:00:00 2009 Gerd Hoffmann <kraxel@redhat.com> - 3.3.1-3
- backport bzImage support for dom0 builder.      


-- Pasi

On Tue, Feb 03, 2009 at 10:18:53PM -0200, Itamar Reis Peixoto
wrote:
> I need to configure something to boot dom0 ?
> 
Well you need to have dom0 kernel.. (there''s no dom0 capable kernel in
fedora/rawhide yet, so you need to compile/build/get one yourself).

Nothing to configure really.. just configure grub.conf in the normal way to
boot Xen and dom0 kernel. 

-- Pasi
> 
> On Tue, Feb 3, 2009 at 6:24 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> > Hello!
> >
> > For those interested in testing pv_ops dom0 kernels it seems latest
Xen
> > packages in rawhide contain bzImage dom0 kernel support in Xen
hypervisor.
> >
> >
> > rawhide report: 20090203 changes
> >
> >
> > xen-3.3.1-3.fc11
> > ----------------
> > * Tue Feb  3 17:00:00 2009 Gerd Hoffmann <kraxel@redhat.com> -
3.3.1-3
> > - backport bzImage support for dom0 builder.
> >
> >
> > -- Pasi
> >
> > _______________________________________________
> > Fedora-virt mailing list
> > Fedora-virt@redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-virt
> >
> 
> 
> 
> -- 
> ------------
> 
> Itamar Reis Peixoto
> 
> e-mail/msn: itamar@ispbrasil.com.br
> sip: itamar@ispbrasil.com.br
> skype: itamarjp
> icq: 81053601
> +55 11 4063 5033
> +55 34 3221 8599

> > On Tue, Feb 3, 2009 at 6:24 PM, Pasi Kärkkäinen <pasik@iki.fi>
wrote:
> > > Hello!
> > >
> > > For those interested in testing pv_ops dom0 kernels it seems
latest Xen
> > > packages in rawhide contain bzImage dom0 kernel support in Xen
hypervisor.
I am trying to compile current 2.6.29 kernel (as described here:
http://wiki.xensource.com/xenwiki/XenParavirtOps), but without success yet.

When trying to boot ./vmlinux ro ./arch/x86/boot/bzImage (also with
xen-hypervisor-3.3.1-3.fc11) I still get something like this:

(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_xen_note_check: ERROR: Will only load images built for the generic
loader or Linux images

My grub.conf entry:
title Xen TEST
        root (hd0,0)
        kernel /boot/xen-3.3.gz noreboot
        module /boot/xen/vmlinux root=/dev/sda1 ro earlyprintk=xen pci=nomsi
        module /boot/xen/initrd.img

[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
/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
[root@note ~]# rpm -q xen-hypervisor
xen-hypervisor-3.3.1-3.fc11.i386
[root@note ~]# 

My bzImage boots well with modified grub to boot it as "kernel" and
not
using xen-3.3 loader.

What I am doing wrong?
Can sombody send me kernel.config file for 2.6.29, something similar to old
kernel-xen rpm package''s config?

			SAL

Jan ONDREJ (SAL) wrote:
>>> On Tue, Feb 3, 2009 at 6:24 PM, Pasi Kärkkäinen
<pasik@iki.fi> wrote:
>>>> Hello!
>>>>
>>>> For those interested in testing pv_ops dom0 kernels it seems
latest Xen
>>>> packages in rawhide contain bzImage dom0 kernel support in Xen
hypervisor.
> 
> I am trying to compile current 2.6.29 kernel (as described here:
> http://wiki.xensource.com/xenwiki/XenParavirtOps), but without success yet.
> 
> When trying to boot ./vmlinux ro ./arch/x86/boot/bzImage (also with
> xen-hypervisor-3.3.1-3.fc11) I still get something like this:
> 
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) elf_xen_note_check: ERROR: Will only load images built for the
generic
> loader or Linux images
> 
> My grub.conf entry:
> title Xen TEST
>         root (hd0,0)
>         kernel /boot/xen-3.3.gz noreboot
>         module /boot/xen/vmlinux root=/dev/sda1 ro earlyprintk=xen
pci=nomsi
>         module /boot/xen/initrd.img
> [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).

HTH
  Gerd

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.

			SAL

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.
Hmm.  Works for me.  x86_64 box boots up fine (until the not-yet fixed
storage issues kick in, see xen-devel).  Old i386 laptop has an early
kernel crash (probably due to lack of an io-apic, the pv_ops kernel
reportly can''t deal with that very well).  The bootup passes the point
where the dom0 domain builder parses the guest kernel though.  32bit
config attached.

HTH,
  Gerd

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.

-- Pasi

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

any chance to someone build a rpm with dom0 available for testing ?


> 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-virt mailing list
> Fedora-virt@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-virt
>


-- 
------------

Itamar Reis Peixoto

e-mail/msn: itamar@ispbrasil.com.br
sip: itamar@ispbrasil.com.br
skype: itamarjp
icq: 81053601
+55 11 4063 5033
+55 34 3221 8599

On Thu, 5 Feb 2009, Itamar Reis Peixoto wrote:
> any chance to someone build a rpm with dom0 available for testing ?
I am not convinced that dom0 support is really stable enough to do that 
yet, because some key aspects are broken such as some hard disk 
support, and the code is still rather a moving target which doesn''t
always
build.

 	Michael Young

On Thu, Feb 05, 2009 at 12:23:27PM +0000, M A Young
wrote:
> On Thu, 5 Feb 2009, Itamar Reis Peixoto wrote:
>
>> any chance to someone build a rpm with dom0 available for testing ?
I am trying to create one, but without success yet.

I have an 2.6.29-rc3-tip kernel with dom0 support, it now can boot using
xen-3.3.gz, but immediatelly after boot my fonts are gone. I don''t know
what
to do without console. My cursor is sometimes moving, just I can''t
control
it (may be console and keyboard are not working). Can somebody help me, what
I am doing wrong? My last functional compiled kernel was 1.3.XX and it is
some years ago. :)
> I am not convinced that dom0 support is really stable enough to do that  
> yet, because some key aspects are broken such as some hard disk support, 
> and the code is still rather a moving target which doesn''t always
build.
Right.

When trying to compile 2.6.29-rc3+xen, I need to turn off xen*frontentds
and xen*backend drivers have to be compiled into kernel, not as modules.
After this I have a functional kernel, but after booting with xen-3.3.gz, my
screen is blank.

		SAL

On Thu, Feb 05, 2009 at 01:37:06PM +0100, Jan ONDREJ (SAL)
wrote:
> On Thu, Feb 05, 2009 at 12:23:27PM +0000, M A Young wrote:
> > On Thu, 5 Feb 2009, Itamar Reis Peixoto wrote:
> >
> >> any chance to someone build a rpm with dom0 available for testing
?
> 
> I am trying to create one, but without success yet.
> 
> I have an 2.6.29-rc3-tip kernel with dom0 support, it now can boot using
> xen-3.3.gz, but immediatelly after boot my fonts are gone. I don''t
know what
> to do without console. My cursor is sometimes moving, just I can''t
control
> it (may be console and keyboard are not working). Can somebody help me,
what
> I am doing wrong? My last functional compiled kernel was 1.3.XX and it is
> some years ago. :)
> 
> > I am not convinced that dom0 support is really stable enough to do
that
> > yet, because some key aspects are broken such as some hard disk
support,
> > and the code is still rather a moving target which doesn''t
always build.
> 
> Right.
> 
> When trying to compile 2.6.29-rc3+xen, I need to turn off xen*frontentds
> and xen*backend drivers have to be compiled into kernel, not as modules.
> After this I have a functional kernel, but after booting with xen-3.3.gz,
my
> screen is blank.
> 
I haven''t gotten the pv_ops dom0 kernel VGA text console to work at all
yet..

I''ve been using serial console.

I guess fixing the console would be the next thing to do after disk problems
are fixed:)

-- Pasi

On Fri, Feb 06, 2009 at 12:37:42AM +0000, M A Young
wrote:
> On Thu, 5 Feb 2009, Pasi Kärkkäinen wrote:
> 
> >On Thu, Feb 05, 2009 at 01:37:06PM +0100, Jan ONDREJ (SAL) wrote:
> >>When trying to compile 2.6.29-rc3+xen, I need to turn off
xen*frontentds
> >>and xen*backend drivers have to be compiled into kernel, not as
modules.
> >>After this I have a functional kernel, but after booting with
xen-3.3.gz,
> >>my
> >>screen is blank.
> >>
> >
> >I haven''t gotten the pv_ops dom0 kernel VGA text console to
work at all
> >yet..
> >
> >I''ve been using serial console.
> 
> I have the VGA console printing boot messages from the kernel with the 
> configuration
> 
> title xen test
> 	root (hd0,5)
> 	kernel /xen-3.3.gz
> 	module /vmlinuz-2.6.29-rc3-tip ro 
> 	root=UUID=00000000-0000-0000-0000-000000000000 single pci=nomsi 
> 	maxcpus=1
> 	module /initrd-2.6.29-rc3-tip.img
> 
> though it crashes before it gets as far as a prompt. This is x86_64. 
> However I have another machine that goes blank after the XEN output 
> (though I am not sure I have tried it with precisely the same options) 
> which is an i686. The difference might be nothing to do with the boot 
> options though, and could relate to graphics cards or precisely how 
> plymouth is set up.
> 
Yeah, that''s my problem too.. VGA text console goes blank when dom0
kernel is
booted.. Xen hypervisor messages are displayed OK (before the dom0 kernel).

I''m running also 32bit Xen and dom0.

-- Pasi

Pasi Kärkkäinen wrote:
> Yeah, that''s my problem too.. VGA text console goes blank when
dom0 kernel is
> booted.. Xen hypervisor messages are displayed OK (before the dom0 kernel).
> 
> I''m running also 32bit Xen and dom0.
Noticed that the laptop shows dom0 kernel messages when booting xen with
"vga=gfx-1024x768x16".  Text mode stays blank for me too.

cheers,
  Gerd