[Xen-devel] Re: apic probe of 2.6.32.41 pv linux

[Jiageng Yu <yujiageng734@xxxxxxxxx>]

2011/5/28 Jeremy Fitzhardinge <jeremy@xxxxxxxx>:
> On 05/27/2011 02:29 AM, Jiageng Yu wrote:
>> I have updated the pv linux kernel from 2.6.32.40 to 2.6.32.41. I
>> found the generic_apic_probe always led to a kernel panic when I try
>> to make the minimal DomU kernel.
>>
>> The 2.6.32.41 pv linux use the new apic probe mechanism:
>>
>> static __init int xen_safe_probe(void) {
>> Â Â Â if (!xen_initial_domain())
>> Â Â Â Â Â Â Â return 0;
>> Â Â Â return 1;
>> }
>>
>> #ifdef CONFIG_XEN_DOM0
>> #define xen_initial_domain() Â(xen_pv_domain() && xen_start_info->flags
>> & SIF_INITDOMAIN)
>> #else Â/* !CONFIG_XEN_DOM0 */
>> #define xen_initial_domain() Â(0)
>> #endif    Â/* CONFIG_XEN_DOM0 */
>>
>>
>> If do not define the CONFIG_XEN_DOM0, xen_safe_probe will always
>> return 0 which causes the kernel panic. For the minimal DomU kernel,
>> the CONFIG_XEN_DOM0 is needless, and in this scenario, how to pass the
>> apic probe safely?
>
> Thanks for looking into this. ÂIn theory a minimal domU kernel should
> never have anything to do with APICs, since there are none present in a
> PV domain. ÂDo you have a stack backtrace for when it crashes?
>
> Thanks,
> Â ÂJ
>

Thanks, Jeremy. This is the panic output when starting the domU kernel:
_______________________________________________________
<0>Kernel panic - not syncing: Didn't find an APIC driver
Pid: 0, comm: swapper Not tainted 2.6.32.41 #1
Call Trace:
 [<c0123406>] ? panic+0x46/0x100
 [<c032a08d>] ? generic_apic_probe+0x6d/0x70
 [<c03220eb>] ? xen_pagetable_setup_done+0x6b/0x70
 [<c0323533>] ? setup_arch+0x483/0x
 [<c020305b>] ? dom0_write_console+0x1b/0x40990
 [<c0124077>] ? printk+0x47/0x60
 [<c031f67b>] ?  start_kernel+0x6b/0x2d0
 [<c0321516>] ? xen_start_kernel+0x396/0x3d0
_______________________________________________________

For debugging perpose, I insert xen_raw_console_write into printk, and
the dom0_write_console belongs to xen_raw_console_write function.

My config file is:
____________________________________________________
kernel = "/root/xen-unstable.hg/linux-stubdom/vmlinuz-ioemu"
ramdisk = "/root/xen-unstable.hg/linux-stubdom/ramdisk-ioemu"
memory = 32
name="stubdom"
vif=['bridge=eth0']
vnc=0;
vfb=['sdl=1']
____________________________________________________

The domU kernel config file is attached. I have cut the options about
backend drivers, dom0, and privileged_guest. So, there is no
CONFIG_XEN_DOM0 option when starting the domU kernel.

Thanks.

Attachment: linux-config-ioemu
Description: Binary data

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