* pv-ops dom0 doesn't boot, serial console broken
@ 2010-01-26 17:19 George Dunlap
2010-01-26 17:38 ` Konrad Rzeszutek Wilk
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: George Dunlap @ 2010-01-26 17:19 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
I did a basic make install on a fresh Debian Lenny box this morning,
and unfortunately haven't been able to successfully boot under Xen:
* The 2.6.27-xen-686 Lenny kernel hangs under Xen-32-PAE and under Xen-64
* Under native, the 2.6.31.6 pv-ops kernel (pulled fresh this morning)
boots fine, with serial console
* Under Xen, the same kernel doesn't boot and doesn't output anything
to the serial console, hanging after a few minutes.
Here's the console log of booting Linux 2.6.31.6 pv-ops (build with
"make kernels") on a 64-bit hypervisor c/s 20858:2636e5619708 is
attached.
Any ideas?
I wouldn't be surprised if I've misconfigured something, but the fact
that the exact same kernel works fine on bare metal makes me think it
likely to be something else...
-George
[-- Attachment #2: console-log-pv-ops-on-xen-x86_64.txt --]
[-- Type: text/plain, Size: 12599 bytes --]
\ \/ /___ _ __ | || | / _ \ / _ \ _ __ ___|___ / _ __ _ __ ___
\ // _ \ '_ \ | || |_| | | | | | |__| '__/ __| |_ \ __| '_ \| '__/ _ \
/ \ __/ | | | |__ _| |_| | |_| |__| | | (__ ___) |__| |_) | | | __/
/_/\_\___|_| |_| |_|(_)___(_)___/ |_| \___|____/ | .__/|_| \___|
|_|
(XEN) Xen version 4.0.0-rc3-pre (dunlapg@(none)) (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) Tue Jan 26 11:18:53 EST 2010
(XEN) Latest ChangeSet: unavailable
(XEN) Console output is synchronous.
(XEN) Command line: watchdog com1=115200,8n1 console=com1,tty sync_console tmem=0
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN) Found 1 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 00000000000a0000 (usable)
(XEN) 0000000000100000 - 00000000bf699000 (usable)
(XEN) 00000000bf699000 - 00000000bf6af000 (reserved)
(XEN) 00000000bf6af000 - 00000000bf6ce000 (ACPI data)
(XEN) 00000000bf6ce000 - 00000000c0000000 (reserved)
(XEN) 00000000e0000000 - 00000000f0000000 (reserved)
(XEN) 00000000fe000000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000840000000 (usable)
(XEN) ACPI: RSDP 000F1630, 0024 (r2 DELL )
(XEN) ACPI: XSDT 000F1734, 009C (r1 DELL PE_SC3 1 DELL 1)
(XEN) ACPI: FACP BF6C3F9C, 00F4 (r3 DELL PE_SC3 1 DELL 1)
(XEN) ACPI: DSDT BF6AF000, 320F (r1 DELL PE_SC3 1 INTL 20050624)
(XEN) ACPI: FACS BF6C6000, 0040
(XEN) ACPI: APIC BF6C3478, 015E (r1 DELL PE_SC3 1 DELL 1)
(XEN) ACPI: SPCR BF6C35D8, 0050 (r1 DELL PE_SC3 1 DELL 1)
(XEN) ACPI: HPET BF6C362C, 0038 (r1 DELL PE_SC3 1 DELL 1)
(XEN) ACPI: DMAR BF6C3668, 01C0 (r1 DELL PE_SC3 1 DELL 1)
(XEN) ACPI: MCFG BF6C38C4, 003C (r1 DELL PE_SC3 1 DELL 1)
(XEN) ACPI: WD__ BF6C3904, 0134 (r1 DELL PE_SC3 1 DELL 1)
(XEN) ACPI: SLIC BF6C3A3C, 0024 (r1 DELL PE_SC3 1 DELL 1)
(XEN) ACPI: ERST BF6B2390, 0270 (r1 DELL PE_SC3 1 DELL 1)
(XEN) ACPI: HEST BF6B2600, 027C (r1 DELL PE_SC3 1 DELL 1)
(XEN) ACPI: BERT BF6B2210, 0030 (r1 DELL PE_SC3 1 DELL 1)
(XEN) ACPI: EINJ BF6B2240, 0150 (r1 DELL PE_SC3 1 DELL 1)
(XEN) ACPI: SRAT BF6C3BC0, 0370 (r1 DELL PE_SC3 1 DELL 1)
(XEN) ACPI: TCPA BF6C3F34, 0064 (r2 DELL PE_SC3 1 DELL 1)
(XEN) ACPI: SSDT BF6C7000, 4194 (r1 INTEL PPM RCM 80000001 INTL 20061109)
(XEN) System RAM: 32737MB (33523424kB)
(XEN) Domain heap initialised DMA width 32 bits
(XEN) Processor #16 7:10 APIC version 21
(XEN) Processor #0 7:10 APIC version 21
(XEN) Processor #18 7:10 APIC version 21
(XEN) Processor #2 7:10 APIC version 21
(XEN) Processor #20 7:10 APIC version 21
(XEN) Processor #4 7:10 APIC version 21
(XEN) Processor #22 7:10 APIC version 21
(XEN) Processor #6 7:10 APIC version 21
(XEN) Processor #17 7:10 APIC version 21
(XEN) Processor #1 7:10 APIC version 21
(XEN) Processor #19 7:10 APIC version 21
(XEN) Processor #3 7:10 APIC version 21
(XEN) Processor #21 7:10 APIC version 21
(XEN) Processor #5 7:10 APIC version 21
(XEN) Processor #23 7:10 APIC version 21
(XEN) Processor #7 7:10 APIC version 21
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 1, version 32, address 0xfec80000, GSI 32-55
(XEN) Enabling APIC mode: Phys. Using 2 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2261.066 MHz processor.
(XEN) Initing memory sharing.
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) Intel VT-d Snoop Control supported.
(XEN) Intel VT-d DMA Passthrough not supported.
(XEN) Intel VT-d Queued Invalidation supported.
(XEN) Intel VT-d Interrupt Remapping supported.
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled
(XEN) CPU0: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 1/0 eip 8c000
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 2/18 eip 8c000
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 3/2 eip 8c000
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 4/20 eip 8c000
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#4.
(XEN) CPU4: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 5/4 eip 8c000
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#5.
(XEN) CPU5: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 6/22 eip 8c000
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#6.
(XEN) CPU6: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 7/6 eip 8c000
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#7.
(XEN) CPU7: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 8/17 eip 8c000
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#8.
(XEN) CPU8: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 9/1 eip 8c000
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#9.
(XEN) CPU9: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 10/19 eip 8c000
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#10.
(XEN) CPU10: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 11/3 eip 8c000
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#11.
(XEN) CPU11: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 12/21 eip 8c000
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#12.
(XEN) CPU12: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 13/5 eip 8c000
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#13.
(XEN) CPU13: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 14/23 eip 8c000
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#14.
(XEN) CPU14: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Booting processor 15/7 eip 8c000
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#15.
(XEN) CPU15: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping 05
(XEN) Total of 16 processors activated.
(XEN) Testing NMI watchdog --- CPU#0 okay. CPU#1 okay. CPU#2 okay. CPU#3 okay. CPU#4 okay. CPU#5 okay. CPU#6 okay. CPU#7 okay. CPU#8 okay. CPU#9 okay. CPU#10 okay. CPU#11 okay. CPU#12 okay. CPU#13 okay. CPU#14 okay. CPU#15 okay.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) TSC is reliable, synchronization unnecessary
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 16 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0x1000000 -> 0x19ce000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000824000000->0000000828000000 (8227955 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: 00000000c1000000->00000000c19ce000
(XEN) Init. ramdisk: 00000000c19ce000->00000000c1ea2800
(XEN) Phys-Mach map: 00000000c1ea3000->00000000c3e161cc
(XEN) Start info: 00000000c3e17000->00000000c3e174b4
(XEN) Page tables: 00000000c3e18000->00000000c3e3e000
(XEN) Boot stack: 00000000c3e3e000->00000000c3e3f000
(XEN) TOTAL: 00000000c0000000->00000000c4000000
(XEN) ENTRY ADDRESS: 00000000c176b000
(XEN) Dom0 has maximum 16 VCPUs
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) **********************************************
(XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
(XEN) ******* This option is intended to aid debugging of Xen by ensuring
(XEN) ******* that all output is synchronously delivered on the serial line.
(XEN) ******* However it can introduce SIGNIFICANT latencies and affect
(XEN) ******* timekeeping. It is NOT recommended for production use!
(XEN) **********************************************
(XEN) 3... 2... 1...
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 152kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
(XEN) ioapic_guest_write: apic=0, pin=0, irq=0
(XEN) ioapic_guest_write: new_entry=00010000
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=2, irq=0
(XEN) ioapic_guest_write: new_entry=00010000
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped
(XEN) ioapic_guest_write: apic=0, pin=4, irq=4
(XEN) ioapic_guest_write: new_entry=00010000
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 7 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 13 already mapped
(XEN) allocated vector for irq:16
(XEN) allocated vector for irq:17
(XEN) allocated vector for irq:18
(XEN) allocated vector for irq:19
(XEN) allocated vector for irq:20
(XEN) allocated vector for irq:21
(XEN) allocated vector for irq:22
(XEN) allocated vector for irq:23
(XEN) allocated vector for irq:32
(XEN) allocated vector for irq:33
(XEN) allocated vector for irq:34
(XEN) allocated vector for irq:35
(XEN) allocated vector for irq:36
(XEN) allocated vector for irq:37
(XEN) allocated vector for irq:38
(XEN) allocated vector for irq:39
(XEN) allocated vector for irq:40
(XEN) allocated vector for irq:41
(XEN) allocated vector for irq:42
(XEN) allocated vector for irq:43
(XEN) allocated vector for irq:44
(XEN) allocated vector for irq:45
(XEN) allocated vector for irq:46
(XEN) allocated vector for irq:47
(XEN) allocated vector for irq:48
(XEN) allocated vector for irq:49
(XEN) allocated vector for irq:50
(XEN) allocated vector for irq:51
(XEN) allocated vector for irq:52
(XEN) allocated vector for irq:53
(XEN) allocated vector for irq:54
(XEN) ioapic_guest_write: apic=1, pin=23, irq=55
(XEN) ioapic_guest_write: new_entry=00010000
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=0, irq=0
(XEN) ioapic_guest_write: new_entry=00000000
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=4, irq=4
(XEN) ioapic_guest_write: new_entry=00000004
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=4, irq=4
(XEN) ioapic_guest_write: new_entry=00000004
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=21, irq=21
(XEN) ioapic_guest_write: new_entry=0001a015
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: pv-ops dom0 doesn't boot, serial console broken
2010-01-26 17:19 pv-ops dom0 doesn't boot, serial console broken George Dunlap
@ 2010-01-26 17:38 ` Konrad Rzeszutek Wilk
2010-01-26 17:42 ` Keir Fraser
2010-01-26 17:56 ` Pasi Kärkkäinen
2 siblings, 0 replies; 4+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-01-26 17:38 UTC (permalink / raw)
To: George Dunlap; +Cc: xen-devel
On Tue, Jan 26, 2010 at 05:19:38PM +0000, George Dunlap wrote:
> I did a basic make install on a fresh Debian Lenny box this morning,
> and unfortunately haven't been able to successfully boot under Xen:
> * The 2.6.27-xen-686 Lenny kernel hangs under Xen-32-PAE and under Xen-64
> * Under native, the 2.6.31.6 pv-ops kernel (pulled fresh this morning)
> boots fine, with serial console
> * Under Xen, the same kernel doesn't boot and doesn't output anything
> to the serial console, hanging after a few minutes.
What does your grub configuration entry look like?
>
> Here's the console log of booting Linux 2.6.31.6 pv-ops (build with
> "make kernels") on a 64-bit hypervisor c/s 20858:2636e5619708 is
> attached.
>
> Any ideas?
Dom0 boots. It probably just is outputing to nowhehere land.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: pv-ops dom0 doesn't boot, serial console broken
2010-01-26 17:19 pv-ops dom0 doesn't boot, serial console broken George Dunlap
2010-01-26 17:38 ` Konrad Rzeszutek Wilk
@ 2010-01-26 17:42 ` Keir Fraser
2010-01-26 17:56 ` Pasi Kärkkäinen
2 siblings, 0 replies; 4+ messages in thread
From: Keir Fraser @ 2010-01-26 17:42 UTC (permalink / raw)
To: George Dunlap, xen-devel@lists.xensource.com
On 26/01/2010 17:19, "George Dunlap" <dunlapg@umich.edu> wrote:
> Here's the console log of booting Linux 2.6.31.6 pv-ops (build with
> "make kernels") on a 64-bit hypervisor c/s 20858:2636e5619708 is
> attached.
>
> Any ideas?
The Xen logging indicates some stuff is happening after dom0 is started.
Probably either the console= option is incorrect, or if this is all
happening before normal console output is initialised, at least earlyprintk
should print something out I think. Clearly dom0 initialisation is getting
reasonably far if it's tickling IRQ related bits and pieces.
-- Keir
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: pv-ops dom0 doesn't boot, serial console broken
2010-01-26 17:19 pv-ops dom0 doesn't boot, serial console broken George Dunlap
2010-01-26 17:38 ` Konrad Rzeszutek Wilk
2010-01-26 17:42 ` Keir Fraser
@ 2010-01-26 17:56 ` Pasi Kärkkäinen
2 siblings, 0 replies; 4+ messages in thread
From: Pasi Kärkkäinen @ 2010-01-26 17:56 UTC (permalink / raw)
To: George Dunlap; +Cc: xen-devel
On Tue, Jan 26, 2010 at 05:19:38PM +0000, George Dunlap wrote:
> I did a basic make install on a fresh Debian Lenny box this morning,
> and unfortunately haven't been able to successfully boot under Xen:
> * The 2.6.27-xen-686 Lenny kernel hangs under Xen-32-PAE and under Xen-64
> * Under native, the 2.6.31.6 pv-ops kernel (pulled fresh this morning)
> boots fine, with serial console
> * Under Xen, the same kernel doesn't boot and doesn't output anything
> to the serial console, hanging after a few minutes.
>
> Here's the console log of booting Linux 2.6.31.6 pv-ops (build with
> "make kernels") on a 64-bit hypervisor c/s 20858:2636e5619708 is
> attached.
>
> Any ideas?
>
> I wouldn't be surprised if I've misconfigured something, but the fact
> that the exact same kernel works fine on bare metal makes me think it
> likely to be something else...
>
There are example grub.conf entries here (including serial console):
http://wiki.xensource.com/xenwiki/XenParavirtOps
And more details about serial console here:
http://wiki.xensource.com/xenwiki/XenSerialConsole
Hopefully that helps.
-- Pasi
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-01-26 17:56 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-01-26 17:19 pv-ops dom0 doesn't boot, serial console broken George Dunlap
2010-01-26 17:38 ` Konrad Rzeszutek Wilk
2010-01-26 17:42 ` Keir Fraser
2010-01-26 17:56 ` Pasi Kärkkäinen
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.