Re: Q: Stopped VM still using host cpu CPU ?

[Avi Kivity <avi@redhat.com>]

On 10/21/2009 10:29 PM, Daniel Schwager wrote:
>
> **** opreport -l  --symbols | less
> CPU: CPU with timer interrupt, speed 0 MHz (estimated)
> Profiling through timer interrupt
> samples  %        image name               app name
> symbol name
> 418814   98.5250  no-vmlinux               no-vmlinux               (no
> symbols)
> 1228      0.2889  qemu-system-x86_64       qemu-system-x86_64
> main_loop_wait
> 888       0.2089  libpthread-2.8.so        libpthread-2.8.so
> __read_nocancel
> ...
>
>    

Sorry, I gave you the wrong instructions.  Since most of the time is 
spent in vmlinux, we want to trace vmlinux, not qemu.

Three ways to see what is happening:

- set up vmlinux (you'll need to install the correct kernel-debuginfo 
package to get this).
- strace -p `pgrep qemu` and see what syscalls take place
- run 'top' and look at the wchan field ('f' 'y' will show it if it is 
hidden)

Probably easiest in reverse order as listed.

-- 
error compiling committee.c: too many arguments to function