Re: Bugs in 2.6.31.12-pvops

[Jeremy Fitzhardinge <jeremy@goop.org>]

On 04/02/2010 06:11 AM, Carsten Schiers wrote:
> Hi,
>
> honestly, I am a bit unsure, whether what I do is correct. I hg cloned
> current xen-4.0-testing,
> which will build the 2.6.31-12 kernel out of the box. I build that
> kernel and let in run on my
> Xen 3.4.1 hypervisor. config was what approximately comes with default
> values, because I have
> not a lot of knowledge with configs.
>
> Kernel started with one WARNING message:
>
> [    0.000999] WARNING: at
> /usr/src/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/arch/x86/kernel/apic
> /apic.c:247 native_apic_write_dummy+0x2d/0x39()
> [    0.000999] Modules linked in:
> [    0.000999] Pid: 0, comm: swapper Not tainted 2.6.31.12pvops-686 #4
> [    0.000999] Call Trace:
> [    0.000999]  [<c1038129>] ? native_apic_write_dummy+0x2d/0x39
>    

That's just a spurious warning; you can safely ignore it.

> BTW: Can someone please tell me how to test xen/stable-2.6.32.x? Is that
> by changing in the mk.linux-2.6-pvops xen/master
> into 2.6.32.x?
>
> Which one should I use for testing?
>    

Use xen/stable-2.6.32.x.  You can easily switch to it by doing:

$ cd linux-2.6-pvops.git
$ git checkout xen/stable-2.6.32.x
$ git pull

and rebuild.  It will probably ask you some config questions to update 
your config for the new kernel; choose the defaults unless there's 
something you specifically want to change.  Use "git pull" to update 
subsequently.

     J