From owner-freebsd-bugs@freebsd.org  Sat Sep 19 06:11:50 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB7C59CE4D1
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sat, 19 Sep 2015 06:11:50 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D80AC14C2
 for <freebsd-bugs@FreeBSD.org>; Sat, 19 Sep 2015 06:11:50 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8J6BoAT099002
 for <freebsd-bugs@FreeBSD.org>; Sat, 19 Sep 2015 06:11:50 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 195970] virtualbox/memory allocator problem: "dd: stdout:
 Cannot allocate memory"
Date: Sat, 19 Sep 2015 06:11:50 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: la5lbtyi@aon.at
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: short_desc version
Message-ID: <bug-195970-8-ixvuV52Rbt@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-195970-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-195970-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Sep 2015 06:11:51 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195970

Martin Birgmeier <la5lbtyi@aon.at> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|dd: stdout: Cannot allocate |virtualbox/memory allocator
                   |memory                      |problem: "dd: stdout:
                   |                            |Cannot allocate memory"
            Version|10.1-RELEASE                |10.2-RELEASE

--- Comment #1 from Martin Birgmeier <la5lbtyi@aon.at> ---
In 10.2, the same behavior still persists. The symptom is that when VirtualBox
is running, a dd from a disk partition does not run to completion, but aborts
with the error messsage "dd: cannot allocate memory".

So, the scenario is:
- I want to low-level copy a disk partition using dd
- At the same time, a VirtualBox instance is running

Expected result:
- dd runs to completion
- VirtualBox does not affect dd

Actual result:
- As long as VirtualBox is running, dd aborts after a random number of blocks
read

Workaround:
- Do not start VirtualBox while dd is running

Is this some interaction in how the kernel allocates buffers? It surely isn't
really a userspace problem?

-- Martin

-- 
You are receiving this mail because:
You are the assignee for the bug.