From owner-freebsd-emulation@freebsd.org Mon Aug 22 19:54:56 2016 Return-Path: Delivered-To: freebsd-emulation@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 D0AAABC2053 for ; Mon, 22 Aug 2016 19:54:56 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id BA1AA13CF for ; Mon, 22 Aug 2016 19:54:56 +0000 (UTC) (envelope-from janm@transactionware.com) Received: by mailman.ysv.freebsd.org (Postfix) id B5E81BC2052; Mon, 22 Aug 2016 19:54:56 +0000 (UTC) Delivered-To: emulation@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 B591EBC2051 for ; Mon, 22 Aug 2016 19:54:56 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail3.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id 2D41013CD for ; Mon, 22 Aug 2016 19:54:55 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 90640 invoked by uid 907); 22 Aug 2016 19:54:53 -0000 Received: from eth222.nsw.adsl.internode.on.net (HELO [192.168.1.101]) (150.101.196.221) (smtp-auth username janm, mechanism plain) by mail3.transactionware.com (qpsmtpd/0.84) with (ECDHE-RSA-AES256-SHA encrypted) ESMTPSA; Tue, 23 Aug 2016 05:54:53 +1000 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Odd behavior with virtualbox-ose-4.3.38 From: Jan Mikkelsen In-Reply-To: Date: Tue, 23 Aug 2016 05:54:52 +1000 Cc: "freebsd-emulation@freebsd.org" Message-Id: <59E9F6CE-0F2B-40E1-B78D-AF9DFBCED280@transactionware.com> References: <2418C811-3C6E-4837-B6A5-51DB4C425EB4@transactionware.com> To: Kevin Oberman X-Mailer: Apple Mail (2.3124) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.22 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: Mon, 22 Aug 2016 19:54:56 -0000 Hi, > On 23 Aug 2016, at 02:25, Kevin Oberman wrote: >=20 > On Mon, Aug 22, 2016 at 1:50 AM, Jan Mikkelsen = > wrote: > Do you have aio loaded or compiled into your kernel? If so, does it = keep happening without aio? > [ =E2=80=A6 ] > Thanks for the suggestion, but, no. This is on my trusty Lenovo T520 = laptop and no aio to be found. My configuration is just: > include GENERIC > ident GENERIC_BSD4 >=20 > nooptions SCHED_ULE # ULE scheduler > options SCHED_4BSD # 4BSD scheduler >=20 > I still can't be sure if the problem was triggered by the move to VB 5 = or t FreeBSD-11 (or a combination of both). Yes, the problem could be in many places. However, if you=E2=80=99ve = gone to FreeBSD 11, you have more aio than you think. =46rom UPDATING: 20160301: The AIO subsystem is now a standard part of the kernel. The VFS_AIO kernel option and aio.ko kernel module have been = removed. Due to stability concerns, asynchronous I/O requests are only permitted on sockets and raw disks by default. To enable asynchronous I/O requests on all file types, set the vfs.aio.enable_unsafe sysctl to a non-zero value. Are you running the VM against a raw disk device? You can check the = VBox.log output =E2=80=94 If you are not using aio, you should see an = entry like this: AIO: Async I/O manager not supported (rc=3DVERR_NOT_SUPPORTED). Falling = back to simple manager If you are using AIO, you will should see entries like: AIOMgr: Default manager type is "Async" AIOMgr: Default file backend is =E2=80=9CNonBuffered" AIO issues were not a big issue for a long time but some recent updates = to 4.3.something (or other environmental issues, possibly load) led me = to turn aio off on a bunch of 10.x machines running a significant number = of VMs (~25). I=E2=80=99m have been curious about whether the aio change = would cause problems with an upgrade to 11. Regards, Jan.