Re: [Xen-devel] Xen-4.10 Domain-0 crashes at bootup

[Juergen Gross <jgross@xxxxxxxx>]

On 04/04/18 12:07, M A Young wrote:
> On Wed, 4 Apr 2018, Ajay Garg wrote:
> 
>> Since I failed to get a single reply on my original issue as per
>> https://lists.xenproject.org/archives/html/minios-devel/2018-04/msg00004.html,
>> so I had no option but to try on a newer xen version.
>>
>> So, I created  a  new virtualbox-guest, and followed the steps as per
>> https://blog.werk21.de/en/2018/02/08/build-xen-hypervisor-410-and-xen-tools-ubuntu-1604-pvh
>>
>> Now, when start the guest with Xen-hypervisor enabled, it does not come up.
>> I took serial-logs at bootup time, they are as follows :
>>
>> #############################################################################
>>  Xen 4.10.1-pre
>> (XEN) Xen version 4.10.1-pre (ajay@) (gcc (Ubuntu
>> 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609) debug=n  Wed Apr  4 12:54:58
>> IST 2018
>> (XEN) Latest ChangeSet: Tue Mar 20 14:23:14 2018 +0100 git:0f92968
>> (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.17
>> (XEN) Command line: placeholder console=com1 com1=115200,8n1
>> loglvl=all guest_loglvl=all
>> (XEN) Xen image load base address: 0
>> (XEN) Video information:
>> (XEN)  VGA is text mode 80x25, font 8x16
>> (XEN) Disc information:
>> (XEN)  Found 1 MBR signatures
>> (XEN)  Found 1 EDD information structures
>> (XEN) Xen-e820 RAM map:
>> (XEN)  0000000000000000 - 000000000009fc00 (usable)
>> (XEN)  000000000009fc00 - 00000000000a0000 (reserved)
>> (XEN)  00000000000f0000 - 0000000000100000 (reserved)
>> (XEN)  0000000000100000 - 00000000bfff0000 (usable)
>> (XEN)  00000000bfff0000 - 00000000c0000000 (ACPI data)
>> (XEN)  00000000fec00000 - 00000000fec01000 (reserved)
>> (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
>> (XEN)  00000000fffc0000 - 0000000100000000 (reserved)
>> (XEN) New Xen image base address: 0xbf800000
>> (XEN) System RAM: 3071MB (3145276kB)
>> (XEN) ACPI: RSDP 000E0000, 0024 (r2 VBOX  )
>> (XEN) ACPI: XSDT BFFF0030, 003C (r1 VBOX   VBOXXSDT        1 ASL        61)
>> (XEN) ACPI: FACP BFFF00F0, 00F4 (r4 VBOX   VBOXFACP        1 ASL        61)
>> (XEN) ACPI: DSDT BFFF0470, 21FF (r2 VBOX   VBOXBIOS        2 INTL 20160108)
>> (XEN) ACPI: FACS BFFF0200, 0040
>> (XEN) ACPI: APIC BFFF0240, 0054 (r2 VBOX   VBOXAPIC        1 ASL        61)
>> (XEN) ACPI: SSDT BFFF02A0, 01CC (r1 VBOX   VBOXCPUT        2 INTL 20160108)
>> (XEN) No NUMA configuration found
>> (XEN) Faking a node at 0000000000000000-00000000bfff0000
>> (XEN) Domain heap initialised
>> (XEN) CPU Vendor: Intel, Family 6 (0x6), Model 142 (0x8e), Stepping 9
>> (raw 000806e9)
>> (XEN) found SMP MP-table at 0009fff0
>> (XEN) DMI 2.5 present.
>> (XEN) Using APIC driver default
>> (XEN) ACPI: PM-Timer IO Port: 0x4008 (32 bits)
>> (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:4004,1:0], pm1x_evt[1:4000,1:0]
>> (XEN) ACPI:             wakeup_vec[bfff020c], vec_size[20]
>> (XEN) ACPI: Local APIC address 0xfee00000
>> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
>> (XEN) ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
>> (XEN) IOAPIC[0]: apic_id 1, 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) ERST table was not found
>> (XEN) Using ACPI (MADT) for SMP configuration information
>> (XEN) SMP: Allowing 1 CPUs (0 hotplug CPUs)
>> (XEN) IRQ limits: 24 GSI, 184 MSI/MSI-X
>> (XEN) Not enabling x2APIC: depends on iommu_supports_eim.
>> (XEN) xstate: size: 0x440 and states: 0x7
>> (XEN) CPU0: No MCE banks present. Machine check support disabled
>> (XEN) Speculative mitigation facilities:
>> (XEN)   Compiled-in support: INDIRECT_THUNK
>> (XEN) BTI mitigations: Thunk RETPOLINE, Others: RSB_NATIVE RSB_VMEXIT
>> (XEN) Using scheduler: SMP Credit Scheduler (credit)
>> (XEN) Platform timer is 3.579MHz ACPI PM Timer
>> (XEN) Detected 2712.035 MHz processor.
>> (XEN) Initing memory sharing.
>> (XEN) alt table ffff82d080421798 -> ffff82d080423244
>> (XEN) I/O virtualisation disabled
>> (XEN) nr_sockets: 1
>> (XEN) ENABLING IO-APIC IRQs
>> (XEN)  -> Using new ACK method
>> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
>> (XEN) Allocated console ring of 16 KiB.
>> (XEN) Brought up 1 CPUs
>> (XEN) build-id: 0734050809e0cb9f52e65322a0d3911d082e348b
>> (XEN) CPUIDLE: disabled due to no HPET. Force enable with 'cpuidle'.
>> (XEN) ACPI sleep modes: S3
>> (XEN) VPMU: disabled
>> (XEN) xenoprof: Initialization failed. Intel processor family 6 model
>> 142 is not supported
>> (XEN) Dom0 has maximum 208 PIRQs
>> (XEN) NX (Execute Disable) protection active
>> (XEN) *** LOADING DOMAIN 0 ***
>> (XEN)  Xen  kernel: 64-bit, lsb, compat32
>> (XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2957000
>> (XEN) PHYSICAL MEMORY ARRANGEMENT:
>> (XEN)  Dom0 alloc.:   00000000b4000000->00000000b8000000 (715309 pages
>> to be allocated)
>> (XEN)  Init. ramdisk: 00000000bc915000->00000000bf7ffed9
>> (XEN) VIRTUAL MEMORY ARRANGEMENT:
>> (XEN)  Loaded kernel: ffffffff81000000->ffffffff82957000
>> (XEN)  Init. ramdisk: 0000000000000000->0000000000000000
>> (XEN)  Phys-Mach map: 0000008000000000->00000080005ac8c0
>> (XEN)  Start info:    ffffffff82957000->ffffffff829574b4
>> (XEN)  Xenstore ring: 0000000000000000->0000000000000000
>> (XEN)  Console ring:  0000000000000000->0000000000000000
>> (XEN)  Page tables:   ffffffff82958000->ffffffff82971000
>> (XEN)  Boot stack:    ffffffff82971000->ffffffff82972000
>> (XEN)  TOTAL:         ffffffff80000000->ffffffff82c00000
>> (XEN)  ENTRY ADDRESS: ffffffff824a4180
>> (XEN) Dom0 has maximum 1 VCPUs
>> (XEN) Initial low memory virq threshold set at 0x4000 pages.
>> (XEN) Scrubbing Free RAM on 1 nodes using 1 CPUs
>> (XEN) ........................done.
>> (XEN) Std. Loglevel: All
>> (XEN) Guest Loglevel: All
>> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
>> input to Xen)
>> (XEN) Freed 468kB init memory
>> mapping kernel into physical memory
>> about to get started...
>> (XEN) d0v0 Unhandled invalid opcode fault/trap [#6, ec=ffffffff]
>> (XEN) domain_crash_sync called from entry.S: fault at ffff82d08035501f
>> x86_64/entry.S#create_bounce_frame+0x135/0x166
>> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
>> (XEN) ----[ Xen-4.10.1-pre  x86_64  debug=n   Not tainted ]----
>> (XEN) CPU:    0
>> (XEN) RIP:    e033:[<ffffffff824b49cd>]
>> (XEN) RFLAGS: 0000000000000286   EM: 1   CONTEXT: pv guest (d0v0)
>> (XEN) rax: 0000000000000029   rbx: 000000000000000a   rcx: ffffffff822611c8
>> (XEN) rdx: 0000000000000000   rsi: 0000000000000000   rdi: 0000000000000000
>> (XEN) rbp: ffffffff82203e00   rsp: ffffffff82203d68   r8:  657661656c20676e
>> (XEN) r9:  0000000000000007   r10: ffffffff82203d84   r11: 0000000000000029
>> (XEN) r12: 0000000000000100   r13: 0000000000000340   r14: 0000000000000440
>> (XEN) r15: ffffffff82203dc0   cr0: 0000000080050033   cr4: 00000000000406a0
>> (XEN) cr3: 00000000b620a000   cr2: 0000000000000000
>> (XEN) fsb: 0000000000000000   gsb: ffffffff82480000   gss: 0000000000000000
>> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
>> (XEN) Guest stack trace from rsp=ffffffff82203d68:
>> (XEN)    ffffffff822611c8 0000000000000029 ffffffff824b49cd 000000010000e030
>> (XEN)    0000000000010086 ffffffff82203da0 000000000000e02b 0000044000000007
>> (XEN)    0000000000000340 0000000000000020 ffffffff82203df0 0000024000000100
>> (XEN)    0000000000000000 a6f6a292a6f6a200 ffffffff82203e28 ffffffff81e08d80
>> (XEN)    0000000000000000 0000000000000000 0000000000000000 ffffffff82203e60
>> (XEN)    ffffffff824b4342 ffffffff82203e28 ffffffff8101f2a6 ffffffff82203e28
>> (XEN)    ffffffff81040900 ffffffff81040ae2 00000800000806e9 0789dbf5def82203
>> (XEN)    a6f6a292a6f6a200 0000000000000018 ffffffff82203e78 ffffffff82203e88
>> (XEN)    ffffffff824b56b0 ffffffff824b56b0 0000000001000000 ffffffff82203f00
>> (XEN)    ffffffff82203ef0 ffffffff824b07aa ffffffff00000010 ffffffff82203f00
>> (XEN)    ffffffff82203eb8 a6f6a292a6f6a200 ffffffff82203e68 a6f6a292a6f6a200
>> (XEN)    ffffffff82203f60 ffffffff82203f5c 0000000000000000 0000000000000000
>> (XEN)    0000000000000000 ffffffff82203f30 ffffffff824a4d0c a6f6a292a6f6a200
>> (XEN)    0000000000000000 ffffffff82203f60 ffffffff82203f5c 0000000000000000
>> (XEN)    0000000000000000 ffffffff82203f40 ffffffff824a42d5 ffffffff82203ff8
>> (XEN)    ffffffff824ad145 000806e900000000 0000000100000800 0300000100000032
>> (XEN)    0000000000000005 0000000000000000 0000000000000000 0000000000000000
>> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
>> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
>> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
>> (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds.
>> (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
>> #############################################################################
>>
>>
>> One thing is for sure, that there is no virtualization-related issue,
>> as xen-dom0 is starting in PV mode only.
> 
> It is a kernel problem under some compile conditions. See for example
> https://lists.xenproject.org/archives/html/xen-devel/2018-02/msg00010.html
> and the patch at
> https://lists.xenproject.org/archives/html/xen-devel/2018-02/msg00045.html

No, those are different.

There is no way to tell what led to the crash without further data
(dom0 kernel version, kernel boot parameters, mapping of function names
to kernel addresses on the guest stack).

What can be said, however, is that nested virtualization is often a
problem and might be the cause here, too.


Juergen

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel