From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: xen-devel@lists.xensource.com, jeremy.fitzhardinge@citrix.co,
stefano.stabellini@eu.citrix.com
Subject: Re: FC15: 32-bit PV guest crash on restore on x64_86 host
Date: Wed, 4 May 2011 16:19:51 -0400 [thread overview]
Message-ID: <20110504201951.GB2117@dumpdata.com> (raw)
In-Reply-To: <4DC1AFC9.2070407@redhat.com>
On Wed, May 04, 2011 at 09:58:01PM +0200, Igor Mammedov wrote:
> On restore 32bit PV guest crashes on x64_86 host, while x64_86 PV guest
> works as expected.
>
> Bisecting of upstream kernel shows following offending commit:
Can you try the patches in devel/p2m-e820-pci.v2
(git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git)
>
> commit 448f2831934381e9d3c4d93e700ba7bbe14612dc
> Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> Date: Wed Dec 15 13:19:33 2010 +0000
>
> xen: add m2p override mechanism
>
>
> More details from https://bugzilla.redhat.com/show_bug.cgi?id=700752
>
> excerpt from hypervisor.log:
Can you attach the full bootup log of the DomU? I am curios of the
memory layout. And also the guest config.
>
> (XEN) mm.c:630:d16 Non-privileged (16) attempt to map I/O space 2712536c5e
> (XEN) mm.c:3619:d16 ptwr_emulate: fixing up invalid PAE PTE c082712536c5e063
> (XEN) /builddir/build/BUILD/kernel-2.6.18/xen/include/asm/mm.h:225:d16 Error
> pfn 36c5b: rd=ffff8300afdca080, od=ffff8300af1f0080, caf=80000002,
> taf=00000000e8000001
> (XEN) mm.c:654:d16 Error getting mfn 36c5b (pfn 3b325b) from L1 entry
> 0000000036c5b063 for dom16
> (XEN) mm.c:3619:d16 ptwr_emulate: fixing up invalid PAE PTE 0000000036c5b063
> (XEN) Pagetable walk from 00000000eb40ff98:
> (XEN) L4[0x000] = 0000000066ad4027 0000000000027494
> (XEN) L3[0x003] = 0000000066eae027 0000000000027492
> (XEN) L2[0x15a] = 0000000237400067 0000000000001600
> (XEN) L1[0x00f] = 80000002373f8061 000000000002b40f
> (XEN) domain_crash_sync called from entry.S
> (XEN) Domain 16 (vcpu#0) crashed on cpu#1:
> (XEN) ----[ Xen-3.1.2-257.el5 x86_64 debug=n Not tainted ]----
> (XEN) CPU: 1
> (XEN) RIP: 0061:[<00000000c04047ee>]
> (XEN) RFLAGS: 0000000000010213 CONTEXT: guest
> (XEN) rax: 00000000f4d78000 rbx: 00000000eb4aea40 rcx: 000000000000007b
> (XEN) rdx: 00000000eb4aea40 rsi: 00000000eb410024 rdi: 00000000c0827117
> (XEN) rbp: 00000000eb40ffa0 rsp: 00000000eb40ffa0 r8: 0000000000000000
> (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
> (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000
> (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000006f0
> (XEN) cr3: 0000000250002000 cr2: 00000000f4d78008
> (XEN) ds: 007b es: 007b fs: 00d8 gs: 00e0 ss: 0069 cs: 0061
> (XEN) Guest stack trace from esp=eb40ffa0:
> (XEN) eb41001c c0827152 36c5d063 80000002 36c5c063 80000002 36c5b062 00000000
> (XEN) 00000008 eb4aea40 00000000 80000002 36c58063 80000002 36c57063 80000002
> (XEN) 36c56063 80000002 36c55063 80000002 36c54063 80000002 36c53063 80000002
> (XEN) mm.c:630:d0 Non-privileged (16) attempt to map I/O space 00000000
>
> gdb guest kernel stack trace:
> #0 0xc04047ee in xen_read_cr2 () at arch/x86/xen/mmu.c:1244
> #1 0xc0827152 in read_cr2 (regs=0xeb410024, error_code=0)
> at
> /usr/src/debug/kernel-2.6.38.fc15/linux-2.6.38.i686/arch/x86/include/asm/paravirt.h:64
> #2 do_page_fault (regs=0xeb410024, error_code=0) at arch/x86/mm/fault.c:974
> #3<signal handler called>
> ...
>
>
>
next prev parent reply other threads:[~2011-05-04 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 19:58 FC15: 32-bit PV guest crash on restore on x64_86 host Igor Mammedov
2011-05-04 20:19 ` Konrad Rzeszutek Wilk [this message]
2011-05-04 21:03 ` Igor Mammedov
2011-05-04 21:13 ` Konrad Rzeszutek Wilk
2011-05-05 13:32 ` Stefano Stabellini
2011-05-05 21:28 ` Konrad Rzeszutek Wilk
2011-05-06 16:16 ` Igor Mammedov
2011-05-06 17:12 ` Konrad Rzeszutek Wilk
2011-05-06 17:41 ` Igor Mammedov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110504201951.GB2117@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=imammedo@redhat.com \
--cc=jeremy.fitzhardinge@citrix.co \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).