Thanks a lot. So any approach to get the dynamic or static whole memory information of the guest OS ? Not the memory of each process.
Sorry for the confusion. I do use version 1.0.1. I mention not in 0.9.1 because someone has already implemented the dynamic tracing in 0.9.1, but not in the latest version. On Mon, Mar 12, 2012 at 2:20 AM, Chen Yufei <cyfde...@gmail.com> wrote: > On Mon, Mar 12, 2012 at 5:43 AM, Mulyadi Santosa > <mulyadi.sant...@gmail.com> wrote: > > Hi.... > > > > On Sun, Mar 11, 2012 at 10:12, Yue Chen <ycyc...@gmail.com> wrote: > >> I am doing some research based on the QEMU. Does anyone know how to get > >> (trace) all the instructions of the guest OS, and get all the > intermediate > >> micro-ops ? (Not in the 0.9.1 version) > > QEMU has release version 1.0.1. Why are you still using 0.9.1? > > > > > I believe it's "-d" option you're looking for. Please read qemu manual > > for further clarification and info. > > "-d" can only give a static view of what instruction is translated, > but can't get a dynamic instruction execution trace. > > > > >> Additionally, how to get the whole memory or each process' memory data > of > >> the guest OS? > > > > you wanna do that simply from Qemu's monitor? I don't think that's > > doable...or at least easily. Qemu sees guest RAM like your physical > > RAM. It doesn't differentiate which pages belongs to which process. > > You need to hook or go straight inside the guest OS, maybe using gdb > > or other tool to get the core dump of those processes. > > > >> I really appreciate your help. > > > > Hope it helps... > > > > -- > > regards, > > > > Mulyadi Santosa > > Freelance Linux trainer and consultant > > > > blog: the-hydra.blogspot.com > > training: mulyaditraining.blogspot.com > > > > > > -- > Best regards, > Chen Yufei >
