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 14:41:47 +0100 [thread overview]
Message-ID: <20120403134146.GF28553@arachsys.com> (raw)
In-Reply-To: <CAJSP0QXvvHV_gC3BTjJWVX5ELEbajPsN9vb58gXXi8kd9_x1oQ@mail.gmail.com>
Stefan Hajnoczi <stefanha@gmail.com> writes:
> No, that's weird. I would have simply tried "b start_xmit" and as
> long as the binary has symbols gdb would know what to do.
I'll get another one and give it a go. There wasn't any particular reason I
gave a line number rather than a function except that I worried there might
be start_xmit in a variety of different nic models compiled into qemu so I
might end up setting the breakpoint on the wrong one. b hw/e1000.c:start_xmit
maybe?
> Are you sure no other guest has the same MAC address or IP address?
> This weird behavior sounds similar to what happens when you have
> multiple devices on a network using the same address - the results are
> very confusing :).
Yes, I agree! However, in this case there's no other guest with the same MAC
or IP address on the network. I've explicitly rechecked this to be sure, and
also deliberately varied the MAC address to something I know can't be
generated by our scripts. In any case, I'm using the same MAC and IP address
for every reboot of this VM, and usually (19 times out of 20) it works fine.
Cheers,
Chris.
next prev parent reply other threads:[~2012-04-03 13:42 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
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 [this message]
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=20120403134146.GF28553@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).