From: Charles Duffy <cduffy@spamcop.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Network connections stalling
Date: Thu, 02 Aug 2007 20:48:10 -0500 [thread overview]
Message-ID: <f8u1gq$rdu$1@sea.gmane.org> (raw)
In-Reply-To: <f8sus3$e6m$1@sea.gmane.org>
This loss of connectivity is still happening; at least within my
environment, it's quite reproducible. While I've eliminated the message
about being unable to set the RTC to 1024Hz by recompiling my host
kernel without CONFIG_HPET_RTC_IRQ, the host's kernel is frequently
complaining "rtc: lost some interrupts at 1024Hz".
I'm using tap-based networking (-net nic -net
tap,ifname=tap0,script=./tap0-start), where tap0 is bridged to my local
ethernet device, and outgoing network traffic from the qemu instance is
visible if I monitor traffic on the bridge.
Indeed, external responses to such traffic (ie. ARP responses) are
visible on the bridge, but evidently not to the virtual machine: the TX
counter rises when I try to ping the outside world, but the RX counter
does not. Resetting the device (ifconfig eth0 down; ifconfig eth0 up)
brings it back alive -- but this isn't an action which can trivially be
slotted into a trivial, single-threaded install script.
These same scripts have been tested on real hardware, and have not
turned up this issue. Certainly, a race condition unrelated to qemu is
possible, but I'd appreciate any insight 'yall can provide. Thank you!
next prev parent reply other threads:[~2007-08-03 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 15:56 [Qemu-devel] Network connections stalling (due to lost interrupts/ticks?) Charles Duffy
2007-08-02 22:06 ` [Qemu-devel] " Charles Duffy
2007-08-03 12:18 ` Jason Wessel
2007-08-03 19:48 ` Charles Duffy
2007-08-06 19:48 ` Charles Duffy
2007-08-03 1:48 ` Charles Duffy [this message]
2007-08-03 2:28 ` [Qemu-devel] Re: Network connections stalling Charles Duffy
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='f8u1gq$rdu$1@sea.gmane.org' \
--to=cduffy@spamcop.net \
--cc=charles@dyfis.net \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.