From owner-freebsd-questions@FreeBSD.ORG Tue Jun 30 06:24:41 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D4021065670 for ; Tue, 30 Jun 2009 06:24:41 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 6B4EB8FC12 for ; Tue, 30 Jun 2009 06:24:41 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from smoochies.rachie.is-a-geek.net (mailhub.lan.rachie.is-a-geek.net [192.168.2.11]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id 73DC17E837 for ; Mon, 29 Jun 2009 22:24:40 -0800 (AKDT) From: Mel Flynn To: freebsd-questions@freebsd.org Date: Mon, 29 Jun 2009 22:24:39 -0800 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <6201873e0906261104n575611bemeb3025d9e6e1ecb9@mail.gmail.com> In-Reply-To: <6201873e0906261104n575611bemeb3025d9e6e1ecb9@mail.gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906292224.39237.mel.flynn+fbsd.questions@mailing.thruhere.net> Subject: Re: vde qemu write: No buffer space available X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2009 06:24:41 -0000 On Friday 26 June 2009 10:04:13 Adam Vande More wrote: > I'm having issues with high network throughput with vde and qemu. There > are two qemu vm's each running debian lenny and they are configured for > drbd. The vm's work fine until drbd is started then the networking fails. > The only message I get(on the host side) is > > write: No buffer space available It can be a driver issue, but the error message is somewhat misleading as it can be the result of an ill-configured firewall rule. Typically this happens when no state exists for the outgoing connection. > which is echoed to console, and nothing appears in the logs. I believe > this to be an issue with vde, but I can't be certain because I can't seem > to find any way to turn on more extensive logging. Anyone have an idea how > to resolve this? You should check netstat -m to make sure there are mbufs available and if there is check your firewall. If all seems ok, try freebsd-net list for any known issues, since you didn't get any "me too's" here. You may want to specify a bit more info, like pciconf -lv for the vde device, vmstat -i at the time of the errors, ifconfig vde0 output and any firewall information (including "I don't have one" or "error persists if firewall is disabled"). -- Mel