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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> On 10/04/2009 05:21 PM, Daniel Schwager wrote:
> >
> >> How long is this after the 'stop'?
> >>
> > 30 seconds or 2 days ... the process takes CPU all the time
> >
> 
> Can you take an oprofile run to see where it's spending its time?

I'm not that familiar with oprofile ... 

so, setup with
	opcontrol --deinit; modprobe oprofile timer=1; opcontrol --start

gave me the following result:

kvm03:~# opreport
CPU: CPU with timer interrupt, speed 0 MHz (estimated)
Profiling through timer interrupt
          TIMER:0|
  samples|      %|
------------------
   613327 95.3150 no-vmlinux
    12416  1.9295 qemu-system-x86_64
                  TIMER:0|
          samples|      %|
        ------------------
            10888 87.6933 qemu-system-x86_64
              209  1.6833 [vdso] (tgid:2164
range:0x7ffff37ff000-0x7ffff3800000)
              171  1.3773 [vdso] (tgid:28126
range:0x7fffe7dff000-0x7fffe7e00000)
              168  1.3531 [vdso] (tgid:11172
range:0x7ffff67fe000-0x7ffff67ff000)
              147  1.1840 [vdso] (tgid:1511
range:0x7fff741fe000-0x7fff741ff000)
              143  1.1517 [vdso] (tgid:28327
range:0x7fffdcbfe000-0x7fffdcbff000)
              141  1.1356 [vdso] (tgid:17010
range:0x7fff2a1fe000-0x7fff2a1ff000)
              127  1.0229 [vdso] (tgid:27527
range:0x7fff2cffe000-0x7fff2cfff000)
              111  0.8940 [vdso] (tgid:27644
range:0x7fffec7fe000-0x7fffec7ff000)
               92  0.7410 [vdso] (tgid:11565
range:0x7fff247fe000-0x7fff247ff000)
               81  0.6524 [vdso] (tgid:27438
range:0x7fff7c3fe000-0x7fff7c3ff000)
               76  0.6121 [vdso] (tgid:26857
range:0x7ffffa7fe000-0x7ffffa7ff000)
               62  0.4994 [vdso] (tgid:1676
range:0x7fff2f5ff000-0x7fff2f600000)
    11488  1.7853 libpthread-2.8.so
	....


Try to start without timer=1 hung up my physical machine after daemon is
started:
kvm03:/opt/kvm-86-vnc-patch# opcontrol --deinit; modprobe oprofile ;
opcontrol --start
Stopping profiling.
Killing daemon.
Unloading oprofile module
Using default event: CPU_CLK_UNHALTED:100000:0:1:1
Using 2.6+ OProfile kernel interface.
Using log file /var/lib/oprofile/samples/oprofiled.log
Daemon started.


Could I give you more information ? Should I setup oprofile in another
way ?

regards
Danny

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux