Hi,
On cset:18134, creating DomVTi with PV-on-HVM drivers causes the
hypervisor panic on both hp rx2620 and Tiger4.
I attached the panic message on hp rx2620.
(XEN) ia64_fault, vector=0x18, ifa=0xf0000040fb8a0010, iip=0xf4000000040638e0,
ipsr=0x0000101008226038, isr=0x0000008000000030
(XEN) General Exception: IA-64 Reserved Register/Field fault (data access).
(XEN) d 0xf000000004118080 domid 6
(XEN) vcpu 0xf0000002bd318000 vcpu 1
(XEN)
(XEN) CPU 0
(XEN) psr : 0000101008226038 ifs : 8000000000000710 ip : [<f4000000040638e0>]
(XEN) ip is at flush_vtlb_for_context_switch+0x20/0x370
Instructions:
f4000000040638e0: 08 00 01 40 18 10 [MMI] ld8 r32=[r32]
f4000000040638e6: 20 01 38 20 20 00 ld4 r18=[r14]
f4000000040638ec: f2 07 fc 93 mov r16=32767
TEST ENVIRONMENT #1
Machine : Tiger4
Changeset : 18134:1970781956c7 (ia64/xen-unstable)
609:8a3dc4fdb478 (ia64/linux-2.6.18-xen)
126:d255b2cfdd5a (efi-vfirmware)
Dom0 OS : RHEL4 U2 (2P)
DomVTi OS : RHEL4 U2 (8P, with PV-on-HVM drivers)
CONFIG_QEMU : ioemu
TEST ENVIRONMENT #2
Machine : hp rx2620
Changeset : 18134:1970781956c7 (ia64/xen-unstable)
609:8a3dc4fdb478 (ia64/linux-2.6.18-xen)
126:d255b2cfdd5a (efi-vfirmware)
Dom0 OS : RHEL5.2 (2P)
DomVTi OS : RHEL5.2 (2P, with PV-on-HVM drivers)
CONFIG_QEMU : ioemu
Best regards,
--
KUWAMURA Shin'ya
(XEN) ia64_fault, vector=0x18, ifa=0xf0000040fb8a0010, iip=0xf4000000040638e0,
ipsr=0x0000101008226038, isr=0x0000008000000030
(XEN) General Exception: IA-64 Reserved Register/Field fault (data access).
(XEN) d 0xf000000004118080 domid 6
(XEN) vcpu 0xf0000002bd318000 vcpu 1
(XEN)
(XEN) CPU 0
(XEN) psr : 0000101008226038 ifs : 8000000000000710 ip : [<f4000000040638e0>]
(XEN) ip is at flush_vtlb_for_context_switch+0x20/0x370
(XEN) unat: 0000000000000000 pfs : 0000000000000006 rsc : 0000000000000003
(XEN) rnat: 0000000000000000 bsps: 0000000000000000 pr : 0000000000008153
(XEN) ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70433f
(XEN) csd : 0000000000000000 ssd : 0000000000000000
(XEN) b0 : f4000000040a9570 b6 : a0000002005461e0 b7 : 0000000000000000
(XEN) f6 : 000000000000000000000 f7 : 000000000000000000000
(XEN) f8 : 000000000000000000000 f9 : 000000000000000000000
(XEN) f10 : 000000000000000000000 f11 : 000000000000000000000
(XEN) r1 : a0000002005607a8 r2 : 0000000000000020 r3 : 0000000000000000
(XEN) r8 : 0000000000000000 r9 : 000000007e817c90 r10 : 0000000000000000
(XEN) r11 : 2000000000000000 r12 : e00000007e817c40 r13 : e00000007e810000
(XEN) r14 : 0000000000000000 r15 : f0000002bd319081 r16 : 0000000000000000
(XEN) r17 : 0000000000000000 r18 : 0000000000000000 r19 : 0000000000000000
(XEN) r20 : 0000000000000000 r21 : 0000000000000000 r22 : 0000000000000000
(XEN) r23 : 0000000000000000 r24 : 0000000000000000 r25 : 0000000000000000
(XEN) r26 : 0000000000000000 r27 : 0000000000000000 r28 : 0000000000000000
(XEN) r29 : 0000000000000000 r30 : 0000000000000000 r31 : 0000000000000000
(XEN)
(XEN) Call Trace:
(XEN) [<f4000000040cf2e0>] show_stack+0x80/0xa0
(XEN) sp=f0000002bd319680 bsp=f0000002bd319660
(XEN) [<f40000000408d790>] ia64_fault+0x790/0xad0
(XEN) sp=f0000002bd319850 bsp=f0000002bd319628
(XEN) [<f4000000040c7480>] ia64_leave_kernel+0x0/0x300
(XEN) sp=f0000002bd319850 bsp=f0000002bd319628
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Fault in Xen.
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|