From owner-freebsd-current@freebsd.org Mon Mar 29 05:17:35 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EA1895BC0FC for ; Mon, 29 Mar 2021 05:17:35 +0000 (UTC) (envelope-from dg@dglawrence.com) Received: from dglawrence.com (dglawrence.com [50.76.111.10]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mailx.dglawrence.com", Issuer "mailx.dglawrence.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F816k6TRcz4bWp; Mon, 29 Mar 2021 05:17:34 +0000 (UTC) (envelope-from dg@dglawrence.com) Received: from mailx.dglawrence.com ([10.19.1.8]) by dglawrence.com (8.15.2/8.15.2) with ESMTPS id 12T5HW7v053710 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 28 Mar 2021 22:17:32 -0700 (PDT) (envelope-from dg@dglawrence.com) Received: (from dg@localhost) by mailx.dglawrence.com (8.15.2/8.15.2/Submit) id 12T5HWUV053709; Sun, 28 Mar 2021 22:17:32 -0700 (PDT) (envelope-from dg@dglawrence.com) Date: Sun, 28 Mar 2021 22:17:32 -0700 From: David G Lawrence To: Gleb Popov Cc: FreeBSD Current Subject: Re: 13.0 RC4 might be delayed Message-ID: <20210329051732.GJ46884@mailx.dglawrence.com> References: <2766233C-3CC7-4B02-95AB-7555A60FFD81@samsco.org> <9c49b2b1-6c49-410b-fbb2-a3b73618b01c@gmail.com> <20210327050411.GS15485@mailx.dglawrence.com> <5f4c94c2-df08-60ca-4dfc-31364fb444be@madpilot.net> <1b3605eb-388e-283b-d907-67058ea62c0a@madpilot.net> <20210329013713.GA52047@mailx.dglawrence.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (dglawrence.com [10.19.1.8]); Sun, 28 Mar 2021 22:17:32 -0700 (PDT) X-Rspamd-Queue-Id: 4F816k6TRcz4bWp X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.99 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[dglawrence.com:s=ab7ba439]; FREEFALL_USER(0.00)[dg]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[50.76.111.10:from:127.0.2.255]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[dglawrence.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[dglawrence.com,quarantine]; NEURAL_HAM_SHORT(-0.99)[-0.994]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[50.76.111.10:from]; ASN(0.00)[asn:7922, ipnet:50.76.0.0/14, country:US]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Mar 2021 05:17:36 -0000 > On Mon, Mar 29, 2021 at 4:37 AM David G Lawrence via freebsd-current < > freebsd-current@freebsd.org> wrote: > > > > > On 27/03/21 06:04, David G Lawrence via freebsd-current wrote: > > > >>> On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin < > > grahamperrin@gmail.com> > > > >>> wrote: > > > >>> > > > >>>> On 26/03/2021 03:40, The Doctor via freebsd-current wrote: > > > >>>>> ??? if people are having issues with ports like ??? > > > >>>> > > > >>>> If I'm not mistaken: > > > >>>> > > > >>>> * 13.0-RC3 seems to be troublesome, as a guest machine, with > > > >>>> emulators/virtualbox-ose 6.1.18 as the host > > > >>>> > > > >>>> * no such trouble with 12.0-RELEASE-p5 as a guest. > > > >>>> > > > >>>> I hope to refine the bug report this weekend. > > > >>>> > > > >>> > > > >>> Had nothing but frequent guest lockups on 6.1.18 with my Win7 > > system. > > > >>> That > > > >>> was right after 6.1.18 was put into ports. Fell back to legacy (v5) > > and > > > >>> will try again shortly to see if it's any better. > > > >> > > > >> Kevin, > > > >> > > > >> ?????? Make sure you have these options in your /etc/sysctl.conf : > > > >> > > > >> vfs.aio.max_buf_aio=8192 > > > >> vfs.aio.max_aio_queue_per_proc=65536 > > > >> vfs.aio.max_aio_per_proc=8192 > > > >> vfs.aio.max_aio_queue=65536 > > > >> > > > >> ?????? ...otherwise the guest I/O will random hang in VirtualBox. > > This > > > >> issue was > > > >> mitigated in a late 5.x VirtualBox by patching to not use AIO, but > > the > > > >> issue > > > >> came back in 6.x when that patch wasn't carried forward. > > > > > > > > Sorry I lost that patch. Can you point me to the patch? Maybe it can > > be > > > > easily ported. > > > > > > > > > > I found the relevant commit. Please give me some time for testing and > > > I'll put this patch back in the tree. > > > > If you're going to put that patch back in, then AIO should probably be > > made an option in the port config, as shutting AIO off by default will > > have a significant performance impact. Without AIO, all guest IO will > > be become synchronous. > > > > Are you sure about that? Without AIO, VBox uses a generic POSIX backend, > which is based on pthread, I think. No, I'm not sure - I haven't looked at the code. My comment is based on some comments that a VirtualBox developer made in a forum 3-4 years ago where he said that the "generic POSIX" IO was very simple and never intended to be used in production - only as a placeholder when developing for a new host platform. Are you sure that it does multi-threaded IO? -DG