On Thu, Sep 26, 2013 at 3:20 PM, Hu Yaohui <loki2...@gmail.com> wrote:
> > > On Thu, Sep 26, 2013 at 3:07 PM, Jan Kiszka <jan.kis...@web.de> wrote: > >> On 2013-09-26 20:53, Hu Yaohui wrote: >> > Hi Jan, >> > I am working on some Nested VM related projects. Some other teammates >> have >> > made the modifications to the kvm module. >> >> And these modifications cannot cause the misguided INT3? >> > No > >> >> > Most of my work depends on his. >> > If I could not use Qemu Debug method. Could you please suggest some >> other >> > debugging methods to debug the L2 guest OS(printk, hijack kernel >> function, >> > or something else)? >> >> Remove L0 while debugging L2 and, once it works, move L1/L2 back over >> L0? Your setup seems to be pretty special with (for us) unknown >> requirements, so it's hard to suggest what to do best. >> >> I will try that. > When I remove L0 while debugging L2, it works, but When I move it back, it failed with the same error message in L2 guest. Thank you Jan! I will figure out some other methods to overcome this hurdle. > > >> In any case, you seem to be pretty much "off-track" and may either have >> to stabilize the whole stack on your own, possibly back-porting >> essential nVMX fixes from latest versions, or rebase & share your >> changes so that we can help again. >> >> Thank you! > >> Jan >> >> >> >
