I compiled a domU kernel, the source is from kernel.org, the version is 2.6.29.6. The domU kernel crashed on Xen 3.3.1. The dom0 kernel is 2.6.18.8 from xen.org. xm dmesg: (XEN) mm.c:1482:d95 Bad L1 flags 800000 (XEN) traps.c:437:d95 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=0000] (XEN) domain_crash_sync called from entry.S (XEN) Domain 95 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-3.3.1 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e033:[<ffffffff8100aa83>] (XEN) RFLAGS: 0000000000000282 EM: 1 CONTEXT: pv guest (XEN) rax: 00000000ffffffea rbx: 8000000000000161 rcx: 00000000017ff000 (XEN) rdx: 0000000000000000 rsi: 80000005f31da061 rdi: ffffffff8150f000 (XEN) rbp: ffffffff81483fa8 rsp: ffffffff81483f58 r8: 0000000000000000 (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 (XEN) r12: ffffffff8150f000 r13: 0000000000000200 r14: 0000000000002000 (XEN) r15: 0000000000000800 cr0: 000000008005003b cr4: 00000000000026b0 (XEN) cr3: 00000005f307a000 cr2: 0000000000000000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff81483f58: (XEN) 00000000017ff000 0000000000000000 ffffffff8100aa83 000000010000e030 (XEN) 0000000000010082 ffffffff81483f98 000000000000e02b ffffffff8100aa7f (XEN) 0000000000000200 0000000000000010 ffffffff81483ff8 ffffffff814b1268 (XEN) ffffffff8166f000 0000000000010000 0000000000000010 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 ffffffff815ec000 ffffffff815ed000 ffffffff815ee000 (XEN) ffffffff815ef000 ffffffff815f0000 ffffffff815f1000 ffffffff815f2000 (XEN) ffffffff815f3000 ffffffff815f4000 ffffffff815f5000 ffffffff815f6000 (XEN) ffffffff815f7000 ffffffff815f8000 ffffffff815f9000 ffffffff815fa000 (XEN) ffffffff815fb000 ffffffff815fc000 ffffffff815fd000 ffffffff815fe000 (XEN) ffffffff815ff000 ffffffff81600000 ffffffff81601000 ffffffff81602000 (XEN) ffffffff81603000 ffffffff81604000 ffffffff81605000 ffffffff81606000 (XEN) ffffffff81607000 ffffffff81608000 ffffffff81609000 ffffffff8160a000 (XEN) ffffffff8160b000 ffffffff8160c000 ffffffff8160d000 ffffffff8160e000 (XEN) ffffffff8160f000 ffffffff81610000 ffffffff81611000 ffffffff81612000 (XEN) ffffffff81613000 ffffffff81614000 ffffffff81615000 ffffffff81616000 (XEN) ffffffff81617000 ffffffff81618000 ffffffff81619000 ffffffff8161a000 (XEN) ffffffff8161b000 ffffffff8161c000 ffffffff8161d000 ffffffff8161e000 (XEN) ffffffff8161f000 ffffffff81620000 ffffffff81621000 ffffffff81622000 (XEN) ffffffff81623000 ffffffff81624000 ffffffff81625000 ffffffff81626000 xm info: [root@zf1 debian5.rashost.com]# xm info host : zf1.rashost.com release : 2.6.18.8-xen version : #2 SMP Wed May 13 10:22:26 CST 2009 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 1995 hw_caps : bfebfbff:20000800:00000000:00000140:040ce33d:00000000:00000001:00000000 virt_caps : hvm total_memory : 32766 free_memory : 22003 node_to_cpu : node0:0-3 node_to_memory : node0:22003 xen_major : 3 xen_minor : 3 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-44) cc_compile_by : zzh cc_compile_domain : rashost.com cc_compile_date : Fri May 1 16:47:47 CST 2009 xend_config_format : 4 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pasi Kärkkäinen
2009-Sep-04 11:34 UTC
Re: [Xen-users] vanilla kernel 2.6.29.6 crashes on xen 3.3.1
On Fri, Sep 04, 2009 at 05:01:47PM +0800, Zu wrote:> I compiled a domU kernel, the source is from kernel.org, the version is > 2.6.29.6. The domU kernel crashed on Xen 3.3.1. The dom0 kernel is 2.6.18.8 > from xen.org. >Have you tried with Xen 3.4.1 ? Also, have you tried vanilla 2.6.30.<latest> in domU? Is this AMD hardware? -- Pasi> xm dmesg: > (XEN) mm.c:1482:d95 Bad L1 flags 800000 > (XEN) traps.c:437:d95 Unhandled invalid opcode fault/trap [#6] on VCPU 0 > [ec=0000] > (XEN) domain_crash_sync called from entry.S > (XEN) Domain 95 (vcpu#0) crashed on cpu#0: > (XEN) ----[ Xen-3.3.1 x86_64 debug=n Not tainted ]---- > (XEN) CPU: 0 > (XEN) RIP: e033:[<ffffffff8100aa83>] > (XEN) RFLAGS: 0000000000000282 EM: 1 CONTEXT: pv guest > (XEN) rax: 00000000ffffffea rbx: 8000000000000161 rcx: 00000000017ff000 > (XEN) rdx: 0000000000000000 rsi: 80000005f31da061 rdi: ffffffff8150f000 > (XEN) rbp: ffffffff81483fa8 rsp: ffffffff81483f58 r8: 0000000000000000 > (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 > (XEN) r12: ffffffff8150f000 r13: 0000000000000200 r14: 0000000000002000 > (XEN) r15: 0000000000000800 cr0: 000000008005003b cr4: 00000000000026b0 > (XEN) cr3: 00000005f307a000 cr2: 0000000000000000 > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 > (XEN) Guest stack trace from rsp=ffffffff81483f58: > (XEN) 00000000017ff000 0000000000000000 ffffffff8100aa83 000000010000e030 > (XEN) 0000000000010082 ffffffff81483f98 000000000000e02b ffffffff8100aa7f > (XEN) 0000000000000200 0000000000000010 ffffffff81483ff8 ffffffff814b1268 > (XEN) ffffffff8166f000 0000000000010000 0000000000000010 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > (XEN) 0000000000000000 ffffffff815ec000 ffffffff815ed000 ffffffff815ee000 > (XEN) ffffffff815ef000 ffffffff815f0000 ffffffff815f1000 ffffffff815f2000 > (XEN) ffffffff815f3000 ffffffff815f4000 ffffffff815f5000 ffffffff815f6000 > (XEN) ffffffff815f7000 ffffffff815f8000 ffffffff815f9000 ffffffff815fa000 > (XEN) ffffffff815fb000 ffffffff815fc000 ffffffff815fd000 ffffffff815fe000 > (XEN) ffffffff815ff000 ffffffff81600000 ffffffff81601000 ffffffff81602000 > (XEN) ffffffff81603000 ffffffff81604000 ffffffff81605000 ffffffff81606000 > (XEN) ffffffff81607000 ffffffff81608000 ffffffff81609000 ffffffff8160a000 > (XEN) ffffffff8160b000 ffffffff8160c000 ffffffff8160d000 ffffffff8160e000 > (XEN) ffffffff8160f000 ffffffff81610000 ffffffff81611000 ffffffff81612000 > (XEN) ffffffff81613000 ffffffff81614000 ffffffff81615000 ffffffff81616000 > (XEN) ffffffff81617000 ffffffff81618000 ffffffff81619000 ffffffff8161a000 > (XEN) ffffffff8161b000 ffffffff8161c000 ffffffff8161d000 ffffffff8161e000 > (XEN) ffffffff8161f000 ffffffff81620000 ffffffff81621000 ffffffff81622000 > (XEN) ffffffff81623000 ffffffff81624000 ffffffff81625000 ffffffff81626000 > > > xm info: > [root@zf1 debian5.rashost.com]# xm info > host : zf1.rashost.com > release : 2.6.18.8-xen > version : #2 SMP Wed May 13 10:22:26 CST 2009 > machine : x86_64 > nr_cpus : 4 > nr_nodes : 1 > cores_per_socket : 4 > threads_per_core : 1 > cpu_mhz : 1995 > hw_caps : > bfebfbff:20000800:00000000:00000140:040ce33d:00000000:00000001:00000000 > virt_caps : hvm > total_memory : 32766 > free_memory : 22003 > node_to_cpu : node0:0-3 > node_to_memory : node0:22003 > xen_major : 3 > xen_minor : 3 > xen_extra : .1 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-44) > cc_compile_by : zzh > cc_compile_domain : rashost.com > cc_compile_date : Fri May 1 16:47:47 CST 2009 > xend_config_format : 4> _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2009-Sep-04 11:57 UTC
Re: [Xen-users] vanilla kernel 2.6.29.6 crashes on xen 3.3.1
On Fri, Sep 4, 2009 at 4:01 PM, Zu<zuzhihui@gmail.com> wrote:> I compiled a domU kernel, the source is from kernel.org, the version is > 2.6.29.6. The domU kernel crashed on Xen 3.3.1. The dom0 kernel is 2.6.18.8 > from xen.org.I''m using xenified 2.6.96 and vanilla 2.6.30.5 domU on top of Xen 3.3.1 and Xen 3.4.1, RHEL''s 2.6.18 kernel-xen dom0. On both systems, domU kernel config matters :D Sometimes turning on/off something that seems completely unrelated makes a difference between crashing or not. Unfortunately I can''t make out what''s wrong from your log. If you want to try out either 2.6.96-xen or 2.6.30.5, I can share my working domU .config. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I have not try Xen 3.4.1. I tried 2.6.30.5 on Quad-Core AMD Opteron(tm) Processor 2346 HE, crash too. The 2.6.29.6 domU crashed on Intel Xeon(R) CPU E5405 On Fri, Sep 4, 2009 at 7:34 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Fri, Sep 04, 2009 at 05:01:47PM +0800, Zu wrote: > > I compiled a domU kernel, the source is from kernel.org, the version is > > 2.6.29.6. The domU kernel crashed on Xen 3.3.1. The dom0 kernel is > 2.6.18.8 > > from xen.org. > > > > Have you tried with Xen 3.4.1 ? Also, have you tried vanilla > 2.6.30.<latest> in domU? > > Is this AMD hardware? > > -- Pasi > > > xm dmesg: > > (XEN) mm.c:1482:d95 Bad L1 flags 800000 > > (XEN) traps.c:437:d95 Unhandled invalid opcode fault/trap [#6] on VCPU 0 > > [ec=0000] > > (XEN) domain_crash_sync called from entry.S > > (XEN) Domain 95 (vcpu#0) crashed on cpu#0: > > (XEN) ----[ Xen-3.3.1 x86_64 debug=n Not tainted ]---- > > (XEN) CPU: 0 > > (XEN) RIP: e033:[<ffffffff8100aa83>] > > (XEN) RFLAGS: 0000000000000282 EM: 1 CONTEXT: pv guest > > (XEN) rax: 00000000ffffffea rbx: 8000000000000161 rcx: > 00000000017ff000 > > (XEN) rdx: 0000000000000000 rsi: 80000005f31da061 rdi: > ffffffff8150f000 > > (XEN) rbp: ffffffff81483fa8 rsp: ffffffff81483f58 r8: > 0000000000000000 > > (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: > 0000000000000000 > > (XEN) r12: ffffffff8150f000 r13: 0000000000000200 r14: > 0000000000002000 > > (XEN) r15: 0000000000000800 cr0: 000000008005003b cr4: > 00000000000026b0 > > (XEN) cr3: 00000005f307a000 cr2: 0000000000000000 > > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 > > (XEN) Guest stack trace from rsp=ffffffff81483f58: > > (XEN) 00000000017ff000 0000000000000000 ffffffff8100aa83 > 000000010000e030 > > (XEN) 0000000000010082 ffffffff81483f98 000000000000e02b > ffffffff8100aa7f > > (XEN) 0000000000000200 0000000000000010 ffffffff81483ff8 > ffffffff814b1268 > > (XEN) ffffffff8166f000 0000000000010000 0000000000000010 > 0000000000000000 > > (XEN) 0000000000000000 0000000000000000 0000000000000000 > 0000000000000000 > > (XEN) 0000000000000000 ffffffff815ec000 ffffffff815ed000 > ffffffff815ee000 > > (XEN) ffffffff815ef000 ffffffff815f0000 ffffffff815f1000 > ffffffff815f2000 > > (XEN) ffffffff815f3000 ffffffff815f4000 ffffffff815f5000 > ffffffff815f6000 > > (XEN) ffffffff815f7000 ffffffff815f8000 ffffffff815f9000 > ffffffff815fa000 > > (XEN) ffffffff815fb000 ffffffff815fc000 ffffffff815fd000 > ffffffff815fe000 > > (XEN) ffffffff815ff000 ffffffff81600000 ffffffff81601000 > ffffffff81602000 > > (XEN) ffffffff81603000 ffffffff81604000 ffffffff81605000 > ffffffff81606000 > > (XEN) ffffffff81607000 ffffffff81608000 ffffffff81609000 > ffffffff8160a000 > > (XEN) ffffffff8160b000 ffffffff8160c000 ffffffff8160d000 > ffffffff8160e000 > > (XEN) ffffffff8160f000 ffffffff81610000 ffffffff81611000 > ffffffff81612000 > > (XEN) ffffffff81613000 ffffffff81614000 ffffffff81615000 > ffffffff81616000 > > (XEN) ffffffff81617000 ffffffff81618000 ffffffff81619000 > ffffffff8161a000 > > (XEN) ffffffff8161b000 ffffffff8161c000 ffffffff8161d000 > ffffffff8161e000 > > (XEN) ffffffff8161f000 ffffffff81620000 ffffffff81621000 > ffffffff81622000 > > (XEN) ffffffff81623000 ffffffff81624000 ffffffff81625000 > ffffffff81626000 > > > > > > xm info: > > [root@zf1 debian5.rashost.com]# xm info > > host : zf1.rashost.com > > release : 2.6.18.8-xen > > version : #2 SMP Wed May 13 10:22:26 CST 2009 > > machine : x86_64 > > nr_cpus : 4 > > nr_nodes : 1 > > cores_per_socket : 4 > > threads_per_core : 1 > > cpu_mhz : 1995 > > hw_caps : > > bfebfbff:20000800:00000000:00000140:040ce33d:00000000:00000001:00000000 > > virt_caps : hvm > > total_memory : 32766 > > free_memory : 22003 > > node_to_cpu : node0:0-3 > > node_to_memory : node0:22003 > > xen_major : 3 > > xen_minor : 3 > > xen_extra : .1 > > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > > hvm-3.0-x86_32p hvm-3.0-x86_64 > > xen_scheduler : credit > > xen_pagesize : 4096 > > platform_params : virt_start=0xffff800000000000 > > xen_changeset : unavailable > > cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-44) > > cc_compile_by : zzh > > cc_compile_domain : rashost.com > > cc_compile_date : Fri May 1 16:47:47 CST 2009 > > xend_config_format : 4 > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pasi Kärkkäinen
2009-Sep-04 13:57 UTC
Re: [Xen-users] vanilla kernel 2.6.29.6 crashes on xen 3.3.1
On Fri, Sep 04, 2009 at 09:53:47PM +0800, Zu wrote:> I have not try Xen 3.4.1. > I tried 2.6.30.5 on Quad-Core AMD Opteron(tm) Processor 2346 HE, crash too. > The 2.6.29.6 domU crashed on Intel Xeon(R) CPU E5405 >OK. You should report this to xen-devel list. -- Pasi> On Fri, Sep 4, 2009 at 7:34 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > > On Fri, Sep 04, 2009 at 05:01:47PM +0800, Zu wrote: > > > I compiled a domU kernel, the source is from kernel.org, the version is > > > 2.6.29.6. The domU kernel crashed on Xen 3.3.1. The dom0 kernel is > > 2.6.18.8 > > > from xen.org. > > > > > > > Have you tried with Xen 3.4.1 ? Also, have you tried vanilla > > 2.6.30.<latest> in domU? > > > > Is this AMD hardware? > > > > -- Pasi > > > > > xm dmesg: > > > (XEN) mm.c:1482:d95 Bad L1 flags 800000 > > > (XEN) traps.c:437:d95 Unhandled invalid opcode fault/trap [#6] on VCPU 0 > > > [ec=0000] > > > (XEN) domain_crash_sync called from entry.S > > > (XEN) Domain 95 (vcpu#0) crashed on cpu#0: > > > (XEN) ----[ Xen-3.3.1 x86_64 debug=n Not tainted ]---- > > > (XEN) CPU: 0 > > > (XEN) RIP: e033:[<ffffffff8100aa83>] > > > (XEN) RFLAGS: 0000000000000282 EM: 1 CONTEXT: pv guest > > > (XEN) rax: 00000000ffffffea rbx: 8000000000000161 rcx: > > 00000000017ff000 > > > (XEN) rdx: 0000000000000000 rsi: 80000005f31da061 rdi: > > ffffffff8150f000 > > > (XEN) rbp: ffffffff81483fa8 rsp: ffffffff81483f58 r8: > > 0000000000000000 > > > (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: > > 0000000000000000 > > > (XEN) r12: ffffffff8150f000 r13: 0000000000000200 r14: > > 0000000000002000 > > > (XEN) r15: 0000000000000800 cr0: 000000008005003b cr4: > > 00000000000026b0 > > > (XEN) cr3: 00000005f307a000 cr2: 0000000000000000 > > > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 > > > (XEN) Guest stack trace from rsp=ffffffff81483f58: > > > (XEN) 00000000017ff000 0000000000000000 ffffffff8100aa83 > > 000000010000e030 > > > (XEN) 0000000000010082 ffffffff81483f98 000000000000e02b > > ffffffff8100aa7f > > > (XEN) 0000000000000200 0000000000000010 ffffffff81483ff8 > > ffffffff814b1268 > > > (XEN) ffffffff8166f000 0000000000010000 0000000000000010 > > 0000000000000000 > > > (XEN) 0000000000000000 0000000000000000 0000000000000000 > > 0000000000000000 > > > (XEN) 0000000000000000 ffffffff815ec000 ffffffff815ed000 > > ffffffff815ee000 > > > (XEN) ffffffff815ef000 ffffffff815f0000 ffffffff815f1000 > > ffffffff815f2000 > > > (XEN) ffffffff815f3000 ffffffff815f4000 ffffffff815f5000 > > ffffffff815f6000 > > > (XEN) ffffffff815f7000 ffffffff815f8000 ffffffff815f9000 > > ffffffff815fa000 > > > (XEN) ffffffff815fb000 ffffffff815fc000 ffffffff815fd000 > > ffffffff815fe000 > > > (XEN) ffffffff815ff000 ffffffff81600000 ffffffff81601000 > > ffffffff81602000 > > > (XEN) ffffffff81603000 ffffffff81604000 ffffffff81605000 > > ffffffff81606000 > > > (XEN) ffffffff81607000 ffffffff81608000 ffffffff81609000 > > ffffffff8160a000 > > > (XEN) ffffffff8160b000 ffffffff8160c000 ffffffff8160d000 > > ffffffff8160e000 > > > (XEN) ffffffff8160f000 ffffffff81610000 ffffffff81611000 > > ffffffff81612000 > > > (XEN) ffffffff81613000 ffffffff81614000 ffffffff81615000 > > ffffffff81616000 > > > (XEN) ffffffff81617000 ffffffff81618000 ffffffff81619000 > > ffffffff8161a000 > > > (XEN) ffffffff8161b000 ffffffff8161c000 ffffffff8161d000 > > ffffffff8161e000 > > > (XEN) ffffffff8161f000 ffffffff81620000 ffffffff81621000 > > ffffffff81622000 > > > (XEN) ffffffff81623000 ffffffff81624000 ffffffff81625000 > > ffffffff81626000 > > > > > > > > > xm info: > > > [root@zf1 debian5.rashost.com]# xm info > > > host : zf1.rashost.com > > > release : 2.6.18.8-xen > > > version : #2 SMP Wed May 13 10:22:26 CST 2009 > > > machine : x86_64 > > > nr_cpus : 4 > > > nr_nodes : 1 > > > cores_per_socket : 4 > > > threads_per_core : 1 > > > cpu_mhz : 1995 > > > hw_caps : > > > bfebfbff:20000800:00000000:00000140:040ce33d:00000000:00000001:00000000 > > > virt_caps : hvm > > > total_memory : 32766 > > > free_memory : 22003 > > > node_to_cpu : node0:0-3 > > > node_to_memory : node0:22003 > > > xen_major : 3 > > > xen_minor : 3 > > > xen_extra : .1 > > > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > > > hvm-3.0-x86_32p hvm-3.0-x86_64 > > > xen_scheduler : credit > > > xen_pagesize : 4096 > > > platform_params : virt_start=0xffff800000000000 > > > xen_changeset : unavailable > > > cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-44) > > > cc_compile_by : zzh > > > cc_compile_domain : rashost.com > > > cc_compile_date : Fri May 1 16:47:47 CST 2009 > > > xend_config_format : 4 > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2009-Sep-04 14:34 UTC
Re: [Xen-users] vanilla kernel 2.6.29.6 crashes on xen 3.3.1
On Fri, Sep 4, 2009 at 8:55 PM, Zu<zuzhihui@gmail.com> wrote:> It''s great if you send me the two .config files. Thank you! >Here''s .config for xenified 2.6.29.6 (kernel downloaded from http://x17.eu/xen/) : http://pastebin.com/f549489cb Caveats : - framebuffer support not compiled, so you need to disable it in domU config - you MUST set "console=xvc0" on kernel extra/command line and setup /etc/inittab to spawn login screen on xvc0. Here''s .config for vanilla 2.6.30.5 (from kernel.org) : http://pastebin.com/f741ab09b Caveats : - framebuffer support not compiled, so you need to disable it in domU config - you must setup /etc/inittab to spawn login screen on hvc0. I suggest you try building with that config first and see if it crash. If it works, you can start modifying config files as needed. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2009-Sep-04 14:47 UTC
Re: [Xen-users] vanilla kernel 2.6.29.6 crashes on xen 3.3.1
On Fri, Sep 4, 2009 at 9:34 PM, Fajar A. Nugraha<fajar@fajar.net> wrote:> On Fri, Sep 4, 2009 at 8:55 PM, Zu<zuzhihui@gmail.com> wrote: >> It''s great if you send me the two .config files. Thank you! >> > > Here''s .config for xenified 2.6.29.6 (kernel downloaded from > http://x17.eu/xen/) : http://pastebin.com/f549489cb > Caveats : > - framebuffer support not compiled, so you need to disable it in domU config > - you MUST set "console=xvc0" on kernel extra/command line and setup > /etc/inittab to spawn login screen on xvc0. > > Here''s .config for vanilla 2.6.30.5 (from kernel.org) : > http://pastebin.com/f741ab09b > Caveats : > - framebuffer support not compiled, so you need to disable it in domU config > - you must setup /etc/inittab to spawn login screen on hvc0.Sorry, I sent the wrong one for 2.6.30.5 :( It should be this one : http://pastebin.com/d7e156bc4> > I suggest you try building with that config first and see if it crash. > If it works, you can start modifying config files as needed. > > -- > Fajar >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Fajar, When I use the your .config file and type "make oldconfig", it show me some questions to answer. I assume these answer were already in the .config file. Why it ask me again? Both the vanilla kernel and the kernel from http://x17.eu/xen have this problem. Sorry for me English. Thanks. [root@zf1 linux-2.6.29.6-xen]# make oldconfig scripts/kconfig/conf -o arch/x86/Kconfig * * Restart config... * * * Processor type and features * Tickless System (Dynamic Ticks) (NO_HZ) [N/y/?] (NEW) On Fri, Sep 4, 2009 at 10:47 PM, Fajar A. Nugraha <fajar@fajar.net> wrote:> On Fri, Sep 4, 2009 at 9:34 PM, Fajar A. Nugraha<fajar@fajar.net> wrote: > > On Fri, Sep 4, 2009 at 8:55 PM, Zu<zuzhihui@gmail.com> wrote: > >> It''s great if you send me the two .config files. Thank you! > >> > > > > Here''s .config for xenified 2.6.29.6 (kernel downloaded from > > http://x17.eu/xen/) : http://pastebin.com/f549489cb > > Caveats : > > - framebuffer support not compiled, so you need to disable it in domU > config > > - you MUST set "console=xvc0" on kernel extra/command line and setup > > /etc/inittab to spawn login screen on xvc0. > > > > Here''s .config for vanilla 2.6.30.5 (from kernel.org) : > > http://pastebin.com/f741ab09b > > Caveats : > > - framebuffer support not compiled, so you need to disable it in domU > config > > - you must setup /etc/inittab to spawn login screen on hvc0. > > Sorry, I sent the wrong one for 2.6.30.5 :( > It should be this one : http://pastebin.com/d7e156bc4 > > > > > > > I suggest you try building with that config first and see if it crash. > > If it works, you can start modifying config files as needed. > > > > -- > > Fajar > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2009-Sep-04 16:27 UTC
Re: [Xen-users] vanilla kernel 2.6.29.6 crashes on xen 3.3.1
On Fri, Sep 4, 2009 at 11:15 PM, Zu<zuzhihui@gmail.com> wrote:> Hi Fajar, > > When I use the your .config file and type "make oldconfig", it show me some > questions to answer. I assume these answer were already in the .config file. > Why it ask me again? > > Both the vanilla kernel and the kernel from http://x17.eu/xen have this > problem.They are two different config for two different kernel. Perhaps you use the wrong one? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users