All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Leimbach <felix.leimbach@gmx.net>
To: kvm@vger.kernel.org
Subject: Re: KVM-74 and network timeout?
Date: Thu, 18 Sep 2008 11:13:26 +0200	[thread overview]
Message-ID: <48D21BB6.4050308@gmx.net> (raw)
In-Reply-To: <1890.192.168.75.50.1221707418.squirrel@192.168.75.51>

Sean Mahrt wrote:
> I’ve noticed the guest with a lot of Disk I/O
> (commercial detection) after a while has a lot of NFS timeouts….  Virtio
> or E1000 give me the same result.

I noticed exactly the same problem after moving from kvm-64 on a
2.6.25.3 host to kvm-74 on a 2.6.26.3 host.

Adding to your observations:
- CIFS shares are affected as well: Under heavy traffic I get timeouts
from the server, see [1]
- ne2k_pci and rtl8139 guests seem to be affected as well

> Now the real bad part, I’m getting
> pings in the order of ms, like 20-100ms on a bridged connection… and NFS
> is going crazy...

My pings also increased from < 0.1ms to 16ms when the physical interface
of the bridge was maxed out.
Don't know, whether transferring from VM to VM would also trigger that.

>  I’m using smp on the guests (and the host), and 2.6.25 on the guests…

My guests where UP and mostly Windows Server 2003 and one Gentoo 2.6.26,
so I think the culprit is elsewhere.

> Where should I start looking?  Is this a KVM-74 issue?  Bump to KVM-75?

You might try kvm-64 which is rock-solid for me when paired with a
2.6.25 KVM kernel module.

[1]
Sep 6 17:42:58 kernsrc@obelix CIFS VFS: server not responding
Sep 6 17:42:58 kernsrc@obelix CIFS VFS: No response to cmd 46 mid 30836
Sep 6 17:42:58 kernsrc@obelix CIFS VFS: Send error in read = -11
Sep 6 17:51:28 kernsrc@obelix CIFS VFS: server not responding
Sep 6 17:51:28 kernsrc@obelix CIFS VFS: No response for cmd 50 mid 30850


  reply	other threads:[~2008-09-18  9:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18  3:10 KVM-74 and network timeout? Sean Mahrt
2008-09-18  9:13 ` Felix Leimbach [this message]
2008-09-18 13:51   ` Daniel Godás

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=48D21BB6.4050308@gmx.net \
    --to=felix.leimbach@gmx.net \
    --cc=kvm@vger.kernel.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.