Dan Magenheimer
2012-Aug-29 22:22 UTC
Xen 4.2.0 won''t boot with FC17 dom0 on Dell Optiplex 790, boots fine with 4.1.3
Anybody else see this: a FC17 dom0 which boots fine for 4.1.3
crashes early in boot with Xen 4.2.0-rc4?
The hardware is a new Dell Optiplex 790 which I''ve noticed has a couple
of idiosyncrasies when booting recent upstream versions of Linux:
1) reboot=pci is required or reboot hangs
2) reducing visible memory via memmap= on a Linux command line is
fairly difficult (requires a very complex sequence of Linux boot
parameters, presumably due to a weird e820 RAM map in this hardware)
These idiosyncrasies may or may not be related to the dom0 crash,
just mentioning them in case they suggest an easy workaround.
The stock FC17 Xen booted, then I built/booted xen-4.1-testing.hg
and it was fine. Then I built/booted 4.2.0-rc4 and see the dom0 crash.
FC17 kernel/dom0 rev is 3.3.4-5.fc17.x86_64. I can reboot the
box to 4.1.3 still (but can''t do anything due to at least a 4.1/4.2
libxenlight.so version difference... will have to reinstall 4.1
tools I guess).
I think there have been some Xen memmap issues fixed in recent
upstream Linux, so will try building/booting linux-3.5 while
everyone flies home from Xen Summit ;-). But this seems
unpromising since Xen 4.1.3 works fine.
Tombstone attached:
[first, tail end of previous boot with dom0 crash, then full log with dom0
crash]
(XEN) elf_load_binary: phdr 3 at 0xffffffff81aed000 -> 0xffffffff81bd9000
(XEN) Scrubbing Free RAM: ......................................................
.....................done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch input to Xen
)
(XEN) Freed 260kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.
(XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
__ __ _ _ ____ ___ _ _
\ \/ /___ _ __ | || | |___ \ / _ \ _ __ ___| || | _ __ _ __ ___
\ // _ \ ''_ \ | || |_ __) || | | |__| ''__/ __| || |_ __|
''_ \| ''__/ _ \
/ \ __/ | | | |__ _| / __/ | |_| |__| | | (__|__ _|__| |_) | | | __/
/_/\_\___|_| |_| |_|(_)_____(_)___/ |_| \___| |_| | .__/|_| \___|
|_|
(XEN) Xen version 4.2.0-rc4-pre (root@vpn.oracle.com) (gcc (GCC) 4.7.0 20120507
(Red Hat 4.7.0-5)) Wed Aug 29 15:27:44 MDT 2012
(XEN) Latest ChangeSet: Tue Aug 28 22:40:45 2012 +0100 25786:a0b5f8102a00
(XEN) Bootloader: GRUB 2.00~beta4
(XEN) Command line: placeholder com1=115200,8n1 dom0_mem=512M console=vga,com1 l
oglvl=all guest_loglvl=all cpuidle=off
(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 - 000000000009ac00 (usable)
(XEN) 000000000009ac00 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 0000000020000000 (usable)
(XEN) 0000000020000000 - 0000000020200000 (reserved)
(XEN) 0000000020200000 - 0000000040000000 (usable)
(XEN) 0000000040000000 - 0000000040200000 (reserved)
(XEN) 0000000040200000 - 00000000ca9f7000 (usable)
(XEN) 00000000ca9f7000 - 00000000caa3b000 (reserved)
(XEN) 00000000caa3b000 - 00000000cadb7000 (usable)
(XEN) 00000000cadb7000 - 00000000cade7000 (reserved)
(XEN) 00000000cade7000 - 00000000cafe7000 (ACPI NVS)
(XEN) 00000000cafe7000 - 00000000cafff000 (ACPI data)
(XEN) 00000000cafff000 - 00000000cb000000 (usable)
(XEN) 00000000cb800000 - 00000000cfa00000 (reserved)
(XEN) 00000000fed1c000 - 00000000fed20000 (reserved)
(XEN) 00000000ffc00000 - 00000000ffc20000 (reserved)
(XEN) 0000000100000000 - 000000022e000000 (usable)
(XEN) ACPI: RSDP 000FE300, 0024 (r2 DELL )
(XEN) ACPI: XSDT CAFFDE18, 007C (r1 DELL CBX3 6222004 MSFT 10013)
(XEN) ACPI: FACP CAF87D98, 00F4 (r4 DELL CBX3 6222004 MSFT 10013)
(XEN) ACPI: DSDT CAF71018, 7341 (r2 INT430 SYSFexxx 1001 INTL 20090903)
(XEN) ACPI: FACS CAFE4D40, 0040
(XEN) ACPI: APIC CAFFCF18, 00CC (r2 DELL CBX3 6222004 MSFT 10013)
(XEN) ACPI: TCPA CAFE5D18, 0032 (r2 0 0)
(XEN) ACPI: SSDT CAF88A98, 02F9 (r1 DELLTP TPM 3000 INTL 20090903)
(XEN) ACPI: MCFG CAFE5C98, 003C (r1 DELL SNDYBRDG 6222004 MSFT 97)
(XEN) ACPI: HPET CAFE5C18, 0038 (r1 A M I PCHHPET 6222004 AMI. 3)
(XEN) ACPI: BOOT CAFE5B98, 0028 (r1 DELL CBX3 6222004 AMI 10013)
(XEN) ACPI: SSDT CAF7E818, 07C2 (r1 PmRef Cpu0Ist 3000 INTL 20090903)
(XEN) ACPI: SSDT CAF7D018, 0996 (r1 PmRef CpuPm 3000 INTL 20090903)
(XEN) ACPI: DMAR CAF87C18, 00E8 (r1 INTEL SNB 1 INTL 1)
(XEN) ACPI: SLIC CAF86C18, 0176 (r3 DELL CBX3 6222004 MSFT 10013)
(XEN) System RAM: 8073MB (8266808kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-000000022e000000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000f1fb0
(XEN) DMI 2.6 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI: 32/64X FACS address mismatch in FADT - cafe4e40/00000000cafe4d40, us
ing 32
(XEN) ACPI: wakeup_vec[cafe4e4c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 6:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
(XEN) Processor #2 6:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
(XEN) Processor #4 6:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
(XEN) Processor #6 6:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x08] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x09] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0a] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x0b] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0c] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x0d] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0e] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x0f] disabled)
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000
(XEN) Table is not found!
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 16 CPUs (12 hotplug CPUs)
(XEN) IRQ limits: 24 GSI, 760 MSI/MSI-X
(XEN) Switched to APIC driver x2apic_cluster.
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3093.024 MHz processor.
(XEN) Initing memory sharing.
(XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7
(XEN) mce_intel.c:1239: MCA Capability: BCAST 1 SER 0 CMCI 1 firstbank 0 extende
d MCE MSR 0
(XEN) Intel machine check reporting enabled
(XEN) PCI: MCFG configuration 0: base f8000000 segment 0000 buses 00 - 3f
(XEN) PCI: Not using MCFG for segment 0000 bus 00-3f
(XEN) Intel VT-d supported page sizes: 4kB.
(XEN) Intel VT-d supported page sizes: 4kB.
(XEN) Intel VT-d Snoop Control not enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping enabled.
(XEN) Intel VT-d Shared EPT tables not enabled.
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using old ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) TSC deadline timer enabled
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 32 KiB.
(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) - Unrestricted Guest
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB
(XEN) Brought up 4 CPUs
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) mtrr: your CPUs had inconsistent variable MTRR settings
(XEN) mtrr: probably your BIOS does not setup all CPUs.
(XEN) mtrr: corrected configuration.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0x885000
(XEN) elf_parse_binary: phdr: paddr=0x1a00000 memsz=0xd70e0
(XEN) elf_parse_binary: phdr: paddr=0x1ad8000 memsz=0x14240
(XEN) elf_parse_binary: phdr: paddr=0x1aed000 memsz=0x6bf000
(XEN) elf_parse_binary: memory: 0x1000000 -> 0x21ac000
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) elf_xen_parse_note: ENTRY = 0xffffffff81aed200
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000
(XEN) elf_xen_parse_note: FEATURES =
"!writable_page_tables|pae_pgdir_above_4gb"
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0
(XEN) elf_xen_addr_calc_check: addresses:
(XEN) virt_base = 0xffffffff80000000
(XEN) elf_paddr_offset = 0x0
(XEN) virt_offset = 0xffffffff80000000
(XEN) virt_kstart = 0xffffffff81000000
(XEN) virt_kend = 0xffffffff821ac000
(XEN) virt_entry = 0xffffffff81aed200
(XEN) p2m_base = 0xffffffffffffffff
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x21ac000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000220000000->0000000224000000 (103435 pages to be
all
ocated)
(XEN) Init. ramdisk: 000000022b40b000->000000022dfffa00
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff821ac000
(XEN) Init. ramdisk: ffffffff821ac000->ffffffff84da0a00
(XEN) Phys-Mach map: ffffffff84da1000->ffffffff84ea1000
(XEN) Start info: ffffffff84ea1000->ffffffff84ea14b4
(XEN) Page tables: ffffffff84ea2000->ffffffff84ecd000
(XEN) Boot stack: ffffffff84ecd000->ffffffff84ece000
(XEN) TOTAL: ffffffff80000000->ffffffff85000000
(XEN) ENTRY ADDRESS: ffffffff81aed200
(XEN) Dom0 has maximum 4 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81885000
(XEN) elf_load_binary: phdr 1 at 0xffffffff81a00000 -> 0xffffffff81ad70e0
(XEN) elf_load_binary: phdr 2 at 0xffffffff81ad8000 -> 0xffffffff81aec240
(XEN) elf_load_binary: phdr 3 at 0xffffffff81aed000 -> 0xffffffff81bd9000
(XEN) Scrubbing Free RAM: ......................................................
.....................done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch input to Xen
)
(XEN) Freed 260kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.
(XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
Konrad Rzeszutek Wilk
2012-Aug-29 22:44 UTC
Re: Xen 4.2.0 won''t boot with FC17 dom0 on Dell Optiplex 790, boots fine with 4.1.3
On Wed, Aug 29, 2012 at 03:22:40PM -0700, Dan Magenheimer wrote:> Anybody else see this: a FC17 dom0 which boots fine for 4.1.3 > crashes early in boot with Xen 4.2.0-rc4? > > The hardware is a new Dell Optiplex 790 which I''ve noticed has a couple > of idiosyncrasies when booting recent upstream versions of Linux: > 1) reboot=pci is required or reboot hangs > 2) reducing visible memory via memmap= on a Linux command line is > fairly difficult (requires a very complex sequence of Linux boot > parameters, presumably due to a weird e820 RAM map in this hardware) > > These idiosyncrasies may or may not be related to the dom0 crash, > just mentioning them in case they suggest an easy workaround.What happens if you run with ''console=vga vga=text,keep'' on the hypervisor line and on the Linux command line: ''console=hvc0 earlyprink=xen debug loglevel=8''> > The stock FC17 Xen booted, then I built/booted xen-4.1-testing.hg > and it was fine. Then I built/booted 4.2.0-rc4 and see the dom0 crash. > FC17 kernel/dom0 rev is 3.3.4-5.fc17.x86_64. I can reboot the > box to 4.1.3 still (but can''t do anything due to at least a 4.1/4.2 > libxenlight.so version difference... will have to reinstall 4.1 > tools I guess). > > I think there have been some Xen memmap issues fixed in recent > upstream Linux, so will try building/booting linux-3.5 whileUse v3.5.3 if you can.> everyone flies home from Xen Summit ;-). But this seemsThere was a bug in 3.5 that got fixed in 3.6 and it should be on the stable tree. It is is 5bc6f9888db5739abfa0cae279b4b442e4db8049> unpromising since Xen 4.1.3 works fine. > > Tombstone attached: > > [first, tail end of previous boot with dom0 crash, then full log with dom0 crash] > > (XEN) elf_load_binary: phdr 3 at 0xffffffff81aed000 -> 0xffffffff81bd9000 > (XEN) Scrubbing Free RAM: ...................................................... > .....................done. > (XEN) Initial low memory virq threshold set at 0x4000 pages. > (XEN) Std. Loglevel: All > (XEN) Guest Loglevel: All > (XEN) Xen is relinquishing VGA console. > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen > ) > (XEN) Freed 260kB init memory. > mapping kernel into physical memory > Xen: setup ISA identity maps > about to get started... > (XEN) Domain 0 crashed: rebooting machine in 5 seconds. > (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. > __ __ _ _ ____ ___ _ _ > \ \/ /___ _ __ | || | |___ \ / _ \ _ __ ___| || | _ __ _ __ ___ > \ // _ \ ''_ \ | || |_ __) || | | |__| ''__/ __| || |_ __| ''_ \| ''__/ _ \ > / \ __/ | | | |__ _| / __/ | |_| |__| | | (__|__ _|__| |_) | | | __/ > /_/\_\___|_| |_| |_|(_)_____(_)___/ |_| \___| |_| | .__/|_| \___| > |_| > (XEN) Xen version 4.2.0-rc4-pre (root@vpn.oracle.com) (gcc (GCC) 4.7.0 20120507 > (Red Hat 4.7.0-5)) Wed Aug 29 15:27:44 MDT 2012 > (XEN) Latest ChangeSet: Tue Aug 28 22:40:45 2012 +0100 25786:a0b5f8102a00 > (XEN) Bootloader: GRUB 2.00~beta4 > (XEN) Command line: placeholder com1=115200,8n1 dom0_mem=512M console=vga,com1 l > oglvl=all guest_loglvl=all cpuidle=off > (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 - 000000000009ac00 (usable) > (XEN) 000000000009ac00 - 00000000000a0000 (reserved) > (XEN) 00000000000e0000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 0000000020000000 (usable) > (XEN) 0000000020000000 - 0000000020200000 (reserved) > (XEN) 0000000020200000 - 0000000040000000 (usable) > (XEN) 0000000040000000 - 0000000040200000 (reserved) > (XEN) 0000000040200000 - 00000000ca9f7000 (usable) > (XEN) 00000000ca9f7000 - 00000000caa3b000 (reserved) > (XEN) 00000000caa3b000 - 00000000cadb7000 (usable) > (XEN) 00000000cadb7000 - 00000000cade7000 (reserved) > (XEN) 00000000cade7000 - 00000000cafe7000 (ACPI NVS) > (XEN) 00000000cafe7000 - 00000000cafff000 (ACPI data) > (XEN) 00000000cafff000 - 00000000cb000000 (usable) > (XEN) 00000000cb800000 - 00000000cfa00000 (reserved) > (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) > (XEN) 00000000ffc00000 - 00000000ffc20000 (reserved) > (XEN) 0000000100000000 - 000000022e000000 (usable) > (XEN) ACPI: RSDP 000FE300, 0024 (r2 DELL ) > (XEN) ACPI: XSDT CAFFDE18, 007C (r1 DELL CBX3 6222004 MSFT 10013) > (XEN) ACPI: FACP CAF87D98, 00F4 (r4 DELL CBX3 6222004 MSFT 10013) > (XEN) ACPI: DSDT CAF71018, 7341 (r2 INT430 SYSFexxx 1001 INTL 20090903) > (XEN) ACPI: FACS CAFE4D40, 0040 > (XEN) ACPI: APIC CAFFCF18, 00CC (r2 DELL CBX3 6222004 MSFT 10013) > (XEN) ACPI: TCPA CAFE5D18, 0032 (r2 0 0) > (XEN) ACPI: SSDT CAF88A98, 02F9 (r1 DELLTP TPM 3000 INTL 20090903) > (XEN) ACPI: MCFG CAFE5C98, 003C (r1 DELL SNDYBRDG 6222004 MSFT 97) > (XEN) ACPI: HPET CAFE5C18, 0038 (r1 A M I PCHHPET 6222004 AMI. 3) > (XEN) ACPI: BOOT CAFE5B98, 0028 (r1 DELL CBX3 6222004 AMI 10013) > (XEN) ACPI: SSDT CAF7E818, 07C2 (r1 PmRef Cpu0Ist 3000 INTL 20090903) > (XEN) ACPI: SSDT CAF7D018, 0996 (r1 PmRef CpuPm 3000 INTL 20090903) > (XEN) ACPI: DMAR CAF87C18, 00E8 (r1 INTEL SNB 1 INTL 1) > (XEN) ACPI: SLIC CAF86C18, 0176 (r3 DELL CBX3 6222004 MSFT 10013) > (XEN) System RAM: 8073MB (8266808kB) > (XEN) No NUMA configuration found > (XEN) Faking a node at 0000000000000000-000000022e000000 > (XEN) Domain heap initialised > (XEN) found SMP MP-table at 000f1fb0 > (XEN) DMI 2.6 present. > (XEN) Using APIC driver default > (XEN) ACPI: PM-Timer IO Port: 0x408 > (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0] > (XEN) ACPI: 32/64X FACS address mismatch in FADT - cafe4e40/00000000cafe4d40, us > ing 32 > (XEN) ACPI: wakeup_vec[cafe4e4c], vec_size[20] > (XEN) ACPI: Local APIC address 0xfee00000 > (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > (XEN) Processor #0 6:10 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) > (XEN) Processor #2 6:10 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled) > (XEN) Processor #4 6:10 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) > (XEN) Processor #6 6:10 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x08] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x09] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0a] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x0b] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0c] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x0d] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0e] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x0f] disabled) > (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) > (XEN) ACPI: IRQ0 used by override. > (XEN) ACPI: IRQ2 used by override. > (XEN) ACPI: IRQ9 used by override. > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000 > (XEN) Table is not found! > (XEN) Using ACPI (MADT) for SMP configuration information > (XEN) SMP: Allowing 16 CPUs (12 hotplug CPUs) > (XEN) IRQ limits: 24 GSI, 760 MSI/MSI-X > (XEN) Switched to APIC driver x2apic_cluster. > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Detected 3093.024 MHz processor. > (XEN) Initing memory sharing. > (XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7 > (XEN) mce_intel.c:1239: MCA Capability: BCAST 1 SER 0 CMCI 1 firstbank 0 extende > d MCE MSR 0 > (XEN) Intel machine check reporting enabled > (XEN) PCI: MCFG configuration 0: base f8000000 segment 0000 buses 00 - 3f > (XEN) PCI: Not using MCFG for segment 0000 bus 00-3f > (XEN) Intel VT-d supported page sizes: 4kB. > (XEN) Intel VT-d supported page sizes: 4kB. > (XEN) Intel VT-d Snoop Control not enabled. > (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. > (XEN) Intel VT-d Queued Invalidation enabled. > (XEN) Intel VT-d Interrupt Remapping enabled. > (XEN) Intel VT-d Shared EPT tables not enabled. > (XEN) I/O virtualisation enabled > (XEN) - Dom0 mode: Relaxed > (XEN) Enabled directed EOI with ioapic_ack_old on! > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using old ACK method > (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 > (XEN) TSC deadline timer enabled > (XEN) Platform timer is 14.318MHz HPET > (XEN) Allocated console ring of 32 KiB. > (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) - Unrestricted Guest > (XEN) HVM: ASIDs enabled. > (XEN) HVM: VMX enabled > (XEN) HVM: Hardware Assisted Paging (HAP) detected > (XEN) HVM: HAP page sizes: 4kB, 2MB > (XEN) Brought up 4 CPUs > (XEN) ACPI sleep modes: S3 > (XEN) mcheck_poll: Machine check polling timer started. > (XEN) mtrr: your CPUs had inconsistent variable MTRR settings > (XEN) mtrr: probably your BIOS does not setup all CPUs. > (XEN) mtrr: corrected configuration. > (XEN) *** LOADING DOMAIN 0 *** > (XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0x885000 > (XEN) elf_parse_binary: phdr: paddr=0x1a00000 memsz=0xd70e0 > (XEN) elf_parse_binary: phdr: paddr=0x1ad8000 memsz=0x14240 > (XEN) elf_parse_binary: phdr: paddr=0x1aed000 memsz=0x6bf000 > (XEN) elf_parse_binary: memory: 0x1000000 -> 0x21ac000 > (XEN) elf_xen_parse_note: GUEST_OS = "linux" > (XEN) elf_xen_parse_note: GUEST_VERSION = "2.6" > (XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0" > (XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000 > (XEN) elf_xen_parse_note: ENTRY = 0xffffffff81aed200 > (XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000 > (XEN) elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb" > > (XEN) elf_xen_parse_note: PAE_MODE = "yes" > (XEN) elf_xen_parse_note: LOADER = "generic" > (XEN) elf_xen_parse_note: unknown xen elf note (0xd) > (XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1 > (XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000 > (XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0 > (XEN) elf_xen_addr_calc_check: addresses: > (XEN) virt_base = 0xffffffff80000000 > (XEN) elf_paddr_offset = 0x0 > (XEN) virt_offset = 0xffffffff80000000 > (XEN) virt_kstart = 0xffffffff81000000 > (XEN) virt_kend = 0xffffffff821ac000 > (XEN) virt_entry = 0xffffffff81aed200 > (XEN) p2m_base = 0xffffffffffffffff > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x21ac000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000220000000->0000000224000000 (103435 pages to be all > ocated) > (XEN) Init. ramdisk: 000000022b40b000->000000022dfffa00 > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff81000000->ffffffff821ac000 > (XEN) Init. ramdisk: ffffffff821ac000->ffffffff84da0a00 > (XEN) Phys-Mach map: ffffffff84da1000->ffffffff84ea1000 > (XEN) Start info: ffffffff84ea1000->ffffffff84ea14b4 > (XEN) Page tables: ffffffff84ea2000->ffffffff84ecd000 > (XEN) Boot stack: ffffffff84ecd000->ffffffff84ece000 > (XEN) TOTAL: ffffffff80000000->ffffffff85000000 > (XEN) ENTRY ADDRESS: ffffffff81aed200 > (XEN) Dom0 has maximum 4 VCPUs > (XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81885000 > (XEN) elf_load_binary: phdr 1 at 0xffffffff81a00000 -> 0xffffffff81ad70e0 > (XEN) elf_load_binary: phdr 2 at 0xffffffff81ad8000 -> 0xffffffff81aec240 > (XEN) elf_load_binary: phdr 3 at 0xffffffff81aed000 -> 0xffffffff81bd9000 > (XEN) Scrubbing Free RAM: ...................................................... > .....................done. > (XEN) Initial low memory virq threshold set at 0x4000 pages. > (XEN) Std. Loglevel: All > (XEN) Guest Loglevel: All > (XEN) Xen is relinquishing VGA console. > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen > ) > (XEN) Freed 260kB init memory. > mapping kernel into physical memory > Xen: setup ISA identity maps > about to get started... > (XEN) Domain 0 crashed: rebooting machine in 5 seconds. > (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
bing
2012-Aug-30 06:16 UTC
Re: Xen 4.2.0 won''t boot with FC17 dom0 on Dell Optiplex 790, boots fine with 4.1.3
I have a similar crash on Xen 4.2.0-rc3 with HP DC7900, reboot right after loading Dom0 kernel. I found a workaround by pass xsave=0 option to the xen kernel. It seems to be CPU related, same setup (same xen, Dom0 kernel version) works fine on another Dell Precision 3200. bing On 08/30/2012 08:22 AM, Dan Magenheimer wrote:> Anybody else see this: a FC17 dom0 which boots fine for 4.1.3 > crashes early in boot with Xen 4.2.0-rc4? > > The hardware is a new Dell Optiplex 790 which I''ve noticed has a couple > of idiosyncrasies when booting recent upstream versions of Linux: > 1) reboot=pci is required or reboot hangs > 2) reducing visible memory via memmap= on a Linux command line is > fairly difficult (requires a very complex sequence of Linux boot > parameters, presumably due to a weird e820 RAM map in this hardware) > > These idiosyncrasies may or may not be related to the dom0 crash, > just mentioning them in case they suggest an easy workaround. > > The stock FC17 Xen booted, then I built/booted xen-4.1-testing.hg > and it was fine. Then I built/booted 4.2.0-rc4 and see the dom0 crash. > FC17 kernel/dom0 rev is 3.3.4-5.fc17.x86_64. I can reboot the > box to 4.1.3 still (but can''t do anything due to at least a 4.1/4.2 > libxenlight.so version difference... will have to reinstall 4.1 > tools I guess). > > I think there have been some Xen memmap issues fixed in recent > upstream Linux, so will try building/booting linux-3.5 while > everyone flies home from Xen Summit ;-). But this seems > unpromising since Xen 4.1.3 works fine. > > Tombstone attached: > > [first, tail end of previous boot with dom0 crash, then full log with dom0 crash] > > (XEN) elf_load_binary: phdr 3 at 0xffffffff81aed000 -> 0xffffffff81bd9000 > (XEN) Scrubbing Free RAM: ...................................................... > .....................done. > (XEN) Initial low memory virq threshold set at 0x4000 pages. > (XEN) Std. Loglevel: All > (XEN) Guest Loglevel: All > (XEN) Xen is relinquishing VGA console. > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen > ) > (XEN) Freed 260kB init memory. > mapping kernel into physical memory > Xen: setup ISA identity maps > about to get started... > (XEN) Domain 0 crashed: rebooting machine in 5 seconds. > (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. > __ __ _ _ ____ ___ _ _ > \ \/ /___ _ __ | || | |___ \ / _ \ _ __ ___| || | _ __ _ __ ___ > \ // _ \ ''_ \ | || |_ __) || | | |__| ''__/ __| || |_ __| ''_ \| ''__/ _ \ > / \ __/ | | | |__ _| / __/ | |_| |__| | | (__|__ _|__| |_) | | | __/ > /_/\_\___|_| |_| |_|(_)_____(_)___/ |_| \___| |_| | .__/|_| \___| > |_| > (XEN) Xen version 4.2.0-rc4-pre (root@vpn.oracle.com) (gcc (GCC) 4.7.0 20120507 > (Red Hat 4.7.0-5)) Wed Aug 29 15:27:44 MDT 2012 > (XEN) Latest ChangeSet: Tue Aug 28 22:40:45 2012 +0100 25786:a0b5f8102a00 > (XEN) Bootloader: GRUB 2.00~beta4 > (XEN) Command line: placeholder com1=115200,8n1 dom0_mem=512M console=vga,com1 l > oglvl=all guest_loglvl=all cpuidle=off > (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 - 000000000009ac00 (usable) > (XEN) 000000000009ac00 - 00000000000a0000 (reserved) > (XEN) 00000000000e0000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 0000000020000000 (usable) > (XEN) 0000000020000000 - 0000000020200000 (reserved) > (XEN) 0000000020200000 - 0000000040000000 (usable) > (XEN) 0000000040000000 - 0000000040200000 (reserved) > (XEN) 0000000040200000 - 00000000ca9f7000 (usable) > (XEN) 00000000ca9f7000 - 00000000caa3b000 (reserved) > (XEN) 00000000caa3b000 - 00000000cadb7000 (usable) > (XEN) 00000000cadb7000 - 00000000cade7000 (reserved) > (XEN) 00000000cade7000 - 00000000cafe7000 (ACPI NVS) > (XEN) 00000000cafe7000 - 00000000cafff000 (ACPI data) > (XEN) 00000000cafff000 - 00000000cb000000 (usable) > (XEN) 00000000cb800000 - 00000000cfa00000 (reserved) > (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) > (XEN) 00000000ffc00000 - 00000000ffc20000 (reserved) > (XEN) 0000000100000000 - 000000022e000000 (usable) > (XEN) ACPI: RSDP 000FE300, 0024 (r2 DELL ) > (XEN) ACPI: XSDT CAFFDE18, 007C (r1 DELL CBX3 6222004 MSFT 10013) > (XEN) ACPI: FACP CAF87D98, 00F4 (r4 DELL CBX3 6222004 MSFT 10013) > (XEN) ACPI: DSDT CAF71018, 7341 (r2 INT430 SYSFexxx 1001 INTL 20090903) > (XEN) ACPI: FACS CAFE4D40, 0040 > (XEN) ACPI: APIC CAFFCF18, 00CC (r2 DELL CBX3 6222004 MSFT 10013) > (XEN) ACPI: TCPA CAFE5D18, 0032 (r2 0 0) > (XEN) ACPI: SSDT CAF88A98, 02F9 (r1 DELLTP TPM 3000 INTL 20090903) > (XEN) ACPI: MCFG CAFE5C98, 003C (r1 DELL SNDYBRDG 6222004 MSFT 97) > (XEN) ACPI: HPET CAFE5C18, 0038 (r1 A M I PCHHPET 6222004 AMI. 3) > (XEN) ACPI: BOOT CAFE5B98, 0028 (r1 DELL CBX3 6222004 AMI 10013) > (XEN) ACPI: SSDT CAF7E818, 07C2 (r1 PmRef Cpu0Ist 3000 INTL 20090903) > (XEN) ACPI: SSDT CAF7D018, 0996 (r1 PmRef CpuPm 3000 INTL 20090903) > (XEN) ACPI: DMAR CAF87C18, 00E8 (r1 INTEL SNB 1 INTL 1) > (XEN) ACPI: SLIC CAF86C18, 0176 (r3 DELL CBX3 6222004 MSFT 10013) > (XEN) System RAM: 8073MB (8266808kB) > (XEN) No NUMA configuration found > (XEN) Faking a node at 0000000000000000-000000022e000000 > (XEN) Domain heap initialised > (XEN) found SMP MP-table at 000f1fb0 > (XEN) DMI 2.6 present. > (XEN) Using APIC driver default > (XEN) ACPI: PM-Timer IO Port: 0x408 > (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0] > (XEN) ACPI: 32/64X FACS address mismatch in FADT - cafe4e40/00000000cafe4d40, us > ing 32 > (XEN) ACPI: wakeup_vec[cafe4e4c], vec_size[20] > (XEN) ACPI: Local APIC address 0xfee00000 > (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > (XEN) Processor #0 6:10 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) > (XEN) Processor #2 6:10 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled) > (XEN) Processor #4 6:10 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) > (XEN) Processor #6 6:10 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x08] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x09] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0a] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x0b] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0c] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x0d] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0e] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x0f] disabled) > (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) > (XEN) ACPI: IRQ0 used by override. > (XEN) ACPI: IRQ2 used by override. > (XEN) ACPI: IRQ9 used by override. > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000 > (XEN) Table is not found! > (XEN) Using ACPI (MADT) for SMP configuration information > (XEN) SMP: Allowing 16 CPUs (12 hotplug CPUs) > (XEN) IRQ limits: 24 GSI, 760 MSI/MSI-X > (XEN) Switched to APIC driver x2apic_cluster. > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Detected 3093.024 MHz processor. > (XEN) Initing memory sharing. > (XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7 > (XEN) mce_intel.c:1239: MCA Capability: BCAST 1 SER 0 CMCI 1 firstbank 0 extende > d MCE MSR 0 > (XEN) Intel machine check reporting enabled > (XEN) PCI: MCFG configuration 0: base f8000000 segment 0000 buses 00 - 3f > (XEN) PCI: Not using MCFG for segment 0000 bus 00-3f > (XEN) Intel VT-d supported page sizes: 4kB. > (XEN) Intel VT-d supported page sizes: 4kB. > (XEN) Intel VT-d Snoop Control not enabled. > (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. > (XEN) Intel VT-d Queued Invalidation enabled. > (XEN) Intel VT-d Interrupt Remapping enabled. > (XEN) Intel VT-d Shared EPT tables not enabled. > (XEN) I/O virtualisation enabled > (XEN) - Dom0 mode: Relaxed > (XEN) Enabled directed EOI with ioapic_ack_old on! > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using old ACK method > (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 > (XEN) TSC deadline timer enabled > (XEN) Platform timer is 14.318MHz HPET > (XEN) Allocated console ring of 32 KiB. > (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) - Unrestricted Guest > (XEN) HVM: ASIDs enabled. > (XEN) HVM: VMX enabled > (XEN) HVM: Hardware Assisted Paging (HAP) detected > (XEN) HVM: HAP page sizes: 4kB, 2MB > (XEN) Brought up 4 CPUs > (XEN) ACPI sleep modes: S3 > (XEN) mcheck_poll: Machine check polling timer started. > (XEN) mtrr: your CPUs had inconsistent variable MTRR settings > (XEN) mtrr: probably your BIOS does not setup all CPUs. > (XEN) mtrr: corrected configuration. > (XEN) *** LOADING DOMAIN 0 *** > (XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0x885000 > (XEN) elf_parse_binary: phdr: paddr=0x1a00000 memsz=0xd70e0 > (XEN) elf_parse_binary: phdr: paddr=0x1ad8000 memsz=0x14240 > (XEN) elf_parse_binary: phdr: paddr=0x1aed000 memsz=0x6bf000 > (XEN) elf_parse_binary: memory: 0x1000000 -> 0x21ac000 > (XEN) elf_xen_parse_note: GUEST_OS = "linux" > (XEN) elf_xen_parse_note: GUEST_VERSION = "2.6" > (XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0" > (XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000 > (XEN) elf_xen_parse_note: ENTRY = 0xffffffff81aed200 > (XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000 > (XEN) elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb" > > (XEN) elf_xen_parse_note: PAE_MODE = "yes" > (XEN) elf_xen_parse_note: LOADER = "generic" > (XEN) elf_xen_parse_note: unknown xen elf note (0xd) > (XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1 > (XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000 > (XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0 > (XEN) elf_xen_addr_calc_check: addresses: > (XEN) virt_base = 0xffffffff80000000 > (XEN) elf_paddr_offset = 0x0 > (XEN) virt_offset = 0xffffffff80000000 > (XEN) virt_kstart = 0xffffffff81000000 > (XEN) virt_kend = 0xffffffff821ac000 > (XEN) virt_entry = 0xffffffff81aed200 > (XEN) p2m_base = 0xffffffffffffffff > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x21ac000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000220000000->0000000224000000 (103435 pages to be all > ocated) > (XEN) Init. ramdisk: 000000022b40b000->000000022dfffa00 > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff81000000->ffffffff821ac000 > (XEN) Init. ramdisk: ffffffff821ac000->ffffffff84da0a00 > (XEN) Phys-Mach map: ffffffff84da1000->ffffffff84ea1000 > (XEN) Start info: ffffffff84ea1000->ffffffff84ea14b4 > (XEN) Page tables: ffffffff84ea2000->ffffffff84ecd000 > (XEN) Boot stack: ffffffff84ecd000->ffffffff84ece000 > (XEN) TOTAL: ffffffff80000000->ffffffff85000000 > (XEN) ENTRY ADDRESS: ffffffff81aed200 > (XEN) Dom0 has maximum 4 VCPUs > (XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81885000 > (XEN) elf_load_binary: phdr 1 at 0xffffffff81a00000 -> 0xffffffff81ad70e0 > (XEN) elf_load_binary: phdr 2 at 0xffffffff81ad8000 -> 0xffffffff81aec240 > (XEN) elf_load_binary: phdr 3 at 0xffffffff81aed000 -> 0xffffffff81bd9000 > (XEN) Scrubbing Free RAM: ...................................................... > .....................done. > (XEN) Initial low memory virq threshold set at 0x4000 pages. > (XEN) Std. Loglevel: All > (XEN) Guest Loglevel: All > (XEN) Xen is relinquishing VGA console. > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen > ) > (XEN) Freed 260kB init memory. > mapping kernel into physical memory > Xen: setup ISA identity maps > about to get started... > (XEN) Domain 0 crashed: rebooting machine in 5 seconds. > (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-develUTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects. Think. Green. Do. Please consider the environment before printing this email.
Dan Magenheimer
2012-Aug-30 16:19 UTC
Re: Xen 4.2.0 won''t boot with FC17 dom0 on Dell Optiplex 790, boots fine with 4.1.3
> From: Konrad Rzeszutek Wilk > > On Wed, Aug 29, 2012 at 03:22:40PM -0700, Dan Magenheimer wrote: > > Anybody else see this: a FC17 dom0 which boots fine for 4.1.3 > > crashes early in boot with Xen 4.2.0-rc4? > > > > The hardware is a new Dell Optiplex 790 which I''ve noticed has a couple > > of idiosyncrasies when booting recent upstream versions of Linux: > > 1) reboot=pci is required or reboot hangs > > 2) reducing visible memory via memmap= on a Linux command line is > > fairly difficult (requires a very complex sequence of Linux boot > > parameters, presumably due to a weird e820 RAM map in this hardware) > > > > These idiosyncrasies may or may not be related to the dom0 crash, > > just mentioning them in case they suggest an easy workaround. > > What happens if you run with ''console=vga vga=text,keep'' on the > hypervisor line and on the Linux command line: ''console=hvc0 > earlyprink=xen debug loglevel=8''Ah, good, thanks for the pointer. Haven''t had to do that in awhile. The dom0 tombstone has an xsave_init call in it... I tried booting with xsave=0 as a Xen boot parameter and I can now boot 4.2.0-rc4 with FC17 dom0. Sorry for the noise. Thanks, Dan
Dan Magenheimer
2012-Aug-30 17:04 UTC
Re: Xen 4.2.0 won''t boot with FC17 dom0 on Dell Optiplex 790, boots fine with 4.1.3
> From: bing [mailto:Libing.Chen@uts.edu.au] > Sent: Thursday, August 30, 2012 12:16 AM > To: xen-devel@lists.xen.org > Subject: Re: [Xen-devel] Xen 4.2.0 won''t boot with FC17 dom0 on Dell Optiplex 790, boots fine with > 4.1.3 > > I have a similar crash on Xen 4.2.0-rc3 with HP DC7900, reboot right > after loading Dom0 kernel. I found a workaround by pass xsave=0 option > to the xen kernel. It seems to be CPU related, same setup (same xen, > Dom0 kernel version) works fine on another Dell Precision 3200.Thanks, just saw this as I wasn''t cc''ed on your email. xsave=0 did solve my problem also.
Jan Beulich
2012-Aug-31 11:05 UTC
Re: Xen 4.2.0 won''t boot with FC17 dom0 on Dell Optiplex 790, boots fine with 4.1.3
>>> On 30.08.12 at 19:04, Dan Magenheimer <dan.magenheimer@oracle.com> wrote: >> From: bing [mailto:Libing.Chen@uts.edu.au] >> Sent: Thursday, August 30, 2012 12:16 AM >> To: xen-devel@lists.xen.org >> Subject: Re: [Xen-devel] Xen 4.2.0 won''t boot with FC17 dom0 on Dell Optiplex > 790, boots fine with >> 4.1.3 >> >> I have a similar crash on Xen 4.2.0-rc3 with HP DC7900, reboot right >> after loading Dom0 kernel. I found a workaround by pass xsave=0 option >> to the xen kernel. It seems to be CPU related, same setup (same xen, >> Dom0 kernel version) works fine on another Dell Precision 3200. > > Thanks, just saw this as I wasn''t cc''ed on your email. xsave=0 > did solve my problem also.But that was known to be required only with certain, non-upstream broken kernels (which got their own xsave handling wrong). Can either of you confirm this is a problem with a plain upstream kernel now too (and if so, which version(s))? Jan
Dan Magenheimer
2012-Aug-31 14:59 UTC
Re: Xen 4.2.0 won''t boot with FC17 dom0 on Dell Optiplex 790, boots fine with 4.1.3
> From: Jan Beulich [mailto:JBeulich@suse.com] > Subject: Re: [Xen-devel] Xen 4.2.0 won''t boot with FC17 dom0 on Dell Optiplex 790, boots fine with > 4.1.3 > > >>> On 30.08.12 at 19:04, Dan Magenheimer <dan.magenheimer@oracle.com> wrote: > >> From: bing [mailto:Libing.Chen@uts.edu.au] > >> Sent: Thursday, August 30, 2012 12:16 AM > >> To: xen-devel@lists.xen.org > >> Subject: Re: [Xen-devel] Xen 4.2.0 won''t boot with FC17 dom0 on Dell Optiplex > > 790, boots fine with > >> 4.1.3 > >> > >> I have a similar crash on Xen 4.2.0-rc3 with HP DC7900, reboot right > >> after loading Dom0 kernel. I found a workaround by pass xsave=0 option > >> to the xen kernel. It seems to be CPU related, same setup (same xen, > >> Dom0 kernel version) works fine on another Dell Precision 3200. > > > > Thanks, just saw this as I wasn''t cc''ed on your email. xsave=0 > > did solve my problem also. > > But that was known to be required only with certain, non-upstream > broken kernels (which got their own xsave handling wrong). Can > either of you confirm this is a problem with a plain upstream kernel > now too (and if so, which version(s))?Konrad told me this was a known problem on Fedora so I didn''t try an upstream kernel. Dan
Konrad Rzeszutek Wilk
2012-Aug-31 17:32 UTC
Re: Xen 4.2.0 won''t boot with FC17 dom0 on Dell Optiplex 790, boots fine with 4.1.3
On Fri, Aug 31, 2012 at 12:05:24PM +0100, Jan Beulich wrote:> >>> On 30.08.12 at 19:04, Dan Magenheimer <dan.magenheimer@oracle.com> wrote: > >> From: bing [mailto:Libing.Chen@uts.edu.au] > >> Sent: Thursday, August 30, 2012 12:16 AM > >> To: xen-devel@lists.xen.org > >> Subject: Re: [Xen-devel] Xen 4.2.0 won''t boot with FC17 dom0 on Dell Optiplex > > 790, boots fine with > >> 4.1.3 > >> > >> I have a similar crash on Xen 4.2.0-rc3 with HP DC7900, reboot right > >> after loading Dom0 kernel. I found a workaround by pass xsave=0 option > >> to the xen kernel. It seems to be CPU related, same setup (same xen, > >> Dom0 kernel version) works fine on another Dell Precision 3200. > > > > Thanks, just saw this as I wasn''t cc''ed on your email. xsave=0 > > did solve my problem also. > > But that was known to be required only with certain, non-upstream > broken kernels (which got their own xsave handling wrong). Can > either of you confirm this is a problem with a plain upstream kernel > now too (and if so, which version(s))?I can confirm. Have a brand new AMD machine that goes bellyup with that with a Fedora stock kernel and with a vanialla (v3.5 or v3.6-rc2) works just right.> > Jan > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >