qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chris Webb <chris@arachsys.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Intermittent e1000 failure on qemu-kvm 1.0
Date: Tue, 3 Apr 2012 09:13:16 +0100	[thread overview]
Message-ID: <20120403081313.GD1283@arachsys.com> (raw)
In-Reply-To: <20120403071328.GB27304@stefanha-thinkpad.localdomain>

Stefan Hajnoczi <stefanha@gmail.com> writes:

> On Mon, Apr 02, 2012 at 04:37:23PM +0100, Chris Webb wrote:
> > We initially saw a problem after an upgrade from 0.15.x to 1.0.
> 
> Perhaps git-bisect(1) can help you track down the change that introduced
> this between 0.15 and 1.0.

Hi. I attempted this, but the bug is so intermittent and there are so many
unrelated red-herring breakages along the branchy path between the two that
I had to abandon the effort after a week I'm afraid. It's phenomenally time
consuming, unlike any other bug I've tried to bisect.

> It sounds like this is not the issue, but are you sure the bridge has
> forwarding delay set to 0 or Spanning Tree Protocol disabled?  With STP
> enabled no traffic will be forwarded by the bridge for a configured
> timeout, and depending on the timing of your VM bootup you could see
> weird things.  You can check with brctl showstp br0.

No STP enabled, but the networking is permanently broken on these guests in
any case, not just slow to get started. Usually they've been sat there for
half an hour or more by the time I get back to the stopped reboot loop, and
I left one broken over a weekend without it fixing itself. The network is
statically configured, so if it were down temporarily and came back, pings
would then start working fine.

Cheers,

Chris.

  reply	other threads:[~2012-04-03  8:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 15:37 [Qemu-devel] Intermittent e1000 failure on qemu-kvm 1.0 Chris Webb
2012-04-03  7:13 ` Stefan Hajnoczi
2012-04-03  8:13   ` Chris Webb [this message]
2012-04-03  8:26     ` Stefan Hajnoczi
2012-04-03 12:42       ` Chris Webb
2012-04-03 13:34         ` Stefan Hajnoczi
2012-04-03 13:41           ` Chris Webb
2012-04-03 15:36             ` Stefan Hajnoczi
2012-04-03 16:37               ` Chris Webb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120403081313.GD1283@arachsys.com \
    --to=chris@arachsys.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).