This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] dom0 unable to launch domU

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] dom0 unable to launch domU
From: "Olivier B." <xen.list@xxxxxxxxx>
Date: Sun, 02 Aug 2009 02:17:57 +0200
Delivery-date: Sat, 01 Aug 2009 17:18:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A74680E.8060201@xxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4A741D92.90005@xxxxxxxxx> <4A74203B.2000103@xxxxxxxxx> <4A74680E.8060201@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla-Thunderbird (X11/20090103)

I added "earlyprintk=xen" in cmdline options to can view kernel messages.

Here is the output :
Started domain thundercat
(early) last_map_addr: 100000000 end: 100000000
(early) No NUMA configuration found
(early) Faking a node at 0000000000000000-0000000100000000
(early) Bootmem setup node 0 0000000000000000-0000000100000000
(early)   NODE_DATA [0000000000001000 - 0000000000004fff]
(early)   bootmap [0000000000008000 -  0000000000027fff] pages 20
(early) (5 early reservations) ==> bootmem [0000000000 - 0100000000]
(early) #0 [0000000000 - 0000001000] BIOS data page(early) ==> [0000000000 - 0000001000] (early) #1 [0001123000 - 0001130000] XEN PAGETABLES(early) ==> [0001123000 - 0001130000] (early) #2 [0000006000 - 0000008000] TRAMPOLINE(early) ==> [0000006000 - 0000008000] (early) #3 [0000200000 - 000091f838] TEXT DATA BSS(early) ==> [0000200000 - 000091f838] (early) #4 [0001130000 - 0001925000] PGTABLE(early) ==> [0001130000 - 0001925000]
(early) Zone PFN ranges:
(early)   DMA      0x00000000 -> 0x00001000
(early)   DMA32    0x00001000 -> 0x00100000
(early)   Normal   0x00100000 -> 0x00100000
(early) Movable zone start PFN for each node
(early) early_node_map[3] active PFN ranges
(early)     0: 0x00000000 -> 0x000000a0
(early)     0: 0x00000100 -> 0x00000920
(early)     0: 0x00001123 -> 0x00100000
(early) SMP: Allowing 1 CPUs, 0 hotplug CPUs
(early) No local APIC present
(early) PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
(early) PM: Registered nosave memory: 0000000000920000 - 0000000001123000
(early) PCI: Warning: Cannot find a gap in the 32bit address range
(early) PCI: Unassigned devices with 32bit resource registers may break!
(early) Allocating PCI resources starting at 100200000 (gap: 100100000:400000)
(early) NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1
(early) PERCPU: Allocating 61440 bytes of per cpu data
(early) Built 1 zonelists in Node order, mobility grouping on. Total pages: 1030267
(early) Policy zone: DMA32
(early) Kernel command line: root=/dev/xvda2 ro earlyprintk=xen
(early) Initializing CPU#0
(early) invalid opcode: 0000 [#1] (early) SMP (early)
(early) last sysfs file:
(early) CPU 0 (early)
(early) Modules linked in:(early)
(early) Pid: 0, comm: swapper Not tainted #1
(early) RIP: e030:[<ffffffff805c34b4>] (early) [<ffffffff805c34b4>] xsave_cntxt_init+0xb5/0x194
(early) RSP: e02b:ffffffff80819e38  EFLAGS: 00010046
(early) RAX: 0000000000000003 RBX: ffffffff80819e44 RCX: 0000000000000000
(early) RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000042620
(early) RBP: ffffffff80819e68 R08: ffffffff80819e38 R09: ffffffff80819e3c
(early) R10: 00000000ffffffff R11: 000000000000e710 R12: ffffffff80819e40
(early) R13: ffffffff80819e3c R14: ffffffff80819e38 R15: ffff880001949000
(early) FS: 0000000000000000(0000) GS:ffffffff808cf000(0000) knlGS:0000000000000000
(early) CS:  e033 DS: 0000 ES: 0000 CR0: 0000000080050033
(early) CR2: 0000000000000000 CR3: 0000000000201000 CR4: 0000000000002620
(early) DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
(early) DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
(early) Process swapper (pid: 0, threadinfo ffffffff80818000, task ffffffff80796340)
(early) Stack:
(early) 0000024000000000(early) 0000000300000240(early) 0000000080050033(early) 0000000000000000(early) (early) ffffffff808cd000(early) 0000000000000005(early) ffffffff80819e78(early) ffffffff805dab4f(early) (early) ffffffff80819e98(early) ffffffff805dabcb(early) ffff88008109e000(early) 00000000ffff8800(early)
(early) Call Trace:
(early)  [<ffffffff805dab4f>] init_thread_xstate+0x12/0x20
(early)  [<ffffffff805dabcb>] fpu_init+0x6e/0xbe
(early)  [<ffffffff805dc728>] cpu_init+0x310/0x33c
(early)  [<ffffffff808339c5>] trap_init+0x5b0/0x5b7
(early)  [<ffffffff8082cb24>] start_kernel+0x1cb/0x365
(early)  [<ffffffff8082c2c1>] x86_64_start_reservations+0xac/0xb0
(early)  [<ffffffff80832dfd>] xen_start_kernel+0x814/0x823
(early) Code: (early) e9 (early) 30 (early) 00 (early) 00 (early) 00 (early) 04 (early) 00 (early) ff (early) 15 (early) ba (early) be (early) 1d (early) 00 (early) 89 (early) c7 (early) 81 (early) cf (early) 00 (early) 00 (early) 04 (early) 00 (early) ff (early) 15 (early) b4 (early) be (early) 1d (early) 00 (early) 31 (early) c9 (early) 48 (early) 8b (early) 05 (early) c3 (early) 07 (early) 31 (early) 00 (early) 48 (early) 89 (early) c2 (early) 48 (early) c1 (early) ea (early) 20 (early) <0f> (early) 01 (early) d1 (early) c7 (early) 45 (early) dc (early) 0d (early) 00 (early) 00 (early) 00 (early) c7 (early) 45 (early) d4 (early) 00 (early) 00 (early) 00 (early) 00 (early) 48 (early) 89 (early) df (early) 4c (early)
(early) RIP (early)  [<ffffffff805c34b4>] xsave_cntxt_init+0xb5/0x194
(early)  RSP <ffffffff80819e38>
(early) ---[ end trace 4eaa2a86a8e2da22 ]---
(early) Kernel panic - not syncing: Attempted to kill the idle task!
(early) ------------[ cut here ]------------
(early) WARNING: at kernel/smp.c:329 smp_call_function_many+0x40/0x1f7()
(early) Modules linked in:(early)
(early) Pid: 0, comm: swapper Tainted: G      D #1
(early) Call Trace:
(early)  [<ffffffff802407b7>] warn_slowpath+0xaf/0xd6
(early)  [<ffffffff805e3c3d>] ? _spin_unlock_irqrestore+0x18/0x1c
(early)  [<ffffffff805e3c3d>] ? _spin_unlock_irqrestore+0x18/0x1c
(early)  [<ffffffff80240e11>] ? release_console_sem+0x18f/0x1c4
(early)  [<ffffffff80241322>] ? vprintk+0x2b9/0x2e6
(early)  [<ffffffff802606ff>] smp_call_function_many+0x40/0x1f7
(early)  [<ffffffff802608d3>] smp_call_function+0x1d/0x21
(early)  [<ffffffff8020e2a2>] xen_smp_send_stop+0x14/0x16
(early)  [<ffffffff805e14d5>] panic+0x7d/0x11e
(early)  [<ffffffff80243a07>] do_exit+0x71/0x67f
(early)  [<ffffffff802142cd>] oops_end+0x97/0x9c
(early)  [<ffffffff80214484>] die+0x55/0x5e
(early)  [<ffffffff80212192>] do_trap+0x115/0x124
(early)  [<ffffffff80212551>] do_invalid_op+0x98/0xa1
(early)  [<ffffffff805c34b4>] ? xsave_cntxt_init+0xb5/0x194
(early)  [<ffffffff805e3c3d>] ? _spin_unlock_irqrestore+0x18/0x1c
(early)  [<ffffffff805e3c3d>] ? _spin_unlock_irqrestore+0x18/0x1c
(early)  [<ffffffff80240e11>] ? release_console_sem+0x18f/0x1c4
(early)  [<ffffffff8021151b>] invalid_op+0x1b/0x20
(early)  [<ffffffff805c34b4>] ? xsave_cntxt_init+0xb5/0x194
(early)  [<ffffffff805c34a4>] ? xsave_cntxt_init+0xa5/0x194
(early)  [<ffffffff805dab4f>] init_thread_xstate+0x12/0x20
(early)  [<ffffffff805dabcb>] fpu_init+0x6e/0xbe
(early)  [<ffffffff805dc728>] cpu_init+0x310/0x33c
(early)  [<ffffffff808339c5>] trap_init+0x5b0/0x5b7
(early)  [<ffffffff8082cb24>] start_kernel+0x1cb/0x365
(early)  [<ffffffff8082c2c1>] x86_64_start_reservations+0xac/0xb0
(early)  [<ffffffff80832dfd>] xen_start_kernel+0x814/0x823
(early) ---[ end trace 4eaa2a86a8e2da23 ]---

So I have :
> (early) Initializing CPU#0
> (early) invalid opcode: 0000 [#1] (early) SMP (early)

Should I consider it has a "CPU bug" ?
It's a Xeon E5405 stepping 10. I don't think it's so special, but my other dom0 seems to be Xeon E5405 stepping 6.


PS : is the "xen-devel" list more appropriate ?

Olivier B. a écrit :
So, the problem seem to come from my vanilla kernel : with the Debian kernel domU boot on this dom0.

I will try to find where is the problem. The RAID card is different on this dom0, but I was thinking this hadn't impact for domU.


Xen-users mailing list