public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Arne Kepp <ak@openplans.org>
To: kvm-devel@lists.sourceforge.net
Subject: eth0: transmit timed out
Date: Sun, 24 Feb 2008 19:48:33 -0500	[thread overview]
Message-ID: <47C21061.3080407@openplans.org> (raw)

Hi,

I am running KVM 61 on CentOS 5.1 x86_64 (on a Dell PowerEdge 2950 
III).  I start my virtual machine as follows:
qemu-kvm -hda /dev/kvm_sdb/geust_root -m 1024 -net tap -net 
nic,vlan=0,macaddr=00:16:3e:00:00:02 -daemonize -nographic -smp 2

The problem is that when the guest (also CentOS 5.1 x86_64) utilizes the 
network heavily (scp to a machine on the same switch, around 12 mbyte/s) 
the network on the virtual machine just drops out.

I can no longer ping the virtual machine, and any existing SSH sessions 
die. If I connect to the virtual machine using VNC everything looks okay 
(eth0 is up, routes are okay), but I still cannot connect to anything. 
All other virtual machines on the same host continue to work as if 
nothing has happened. The same problem occurred in -58 and -59.

/var/log/messages on the guest says:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: link up, 100Mbps, full-duplex, lpa 0x05E1

Any suggestions (permanent fixes or temporary workarounds, I'll take 
what you got) would be much appreciated.

Thanks for all the great work :)
-Arne

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

             reply	other threads:[~2008-02-25  0:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25  0:48 Arne Kepp [this message]
2008-02-25  2:51 ` eth0: transmit timed out david ahern
2008-02-25  4:07   ` Arne Kepp
2008-02-25  4:39     ` david ahern

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=47C21061.3080407@openplans.org \
    --to=ak@openplans.org \
    --cc=kvm-devel@lists.sourceforge.net \
    /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