Date: Sat, 19 Sep 2015 06:11:50 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 195970] virtualbox/memory allocator problem: "dd: stdout: Cannot allocate memory" 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-195970-8-ixvuV52Rbt>