Re: tcpdump locks up kvm host for a while.

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

 



On Tue, Oct 04, 2011 at 08:15:12PM +0200, Avi Kivity wrote:
> On 10/03/2011 05:03 AM, Robin Lee Powell wrote:
> >>  >  >  Alternatively, detailed instructions to reproduce?
> >>  >
> >>  >  Start a VM.  Wait a few days.  Run tcpdump.  The system
> >>  >  locks up for 30+ seconds.
> >>
> >>  How do you detect the lockup?  Are you at the console when
> >>  this happens and everything just freezes?  The entire host,
> >>  right, not guests?
> >>
> >>  Is the lockup immediate after starting tcpdump?
> >
> >Ooooh.  Oh, we're on the wrong page entirely.  This *only*
> >happens on the guests.  tcpdump on the master host causes no
> >trouble of any kind whatsoever.
> >
> >I guess I never specified that, maybe?  Shame on me, if so.
> 
> Well, the subject line does say "kvm host".

*mega-face-palm*

(the subject line is also filled with crap of my own devising; I
think I've fixed the script in question)

> >When I run tcpdump on a *guest*, the entire guest completely
> >freezes up; no response even to hitting enter on the console.
> >"virsh list" also locks up whenever it tries to print state about
> >that VM (but the others work fine), as does any other operation
> >that touches the state of that VM.  The VM takes up 100% of CPU
> >on one core while this is happening.  Eventually it gets better.
> 
> You can use 'perf kvm' to figure out where the guest is spinning.

OK, gathered with:

sudo  perf kvm --guest --host record -o /tmp/kvm_perf -a

I don't know how to read it at all, so it's at
http://users.digitalkingdom.org/~rlpowell/media/public/kvm_perf

> >>  >  That's all I have.  There are, of course, any number of details that
> >>  >  make my VMs different from yours, but they're basically straight
> >>  >  Fedora 15.  I could give arbitrary amounts of detail, but I've no
> >>  >  idea what to concentrate on.
> >>  >
> >>
> >>  host /proc/cpuinfo
> >
> >model name      : Intel(R) Core(TM)2 CPU          6600  @ 2.40GHz
> >flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow
> 
> constant_tsc indicates tsc should be good.

Yeah, that's what hte host is on.

-Robin
--
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