Hi Keir,
the whole dmesg and a new objdump is attached.
# tar zcvf xendmesg_vmxdump.tar.gz xen_dmesg vmxassist.objdump2
xen_dmesg
vmxassist.objdump2
here are some snip for your convenience:
(XEN) HVM2: 0x0000D71F: 0xD00:0x071F (0) data32
(XEN) HVM2: 0x0000D71F: 0xD00:0x071F (0) opc 0x83
(XEN) HVM2: 0x0000D71B: 0xD00:0x071B (0) %es:
(XEN) HVM2: 0x0000D71B: 0xD00:0x071B (0) addr32
(XEN) HVM2: 0x0000D71D: 0xD00:0x071D (0) movw %ax, *0xD07FE
(XEN) HVM2: Trap (0x6) while in real mode
(XEN) HVM2: eax D00 ecx 0 edx 71F ebx 71E
(XEN) HVM2: esp D74D4 ebp D7520 esi D74B0 edi D00
(XEN) HVM2: trapno 6 errno 0
(XEN) HVM2: eip D0800 cs 10 eflags 13046
(XEN) HVM2: uesp D75B4 uss 2
(XEN) HVM2: ves D4BC8 vds D4D26 vfs D07FE vgs D7534
(XEN) HVM2: cr0 50032 cr2 0 cr3 0 cr4 651
(XEN) HVM2:
(XEN) HVM2: Halt called from %eip 0xD037C
 d07f7: 89 f8 mov %edi,%eax
 d07f9: 8b 5d f4 mov 0xfffffff4(%ebp),%ebx
 d07fc: 8b 75 f8 mov 0xfffffff8(%ebp),%esi
 d07ff: 25 ff ff 00 00 and 0ドルxffff,%eax
 d0804: 8b 7d fc mov 0xfffffffc(%ebp),%edi
 d0807: 89 ec mov %ebp,%esp
 d0809: c1 e0 04 shl 0ドルx4,%eax
 d080c: 01 d0 add %edx,%eax
 d08f7: 8b 56 2c mov 0x2c(%esi),%edx
 d08fa: 89 44 24 04 mov %eax,0x4(%esp)
 d08fe: c7 04 24 2e 4b 0d 00 movl 0ドルxd4b2e,(%esp)
 d0905: 89 54 24 08 mov %edx,0x8(%esp)
 d0909: e8 c2 30 00 00 call d39d0 <printf>
 d090e: a1 00 76 0d 00 mov 0xd7600,%eax
the dmesg shows some instructions have being simulated.
so they should be the codes just before d0900 or d0800, am i right?
On 8/7/07, Keir Fraser <keir@xxxxxxxxxxxxx> wrote:
> On 7/8/07 09:22, "Brady Chen" <chenchp@xxxxxxxxx> wrote:
>
> > Hi, here the output, you could get the whole dump from the attachment
> > of my last mail.
>
> Oh, I missed that!
>
> > so, there should be a non-support instruction in 0xd0900 or 0xd0800?
>
> Well, there is no instruction boundary at either of those addresses. Either
> the register dump is bogus or somehow we ended up jumping into the middle of
> an instruction inside vmxassist. Bogus. :-(
>
> You could try initialising the traceset variable in vmxassist/vm86.c to ~0
> instead of 0. That should get you a whole load of extra tracing about
> exactly what vmxassist is emulating and where. We might be able to work out
> a bit more from that.
>
> -- Keir
>
>

Attachment: xendmesg_vmxdump.tar.gz
Description: GNU Zip compressed data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel