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
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,
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 timing
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 may or
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 hours
up,
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 afraid
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
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 at the
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)
Oct 2 19:53:01
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
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
11 matches
Mail list logo
