Hi, I have a problem installing a Windows HVM with ACPI support (acpi=1). Have anyone encountered this? What am I doing wrong? I added some printks in order to debug the problem, note where esi points to. (XEN) instrlen.c:431:d1 Cannot emulate 6f at address bf96fd56 (bf96fd55, addr_by tes 4) (XEN) instrlen.c:440:d1 *org_pc opcode: (XEN) 0f 6f 06 0f 7f 07 83 c6 (XEN) 08 83 c7 08 83 e9 08 83 (XEN) esi = 00000018 (XEN) handle_mmio: failed to get instruction length (XEN) domain_crash_sync called from platform.c:1049 (XEN) Domain 1 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-3.0-unstable x86_64 debug=y Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: 0008:[<00000000bf96fd55>] (XEN) RFLAGS: 0000000000090202 CONTEXT: hvm (XEN) rax: 00000000f7dea918 rbx: 00000000e129c0da rcx: 0000000000000044 (XEN) rdx: 0000000000000008 rsi: 00000000f7dea918 rdi: 00000000e129c085 (XEN) rbp: 00000000f8674608 rsp: 00000000f86745fc r8: 0000000000000000 (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000 (XEN) r15: 0000000000000000 cr0: 0000000080010031 cr4: 00000000000006d9 (XEN) cr3: 00000000032c3000 cr2: 00000000bf93aaf2 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0010 cs: 0008 """ (XEN) instrlen.c:440:d1 *org_pc opcode: (XEN) 0f 6f 06 0f 7f 07 83 c6 (XEN) 08 83 c7 08 83 e9 08 83 """ 0F6F06 MOVQ MM0,QWORD PTR DS:[ESI] 0F7F07 MOVQ QWORD PTR DS:[EDI],MM0 83C6 08 ADD ESI,8 83C7 08 ADD EDI,8 83E9 08 SUB ECX,8 """ (XEN) esi = 00000018 """ It happens in the phase where windows is "installing devices...". Another thing, is the HVM 64bit? Thanks, Guy. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Does segment register DS have a non-zero base? The %rsi value dumped when the VCPU crashes is not 0x18. Is the value dumped there bogus? -- Keir On 5/11/07 11:45, "Guy Zana" <guy@neocleus.com> wrote:> Hi, > > I have a problem installing a Windows HVM with ACPI support (acpi=1). > > Have anyone encountered this? What am I doing wrong? > I added some printks in order to debug the problem, note where esi > points to. > > (XEN) instrlen.c:431:d1 Cannot emulate 6f at address bf96fd56 (bf96fd55, > addr_by > tes 4) > (XEN) instrlen.c:440:d1 *org_pc opcode: > (XEN) 0f 6f 06 0f 7f 07 83 c6 > (XEN) 08 83 c7 08 83 e9 08 83 > (XEN) esi = 00000018 > (XEN) handle_mmio: failed to get instruction length > (XEN) domain_crash_sync called from platform.c:1049 > (XEN) Domain 1 (vcpu#0) crashed on cpu#0: > (XEN) ----[ Xen-3.0-unstable x86_64 debug=y Not tainted ]---- > (XEN) CPU: 0 > (XEN) RIP: 0008:[<00000000bf96fd55>] > (XEN) RFLAGS: 0000000000090202 CONTEXT: hvm > (XEN) rax: 00000000f7dea918 rbx: 00000000e129c0da rcx: > 0000000000000044 > (XEN) rdx: 0000000000000008 rsi: 00000000f7dea918 rdi: > 00000000e129c085 > (XEN) rbp: 00000000f8674608 rsp: 00000000f86745fc r8: > 0000000000000000 > (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: > 0000000000000000 > (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: > 0000000000000000 > (XEN) r15: 0000000000000000 cr0: 0000000080010031 cr4: > 00000000000006d9 > (XEN) cr3: 00000000032c3000 cr2: 00000000bf93aaf2 > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0010 cs: 0008 > > """ > (XEN) instrlen.c:440:d1 *org_pc opcode: > (XEN) 0f 6f 06 0f 7f 07 83 c6 > (XEN) 08 83 c7 08 83 e9 08 83 > """ > > 0F6F06 MOVQ MM0,QWORD PTR DS:[ESI] > 0F7F07 MOVQ QWORD PTR DS:[EDI],MM0 > 83C6 08 ADD ESI,8 > 83C7 08 ADD EDI,8 > 83E9 08 SUB ECX,8 > > """ > (XEN) esi = 00000018 > """ > > It happens in the phase where windows is "installing devices...". > Another thing, is the HVM 64bit? > > Thanks, > Guy._______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Sorry, I accidently casted esi to uint8_t,
The value supposed to be 0xf7e70d58.
The PCI bars btw looks like this:
"""
(XEN) HVM4: pci dev 00:01:1 bar 20 size 00000010: 0000c001
(XEN) HVM4: pci dev 00:01:2 INTA->IRQ7
(XEN) HVM4: pci dev 00:02:0 bar 10 size 02000000: c0000008
(XEN) HVM4: pci dev 00:02:0 bar 14 size 00001000: b0000000
(XEN) HVM4: pci dev 00:03:0 bar 10 size 00000100: 0000c101
(XEN) HVM4: pci dev 00:03:0 bar 14 size 00000100: b0001000
(XEN) HVM4: pci dev 00:03:0 INTA->IRQ11
"""
I seperated non-prefetchable and prefetchable memory to two different address
space:
/*
MMIO space looks like this:
Non prefetchable mmio 0xB0000000 - 0xC0000000
Prefectchable mmio 0xC0000000 - End
*/
Thanks,
Guy.
> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk]
> Sent: Monday, November 05, 2007 1:52 PM
> To: Guy Zana; xen-devel@lists.xensource.com
> Subject: Re: Windows XP ACPI Installation
>
> Does segment register DS have a non-zero base? The %rsi value
> dumped when the VCPU crashes is not 0x18. Is the value dumped
> there bogus?
>
> -- Keir
>
> On 5/11/07 11:45, "Guy Zana" <guy@neocleus.com> wrote:
>
> > Hi,
> >
> > I have a problem installing a Windows HVM with ACPI support
> (acpi=1).
> >
> > Have anyone encountered this? What am I doing wrong?
> > I added some printks in order to debug the problem, note where esi
> > points to.
> >
> > (XEN) instrlen.c:431:d1 Cannot emulate 6f at address bf96fd56
> > (bf96fd55, addr_by tes 4)
> > (XEN) instrlen.c:440:d1 *org_pc opcode:
> > (XEN) 0f 6f 06 0f 7f 07 83 c6
> > (XEN) 08 83 c7 08 83 e9 08 83
> > (XEN) esi = 00000018
> > (XEN) handle_mmio: failed to get instruction length
> > (XEN) domain_crash_sync called from platform.c:1049
> > (XEN) Domain 1 (vcpu#0) crashed on cpu#0:
> > (XEN) ----[ Xen-3.0-unstable x86_64 debug=y Not tainted ]----
> > (XEN) CPU: 0
> > (XEN) RIP: 0008:[<00000000bf96fd55>]
> > (XEN) RFLAGS: 0000000000090202 CONTEXT: hvm
> > (XEN) rax: 00000000f7dea918 rbx: 00000000e129c0da rcx:
> > 0000000000000044
> > (XEN) rdx: 0000000000000008 rsi: 00000000f7dea918 rdi:
> > 00000000e129c085
> > (XEN) rbp: 00000000f8674608 rsp: 00000000f86745fc r8:
> > 0000000000000000
> > (XEN) r9: 0000000000000000 r10: 0000000000000000 r11:
> > 0000000000000000
> > (XEN) r12: 0000000000000000 r13: 0000000000000000 r14:
> > 0000000000000000
> > (XEN) r15: 0000000000000000 cr0: 0000000080010031 cr4:
> > 00000000000006d9
> > (XEN) cr3: 00000000032c3000 cr2: 00000000bf93aaf2
> > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0010
> cs: 0008
> >
> > """
> > (XEN) instrlen.c:440:d1 *org_pc opcode:
> > (XEN) 0f 6f 06 0f 7f 07 83 c6
> > (XEN) 08 83 c7 08 83 e9 08 83
> > """
> >
> > 0F6F06 MOVQ MM0,QWORD PTR DS:[ESI]
> > 0F7F07 MOVQ QWORD PTR DS:[EDI],MM0
> > 83C6 08 ADD ESI,8
> > 83C7 08 ADD EDI,8
> > 83E9 08 SUB ECX,8
> >
> > """
> > (XEN) esi = 00000018
> > """
> >
> > It happens in the phase where windows is "installing
devices...".
> > Another thing, is the HVM 64bit?
> >
> > Thanks,
> > Guy.
>
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel