[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Re: [Xen-users] boot a existing windows in hvm domain
On 7/8/07 10:06, "Brady Chen" <chenchp@xxxxxxxxx> wrote: > the dmesg shows some instructions have being simulated. > so they should be the codes just before d0900 or d0800, am i right? No. What is happening is that vmxassist is trying to emulate as far as it can into real-mode execution at around linear address d71b-d71f, until it sees an instruction that it cannot decode. When it sees an instruction it does not understand it prints out "opc <opcode number>". Since there is no such output immediately before the trap, this means that vmxassist was still in its emulation loop and vmxassist itself crashed. This makes sense because the faulting eip is somewhere in vmxassist's code (albeit not on an instruction boundary!). The faulting linear address is definitely d0800, so that is the interesting area of the vmxassist objdump. What would be useful is to try to add tracing to see how far vmxassist gets after its last line of tracing before the trap occurs. That last line is currently from vm86.c, line 620. You might try adding extra printf() statements imemdiately after the write16() on line 622, and also at the top of the opcode() function. We need to find out at what point vmxassist is jumping to this bogus address d0800. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |