On 10/05/2011 10:29 PM, Robin Lee Powell wrote:
>
> #
> # (For a higher level overview, try: perf report --sort comm,dso)
> #
>
> How helpful is that? -_-
>
> I'm guessing I need --guestkallsyms= ; since they're all the same
> kernel I thought it'd figure it out. I'll redo.
OK, here's a
On Wed, Oct 05, 2011 at 11:36:53AM -0700, Robin Lee Powell wrote:
> On Wed, Oct 05, 2011 at 08:21:53PM +0200, Avi Kivity wrote:
> > On 10/04/2011 09:40 PM, Robin Lee Powell wrote:
> > >> >When I run tcpdump on a *guest*, the entire guest completely
> > >> >freezes up; no response even to hitting
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 everyt
> 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.
On Sun, Oct 02, 2011 at 03:38:29PM -0400, Avi Kivity wrote:
>
> > >
> > > Well, any messages?
> >
> > None I can find. I'll try again later today and double check.
>
>
> Please do.
Oct 2 19:53:01 vrici dbus: [system] Activating service
name='net.reactivated.Fprint' (using servicehelper)
Oc
> >
> > Well, any messages?
>
> None I can find. I'll try again later today and double check.
Please do.
>
> > 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
On Sun, Oct 02, 2011 at 07:21:08PM +0200, Avi Kivity wrote:
> On 10/02/2011 07:13 PM, Robin Lee Powell wrote:
> >On Sun, Oct 02, 2011 at 07:12:42PM +0200, Avi Kivity wrote:
> >> On 10/02/2011 07:07 PM, Robin Lee Powell wrote:
> >> >On Sun, Oct 02, 2011 at 07:06:35PM +0200, Avi Kivity wrote:
> >>
On 10/02/2011 07:13 PM, Robin Lee Powell wrote:
On Sun, Oct 02, 2011 at 07:12:42PM +0200, Avi Kivity wrote:
> On 10/02/2011 07:07 PM, Robin Lee Powell wrote:
> >On Sun, Oct 02, 2011 at 07:06:35PM +0200, Avi Kivity wrote:
> >> On 10/02/2011 02:45 AM, Robin Lee Powell wrote:
> >> >I'm afrai
On Sun, Oct 02, 2011 at 07:12:42PM +0200, Avi Kivity wrote:
> On 10/02/2011 07:07 PM, Robin Lee Powell wrote:
> >On Sun, Oct 02, 2011 at 07:06:35PM +0200, Avi Kivity wrote:
> >> On 10/02/2011 02:45 AM, Robin Lee Powell wrote:
> >> >I'm afraid clocksource=hpet didn't help much; after about 24 hour
On 10/02/2011 07:07 PM, Robin Lee Powell wrote:
On Sun, Oct 02, 2011 at 07:06:35PM +0200, Avi Kivity wrote:
> On 10/02/2011 02:45 AM, Robin Lee Powell wrote:
> >I'm afraid clocksource=hpet didn't help much; after about 24 hours
> >up, tcpdump hung the machine for for about 10 seconds. That ma
On Sun, Oct 02, 2011 at 07:06:35PM +0200, Avi Kivity wrote:
> On 10/02/2011 02:45 AM, Robin Lee Powell wrote:
> >I'm afraid clocksource=hpet didn't help much; after about 24 hours
> >up, tcpdump hung the machine for for about 10 seconds. That may or
> >may not be better than usual; I haven't been
On 10/02/2011 02:45 AM, Robin Lee Powell wrote:
I'm afraid clocksource=hpet didn't help much; after about 24 hours
up, tcpdump hung the machine for for about 10 seconds. That may or
may not be better than usual; I haven't been timing things
precisely. My suspicion is that it's slightly better,
I'm afraid clocksource=hpet didn't help much; after about 24 hours
up, tcpdump hung the machine for for about 10 seconds. That may or
may not be better than usual; I haven't been timing things
precisely. My suspicion is that it's slightly better, but it's
still not great.
Also:
rlpowell@vrici>
well, give it a try ;)
I still haven't fully resolved this, but I'm sure it has to do something with
the timesource - with kvm-clock, it got much worse...
n.
> [1.911056] Override clocksource tsc is not HRT compatible. Cannot switch
> while in HRT/NOHZ mode
>
> Will hpet do any better?
>
>
On Fri, Sep 30, 2011 at 09:03:21PM +0200, Nikola Ciprich wrote:
> Hello Robin,
>
> actually I'm stil hitting problems with tcpdump in KVM virtuals..
> what is the content of
> /sys/devices/system/clocksource/clocksource0/current_clocksource?
> I guess it'll be kvm-clock, try using clocksource=tsc
15 matches
Mail list logo
