Akasha
2011-Mar-15 09:19 UTC
[Xen-devel] ASSERT failed in ept_sync_domain when mem_sharing opened!
Hi,
Now I open the memory sharing of VM . But I had only one VM with one VCPU
running.
the ASSERT is of p2m_locked_by_me(d->arch.p2m).
But when trace the route of memory sharing, I found there is no code such
as p2m_lock().
Maybe some one had pick this out before, please enlighten me, thanks a lot!
----pengfei zhang
this is the the stack trace log:
irq.c:243: Dom1 PCI link 1 changed 10 -> 0
(XEN) irq.c:243: Dom1 PCI link 2 changed 11 -> 0
(XEN) irq.c:243: Dom1 PCI link 3 changed 5 -> 0
(XEN) irq.c:306: Dom1 callback via changed to PCI INTx Dev 0x03 IntA
(XEN) Assertion ''(((get_cpu_info()->current_vcpu))->processor
=(d->arch.p2m)->locker)'' failed at vmx.c:1229
(XEN) ----[ Xen-4.0.0 x86_64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e008:[] ept_sync_domain+0x78/0xcd
(XEN) RFLAGS: 0000000000010213 CONTEXT: hypervisor
(XEN) rax: 0000000000000000 rbx: 0000000000000001 rcx: ffff8302597d0000
(XEN) rdx: ffff8302586d5950 rsi: 000000000000000d rdi: ffff8302597d0000
(XEN) rbp: ffff82c48037faa8 rsp: ffff82c48037fa98 r8: 0000000000000000
(XEN) r9: 00000000deadbeef r10: ffff82c48020e770 r11: 0000000000000282
(XEN) r12: ffff8302597d0000 r13: 0000000000000000 r14: 0000000000000001
(XEN) r15: ffff82c48037fb50 cr0: 0000000080050033 cr4: 00000000000026f0
(XEN) cr3: 000000022aac0000 cr2: 000000000042e270
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) Xen stack trace from rsp=ffff82c48037fa98:
(XEN) 0000000000000001 0000000000000000 ffff82c48037fb88 ffff82c4801f4182
(XEN) ffff82c48037fb08 0000000000000092 ffff82c48037fb38 000000000000000d
(XEN) ffff82c48037fb48 000000000000000d 000000000000f614 ffff8302597d0000
(XEN) 8000000000000000 0000000000000000 ffff8302988c60a0 000000008016ed9e
(XEN) 0000000000000040 000000000029f614 ffff82c4801496bd 000000000029f629
(XEN) 0000000000000014 01ff8302988c6000 0000000000000014 ffff8302988c6000
(XEN) ffff8302597d0000 000000000029f629 0000000000000000 0000000000000001
(XEN) ffff8302597d0000 000000000000f614 ffff82c48037fbc8 ffff82c4801c0d9b
(XEN) 000000010000000d 000000000029f614 ffff8302597d0000 000000000000f614
(XEN) 000000000029f629 ffff82f6053ec280 ffff82c48037fc08 ffff82c4801c6e72
(XEN) ffff83023331f890 0000000d586d5f50 ffff8302597d0000 ffff83023331f890
(XEN) ffff8302586d5f50 ffff83023331f868 ffff82c48037fc68 ffff82c4801c92a1
(XEN) 0000000000000004 0000000000000004 ffff83023331f850 ffff82f6053ec520
(XEN) ffff8302586d5f68 ffff82c48037fe58 ffff83023fe50000 00000000006f8000
(XEN) 0000000000000006 0000000000000006 ffff82c48037fc98 ffff82c4801ca35c
(XEN) 0000000000000004 ffff82c48037fc98 00000000006f8000 fffffffffffffff3
(XEN) ffff82c48037fdb8 ffff82c48014ba1d ffff82c48037fce8 00000000002798c4
(XEN) 0000000000000000 0000000000000000 ffff82c48037fe48 ffff83023fe50000
(XEN) ffff82c48037fd18 0000000004f31880 5000000000000000 ffff82f606031400
(XEN) 00000000003018a0 ffffffffffffffff ffff82c48037fd18 ffff82c4801639c7
(XEN) Xen call trace:
(XEN) [] ept_sync_domain+0x78/0xcd
(XEN) [] ept_set_entry+0x6ce/0x7e3
(XEN) [] set_p2m_entry+0x7f/0xc0
(XEN) [] set_shared_p2m_entry+0x150/0x21e
(XEN) [] mem_sharing_share_pages+0x25d/0x38b
(XEN) [] mem_sharing_domctl+0xde/0x142
(XEN) [] arch_do_domctl+0x20cd/0x21be
(XEN) [] do_domctl+0x1177/0x1205
(XEN) [] syscall_enter+0xef/0x149
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Assertion ''(((get_cpu_info()->current_vcpu))->processor
=(d->arch.p2m)->locker)'' failed at vmx.c:1229
(XEN) ****************************************
(XEN)
(XEN) Manual reset required (''noreboot'' specified)
--
View this message in context:
http://xen.1045712.n5.nabble.com/ASSERT-failed-in-ept-sync-domain-when-mem-sharing-opened-tp3693174p3693174.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Akasha
2011-Mar-15 11:00 UTC
[Xen-devel] ASSERT failed in ept_sync_domain when mem_sharing opened!
Hi,
Now I open the memory sharing of VM . But I had only one VM with one VCPU
running.
the ASSERT is of p2m_locked_by_me(d->arch.p2m).
But when trace the route of memory sharing, I found there is no code such
as p2m_lock().
Maybe some one had pick this out before, please enlighten me, thanks a lot!
----pengfei zhang
this is the the stack trace log:
irq.c:243: Dom1 PCI link 1 changed 10 -> 0
(XEN) irq.c:243: Dom1 PCI link 2 changed 11 -> 0
(XEN) irq.c:243: Dom1 PCI link 3 changed 5 -> 0
(XEN) irq.c:306: Dom1 callback via changed to PCI INTx Dev 0x03 IntA
(XEN) Assertion ''(((get_cpu_info()->current_vcpu))->processor
=(d->arch.p2m)->locker)'' failed at vmx.c:1229
(XEN) ----[ Xen-4.0.0 x86_64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e008:[] ept_sync_domain+0x78/0xcd
(XEN) RFLAGS: 0000000000010213 CONTEXT: hypervisor
(XEN) rax: 0000000000000000 rbx: 0000000000000001 rcx: ffff8302597d0000
(XEN) rdx: ffff8302586d5950 rsi: 000000000000000d rdi: ffff8302597d0000
(XEN) rbp: ffff82c48037faa8 rsp: ffff82c48037fa98 r8: 0000000000000000
(XEN) r9: 00000000deadbeef r10: ffff82c48020e770 r11: 0000000000000282
(XEN) r12: ffff8302597d0000 r13: 0000000000000000 r14: 0000000000000001
(XEN) r15: ffff82c48037fb50 cr0: 0000000080050033 cr4: 00000000000026f0
(XEN) cr3: 000000022aac0000 cr2: 000000000042e270
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) Xen stack trace from rsp=ffff82c48037fa98:
(XEN) 0000000000000001 0000000000000000 ffff82c48037fb88 ffff82c4801f4182
(XEN) ffff82c48037fb08 0000000000000092 ffff82c48037fb38 000000000000000d
(XEN) ffff82c48037fb48 000000000000000d 000000000000f614 ffff8302597d0000
(XEN) 8000000000000000 0000000000000000 ffff8302988c60a0 000000008016ed9e
(XEN) 0000000000000040 000000000029f614 ffff82c4801496bd 000000000029f629
(XEN) 0000000000000014 01ff8302988c6000 0000000000000014 ffff8302988c6000
(XEN) ffff8302597d0000 000000000029f629 0000000000000000 0000000000000001
(XEN) ffff8302597d0000 000000000000f614 ffff82c48037fbc8 ffff82c4801c0d9b
(XEN) 000000010000000d 000000000029f614 ffff8302597d0000 000000000000f614
(XEN) 000000000029f629 ffff82f6053ec280 ffff82c48037fc08 ffff82c4801c6e72
(XEN) ffff83023331f890 0000000d586d5f50 ffff8302597d0000 ffff83023331f890
(XEN) ffff8302586d5f50 ffff83023331f868 ffff82c48037fc68 ffff82c4801c92a1
(XEN) 0000000000000004 0000000000000004 ffff83023331f850 ffff82f6053ec520
(XEN) ffff8302586d5f68 ffff82c48037fe58 ffff83023fe50000 00000000006f8000
(XEN) 0000000000000006 0000000000000006 ffff82c48037fc98 ffff82c4801ca35c
(XEN) 0000000000000004 ffff82c48037fc98 00000000006f8000 fffffffffffffff3
(XEN) ffff82c48037fdb8 ffff82c48014ba1d ffff82c48037fce8 00000000002798c4
(XEN) 0000000000000000 0000000000000000 ffff82c48037fe48 ffff83023fe50000
(XEN) ffff82c48037fd18 0000000004f31880 5000000000000000 ffff82f606031400
(XEN) 00000000003018a0 ffffffffffffffff ffff82c48037fd18 ffff82c4801639c7
(XEN) Xen call trace:
(XEN) [] ept_sync_domain+0x78/0xcd
(XEN) [] ept_set_entry+0x6ce/0x7e3
(XEN) [] set_p2m_entry+0x7f/0xc0
(XEN) [] set_shared_p2m_entry+0x150/0x21e
(XEN) [] mem_sharing_share_pages+0x25d/0x38b
(XEN) [] mem_sharing_domctl+0xde/0x142
(XEN) [] arch_do_domctl+0x20cd/0x21be
(XEN) [] do_domctl+0x1177/0x1205
(XEN) [] syscall_enter+0xef/0x149
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Assertion ''(((get_cpu_info()->current_vcpu))->processor
=(d->arch.p2m)->locker)'' failed at vmx.c:1229
(XEN) ****************************************
(XEN)
(XEN) Manual reset required (''noreboot'' specified)
--
View this message in context:
http://xen.1045712.n5.nabble.com/ASSERT-failed-in-ept-sync-domain-when-mem-sharing-opened-tp3696950p3696950.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Tim Deegan
2011-Mar-16 09:00 UTC
Re: [Xen-devel] ASSERT failed in ept_sync_domain when mem_sharing opened!
At 11:00 +0000 on 15 Mar (1300186857), Akasha wrote:> Hi, > Now I open the memory sharing of VM . But I had only one VM with one VCPU > running. > the ASSERT is of p2m_locked_by_me(d->arch.p2m). > But when trace the route of memory sharing, I found there is no code such > as p2m_lock(). > Maybe some one had pick this out before, please enlighten me, thanks a lot!Xen 4.0.0 is quite old and a far amount of cleaning up has happened since then in the mem_sharing code. Your first step should be to upgrade to te tip of Xen 4.1.0-testing (which will be 4.1.0 very soon). Cheers, Tim.> ----pengfei zhang > > this is the the stack trace log: > irq.c:243: Dom1 PCI link 1 changed 10 -> 0 > (XEN) irq.c:243: Dom1 PCI link 2 changed 11 -> 0 > (XEN) irq.c:243: Dom1 PCI link 3 changed 5 -> 0 > (XEN) irq.c:306: Dom1 callback via changed to PCI INTx Dev 0x03 IntA > (XEN) Assertion ''(((get_cpu_info()->current_vcpu))->processor => (d->arch.p2m)->locker)'' failed at vmx.c:1229 > (XEN) ----[ Xen-4.0.0 x86_64 debug=y Not tainted ]---- > (XEN) CPU: 0 > (XEN) RIP: e008:[] ept_sync_domain+0x78/0xcd > (XEN) RFLAGS: 0000000000010213 CONTEXT: hypervisor > (XEN) rax: 0000000000000000 rbx: 0000000000000001 rcx: ffff8302597d0000 > (XEN) rdx: ffff8302586d5950 rsi: 000000000000000d rdi: ffff8302597d0000 > (XEN) rbp: ffff82c48037faa8 rsp: ffff82c48037fa98 r8: 0000000000000000 > (XEN) r9: 00000000deadbeef r10: ffff82c48020e770 r11: 0000000000000282 > (XEN) r12: ffff8302597d0000 r13: 0000000000000000 r14: 0000000000000001 > (XEN) r15: ffff82c48037fb50 cr0: 0000000080050033 cr4: 00000000000026f0 > (XEN) cr3: 000000022aac0000 cr2: 000000000042e270 > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008 > (XEN) Xen stack trace from rsp=ffff82c48037fa98: > (XEN) 0000000000000001 0000000000000000 ffff82c48037fb88 ffff82c4801f4182 > (XEN) ffff82c48037fb08 0000000000000092 ffff82c48037fb38 000000000000000d > (XEN) ffff82c48037fb48 000000000000000d 000000000000f614 ffff8302597d0000 > (XEN) 8000000000000000 0000000000000000 ffff8302988c60a0 000000008016ed9e > (XEN) 0000000000000040 000000000029f614 ffff82c4801496bd 000000000029f629 > (XEN) 0000000000000014 01ff8302988c6000 0000000000000014 ffff8302988c6000 > (XEN) ffff8302597d0000 000000000029f629 0000000000000000 0000000000000001 > (XEN) ffff8302597d0000 000000000000f614 ffff82c48037fbc8 ffff82c4801c0d9b > (XEN) 000000010000000d 000000000029f614 ffff8302597d0000 000000000000f614 > (XEN) 000000000029f629 ffff82f6053ec280 ffff82c48037fc08 ffff82c4801c6e72 > (XEN) ffff83023331f890 0000000d586d5f50 ffff8302597d0000 ffff83023331f890 > (XEN) ffff8302586d5f50 ffff83023331f868 ffff82c48037fc68 ffff82c4801c92a1 > (XEN) 0000000000000004 0000000000000004 ffff83023331f850 ffff82f6053ec520 > (XEN) ffff8302586d5f68 ffff82c48037fe58 ffff83023fe50000 00000000006f8000 > (XEN) 0000000000000006 0000000000000006 ffff82c48037fc98 ffff82c4801ca35c > (XEN) 0000000000000004 ffff82c48037fc98 00000000006f8000 fffffffffffffff3 > (XEN) ffff82c48037fdb8 ffff82c48014ba1d ffff82c48037fce8 00000000002798c4 > (XEN) 0000000000000000 0000000000000000 ffff82c48037fe48 ffff83023fe50000 > (XEN) ffff82c48037fd18 0000000004f31880 5000000000000000 ffff82f606031400 > (XEN) 00000000003018a0 ffffffffffffffff ffff82c48037fd18 ffff82c4801639c7 > (XEN) Xen call trace: > (XEN) [] ept_sync_domain+0x78/0xcd > (XEN) [] ept_set_entry+0x6ce/0x7e3 > (XEN) [] set_p2m_entry+0x7f/0xc0 > (XEN) [] set_shared_p2m_entry+0x150/0x21e > (XEN) [] mem_sharing_share_pages+0x25d/0x38b > (XEN) [] mem_sharing_domctl+0xde/0x142 > (XEN) [] arch_do_domctl+0x20cd/0x21be > (XEN) [] do_domctl+0x1177/0x1205 > (XEN) [] syscall_enter+0xef/0x149 > (XEN) > (XEN) > (XEN) **************************************** > (XEN) Panic on CPU 0: > (XEN) Assertion ''(((get_cpu_info()->current_vcpu))->processor => (d->arch.p2m)->locker)'' failed at vmx.c:1229 > (XEN) **************************************** > (XEN) > (XEN) Manual reset required (''noreboot'' specified) > > > -- > View this message in context: http://xen.1045712.n5.nabble.com/ASSERT-failed-in-ept-sync-domain-when-mem-sharing-opened-tp3696950p3696950.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel-- Tim Deegan <Tim.Deegan@citrix.com> Principal Software Engineer, Xen Platform Team Citrix Systems UK Ltd. (Company #02937203, SL9 0BG) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel