From owner-freebsd-emulation@freebsd.org Tue Aug 23 04:37:21 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 36E6BBC3021 for ; Tue, 23 Aug 2016 04:37:21 +0000 (UTC) (envelope-from kob6558@gmail.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 11021173E for ; Tue, 23 Aug 2016 04:37:21 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 0C9A3BC3020; Tue, 23 Aug 2016 04:37:21 +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 0C3C6BC301F for ; Tue, 23 Aug 2016 04:37:21 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C56D4173D for ; Tue, 23 Aug 2016 04:37:20 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-it0-x22b.google.com with SMTP id e63so126887672ith.1 for ; Mon, 22 Aug 2016 21:37:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=yA/ynwqsYJkWoxj7kcBoV48Ovd6QH6uax1yqzWnQ0Ok=; b=ja6rQFI7R9CifvQBnC5rS4P4hjYL50uMJ2joW0lMBlU+CuJed48BDANBWh2lkVQ5s8 aJyZW7tj2P1lmuSf/FYJdI0IQT19rJog7aguvxYYYJvc2RDArRZMneSsmrpyGcH8lHXn ipBpFo/hqF3fm9bybTQEf5lfqfEdHzNi0JcD4Yx5aPeq/gX2Q3Oe5Zv46FRGM2SkYc8i kn+I1cJ+XM2iEOuMEyBEzc0NzSyQCfT6IyXPJSvY5lOKH6CKFQ31pb+/KwpFbIHRi/L5 GC79smabJ/XWGrf/MWPxu5O8CxcehNxFhVZe7oHXKDnrM/jRyOcJ3HOZP7hUb4hm8kO+ 7goA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=yA/ynwqsYJkWoxj7kcBoV48Ovd6QH6uax1yqzWnQ0Ok=; b=dtInhLt904K5EWSyyjFWLeUi2Pu0t6ehZuq4x7FU4jNSJ/r1nr6Pvx1alht/muvaXY JP1+0vmBDdDzntIeDxciabnQbu95caHidMSKdNRhASEPrvQF7atkplda2INc7lkB4Wg1 qX/m2EMx8Ohw3nHD8ayIJ267N1MJPjJbt/rS2JsiFLWZH3R1nToo75Uq+LOSXlnsq4FC 4DM2vvHvynibLgsyXUT7zJTciVYl0QKNvx6jf2J3m51tDWhBJODgPYFhYaS+SecFGN6S TmeYP1CK54N1rUcv1lnaj6brgqjfWI7jF38tTVZmi53inhstu1EQGtJrycPfwhifBU0I Ferg== X-Gm-Message-State: AEkoousXLGzhulHego1lr4ijV4lSBnXUSR6++VngVcKxBTm2fBJYXc8Sv99fH6CQffq2IzzAfrnqY+QdiM2mGw== X-Received: by 10.107.25.14 with SMTP id 14mr26633904ioz.168.1471927040198; Mon, 22 Aug 2016 21:37:20 -0700 (PDT) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.79.119.144 with HTTP; Mon, 22 Aug 2016 21:37:19 -0700 (PDT) In-Reply-To: References: <2418C811-3C6E-4837-B6A5-51DB4C425EB4@transactionware.com> <59E9F6CE-0F2B-40E1-B78D-AF9DFBCED280@transactionware.com> From: Kevin Oberman Date: Mon, 22 Aug 2016 21:37:19 -0700 X-Google-Sender-Auth: AeH3y4PCPeIRjuKUOmp_hPzJx4g Message-ID: Subject: Re: Odd behavior with virtualbox-ose-4.3.38 To: Jan Mikkelsen Cc: "freebsd-emulation@freebsd.org" 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: Tue, 23 Aug 2016 04:37:21 -0000 On Mon, Aug 22, 2016 at 4:30 PM, Kevin Oberman wrote: > On Mon, Aug 22, 2016 at 12:54 PM, Jan Mikkelsen > wrote: > >> Hi, >> >> On 23 Aug 2016, at 02:25, Kevin Oberman wrote: >> >> 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 kee= p >>> 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 >> >> nooptions SCHED_ULE # ULE scheduler >> options SCHED_4BSD # 4BSD scheduler >> >> I still can't be sure if the problem was triggered by the move to VB 5 o= r >> t FreeBSD-11 (or a combination of both). >> >> >> Yes, the problem could be in many places. However, if you=E2=80=99ve gon= e to >> FreeBSD 11, you have more aio than you think. From 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 en= try 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 t= o >> 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 wo= uld cause >> problems with an upgrade to 11. >> >> Regards, >> >> Jan. >> >> > BINGO! > > Thank you so much, Jan! This does explain a great deal of what I was > seeing and why. > > Now the question... how can I disable it? I'm guessing that > "kern.features.aio=3D0" in /boot/loader.conf might do the trick, but the = man > page does not mention this at all. Also, I guess it is time to open a bug > report on this. FWIW, the problem does seem to be linked to disk activity= . > I had the system locked up and had to kill the process. When I rebooted, > the system told me that a disk check was needed, but I had it lock up > several time (3, I think) before it made it through the check without > locking up again. Once that was complete, the system started and ran > normally again. This also now fits rather well with an aio issue. > > Not too sure how to go about collecting more information for the PR,but > I'll open it with what I have. > > Thanks again, Jan! > -- > Kevin Oberman, Retired Network Engineer > FYI, there is a PR on this. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D168298 I have updated the ticket with what I have seen, especially that it is not ZFS specific. I have also made the adjustment in sysctls as shown in the ticket (comment 3) and will see how things works. -- Kevin Oberman, Retired Network Engineer E-mail: rkoberman@gmail.com