[Xen-bugs] [Bug 1518] New: Booting guest with device assigned &

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1518

           Summary: Booting guest with device assigned & EPT enabled cause
                    xen crash
           Product: Xen
           Version: unstable
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P1
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: jiajun.xu@xxxxxxxxx


Environment:
------------
Service Arch (ia32/ia32e/IA64): ia32/ia32e
Guest Arch (ia32/ia32e/IA64): ia32/ia32e
Guest OS Type (Linux/Windows): Linux
Change Set: 20249 
Hardware: NHM-HEDT
Other:
xen-changeset:   20255:623aa5c2eaa4

pvops git:
commit b6ba0160515df96cf572f5160c471b65f5f37045
Merge: 697ebdf... d84c11c...
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>

ioemu git:
commit 743edef44f1d0da792aeb38a33bf468a4596f730
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Wed Sep 23 15:07:47 2009 +0100


Bug detailed description:
--------------------------
On NHM-HEDT, if booting guest with VT-d device and EPT enabled, system will
crash and reboot. While booting guest only with VT-d device or booting guest
only with EPT enabled has no such issue.

There is no such issue with old c/s 20187.

serial log:
##########
(XEN) [VT-D]iommu.c:1289:d0 domain_context_unmap:PCIe: bdf = 13:0.0
(XEN) [VT-D]iommu.c:1175:d0 domain_context_mapping:PCIe: bdf = 13:0.0
(XEN) [VT-D]io.c:293:d0 VT-d irq bind: m_irq = 4f device = 4 intx = 0
(XEN) HVM3: HVM Loader
(XEN) HVM3: Detected Xen v3.5-unstable
(XEN) HVM3: CPU speed is 2400 MHz
(XEN) irq.c:243: Dom3 PCI link 0 changed 0 -> 5
(XEN) HVM3: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:243: Dom3 PCI link 1 changed 0 -> 10
(XEN) HVM3: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:243: Dom3 PCI link 2 changed 0 -> 11
(XEN) HVM3: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:243: Dom3 PCI link 3 changed 0 -> 5
(XEN) HVM3: PCI-ISA link 3 routed to IRQ5
(XEN) HVM3: pci dev 01:3 INTA->IRQ10
(XEN) HVM3: pci dev 03:0 INTA->IRQ5
(XEN) HVM3: pci dev 04:0 INTA->IRQ5
(XEN) HVM3: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM3: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) domctl.c:836:d0 memory_map:add: gfn=f3000 mfn=fb400 nr_mfns=400
(XEN) Assertion '(((get_cpu_info()->current_vcpu))->processor ==
(d->arch.p2m)->locker)' failed at vmx.c:1236
(XEN) ----[ Xen-3.5-unstable  x86_64  debug=y  Not tainted ]----
(XEN) CPU:    23
(XEN) RIP:    e008:[<ffff82c4801b07bc>] ept_sync_domain+0x62/0x9c
(XEN) RFLAGS: 0000000000010217   CONTEXT: hypervisor
(XEN) rax: 0000000000000017   rbx: 0000000000000001   rcx: 0000000000000000
(XEN) rdx: ffff83032b45ac80   rsi: ffff8303020ac000   rdi: ffff8303020ac000
(XEN) rbp: ffff83033fe17b98   rsp: ffff83033fe17b98   r8:  0000000000000001
(XEN) r9:  0000000000000004   r10: 0000000000000004   r11: 0000000000000004
(XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 0000000000000001
(XEN) r15: ffff83033fe17c40   cr0: 000000008005003b   cr4: 00000000000026f0
(XEN) cr3: 00000001f9123000   cr2: 000000000045ae1c
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from rsp=ffff83033fe17b98:
(XEN)    ffff83033fe17c78 ffff82c4801e463f ffff83033fe17bc8 ffff82c48011be4b
(XEN)    ffff82c480216eb2 ffff83033fe17c00 ffff83033fe17c38 0000000000000005
(XEN)    00000000000f3000 ffff8303020ac000 ffff830300000000 0000000000000000
(XEN)    ffff830302ba2000 00000001802f4f26 0000003000000030 ffff83033fe17d10
(XEN)    ffff83033fe17c28 00000000000fb400 ffff82c48020ffa3 00ff82c48020a219
(XEN)    0000000000000000 ffff830302ba2000 ffff8303020ac000 00000000000fb400
(XEN)    0000000000000000 0000000000000001 ffff8303020ac000 00000000000f3000
(XEN)    ffff83033fe17cb8 ffff82c4801b5de3 0000000502b61000 ffff8303020ac000
(XEN)    ffffffffffffffff 00000000000f3000 00000000000fb400 00000000000f3000
(XEN)    ffff83033fe17cf8 ffff82c4801b8c01 ffff83033fe17ce8 00000004000fb400
(XEN)    00000000000fb400 0000000000000400 0000000000000000 0000000000000000
(XEN)    ffff83033fe17dc8 ffff82c480145ad7 0000000000000400 0000000000000286
(XEN)    ffff83033fe17d28 ffff83033fe17e48 ffff83033fe17d38 ffff82c480166e4d
(XEN)    ffff83033fe17d58 ffff82c48011bd54 ffff83033fe17d78 ffff8303020ac000
(XEN)    ffff83033fe17d78 ffff83033fe17da0 ffff82c480146c00 000000f7aec206c6
(XEN)    ffff83033fe17db8 0000000000000017 ffff8300bf332000 ffff8300bf334000
(XEN)    0000000000000202 00007fff5b993270 fffffffffffffff3 00007fff5b993270
(XEN)    0000000000000005 0000000000000005 ffff83033fe17f08 ffff82c48010523a
(XEN)    ffff83033fe17e18 ffff82f6005720e0 ffff83033fe17df8 0000000000000000
(XEN)    ffff83033fe17e58 ffff82c48015dbf3 ffff82c480257100 00000001aecab97b
(XEN) Xen call trace:
(XEN)    [<ffff82c4801b07bc>] ept_sync_domain+0x62/0x9c
(XEN)    [<ffff82c4801e463f>] ept_set_entry+0x6ba/0x7cf
(XEN)    [<ffff82c4801b5de3>] set_p2m_entry+0x7d/0xb1
(XEN)    [<ffff82c4801b8c01>] set_mmio_p2m_entry+0x12e/0x1f7
(XEN)    [<ffff82c480145ad7>] arch_do_domctl+0x1447/0x1a7c
(XEN)    [<ffff82c48010523a>] do_domctl+0x1069/0x10ef
(XEN)    [<ffff82c4801e71bf>] syscall_enter+0xef/0x149
(XEN)    
(XEN) 
(XEN) ****************************************
(XEN) Panic on CPU 23:
(XEN) Assertion '(((get_cpu_info()->current_vcpu))->processor ==
(d->arch.p2m)->locker)' failed at vmx.c:1236
(XEN) ****************************************
(XEN) 
(XEN) Reboot in five seconds...
(XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
##########


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs
WARNING - OLD ARCHIVES

xen-bugs

[Xen-bugs] [Bug 1518] New: Booting guest with device assigned & EPT enab
