From owner-freebsd-emulation@FreeBSD.ORG Thu Jul 14 00:09:07 2011 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE1E91065672 for ; Thu, 14 Jul 2011 00:09:07 +0000 (UTC) (envelope-from Peter.Ross@bogen.in-berlin.de) Received: from einhorn.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) by mx1.freebsd.org (Postfix) with ESMTP id 54EF38FC0C for ; Thu, 14 Jul 2011 00:09:06 +0000 (UTC) X-Envelope-From: Peter.Ross@bogen.in-berlin.de X-Envelope-To: Received: from localhost (okapi.in-berlin.de [192.109.42.117]) by einhorn.in-berlin.de (8.13.6/8.13.6/Debian-1) with ESMTP id p6DNvHD4031501 for ; Thu, 14 Jul 2011 01:57:17 +0200 Received: from 124-254-118-24-static.bb.ispone.net.au (124-254-118-24-static.bb.ispone.net.au [124.254.118.24]) by webmail.in-berlin.de (Horde Framework) with HTTP; Thu, 14 Jul 2011 09:57:17 +1000 Message-ID: <20110714095717.35581xj4rdju1pel@webmail.in-berlin.de> Date: Thu, 14 Jul 2011 09:57:17 +1000 From: "Peter Ross" To: freebsd-emulation@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) 4.3.3 X-Scanned-By: MIMEDefang_at_IN-Berlin_e.V. on 192.109.42.8 Subject: Network problems while running VirtualBox X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2011 00:09:07 -0000 Hi all, I have a problem with the network while running VirtualBox. As soon as I _run_ a VirtualBox I am not able to copy large files =20 (e.g. virtual disks or ZFS snapshots) using ssh/scp to another machine. The ssh crashes with "Write failed: Cannot allocate memory" thrown by a write(2) in /usr/src/crypto/openssh/roaming_common.c (in =20 function roaming_write). It returns the ENOMEM (an error it should =20 never return, according to the mainpage;-) It is immediately working when I stop the VirtualBox, even if the =20 VirtualBox kernel modules are still loaded. I also "replaced" the VirtualBox load with lookbusy occuping the 2GB =20 of memory the VirtualBox usually uses (to emulate the memory =20 footprint) but it still works. I experienced the problem with VirtualBox 3.2 first but the upgrade to =20 VirtualBox 4.0.8 and the base system recently did not help. > uname -a FreeBSD DellT410one.vv.fda 8.2-STABLE FreeBSD 8.2-STABLE #1: Thu Jun =20 30 17:07:18 EST 2011 =20 root@DellT410one.vv.fda:/usr/obj/usr/src/sys/GENERIC amd64 I discussed it on the -stable mailinglist before, as the link to =20 VirtualBox wasn't obvious to me at first. Scott Sipe had the same =20 experience, he started the thread: http://lists.freebsd.org/pipermail/freebsd-stable/2011-July/063172.html He comes to the same conclusion: http://lists.freebsd.org/pipermail/freebsd-stable/2011-July/063234.html > This is it -- I'm seeing the exact same thing. > > Scp dies reliably with VirtualBox running. Quit VirtualBox and I was able = to > scp about 30 large files with no errors. Once I started VirtualBox an > in-progress scp died within seconds. > > Ditto that the Kernel modules merely being loaded don't seem to make a > difference, it's VirtualBox actually running. > > virtualbox-ose-3.2.12_1 Some technical details related to my machine: http://lists.freebsd.org/pipermail/freebsd-stable/2011-July/063221.html to Scott's here: http://www.cap-press.com/misc/ A similar problem was reported by Mahlon E. Smith in September 2010: http://lists.freebsd.org/pipermail/freebsd-stable/2010-September/058708.html I became aware of it because there was the same bce(4) card involved =20 but that may be a red herring. Scott's is using em(4). At the moment it is a real showstopper for running VirtualBox/FreeBSD =20 production because I cannot backup VirtualBoxes. Mahlon gave up on it =20 and uses Citrix by now (but is still keen to have this solved). Any idea what causes the problem? I am happy to gather information, =20 applying patches etc. if it helps. Thanks for any help Peter