Date: Fri, 15 Apr 2016 07:29:23 -0600 From: Warner Losh <imp@bsdimp.com> To: Ivan Klymenko <fidaj@ukr.net> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Heads up Message-ID: <CANCZdfqC5yAO35N3A-9Nus5HpAujHzcy=t=nKGdT7BVf8-_G8g@mail.gmail.com> In-Reply-To: <20160415114443.660453cb@nonamehost.local> References: <CANCZdfpnYnVrvhNagYUT9RhAuC1AMCrxh=GCt8RKT0bqxuJybw@mail.gmail.com> <20160415114443.660453cb@nonamehost.local>
next in thread | previous in thread | raw e-mail | index | archive | help
Do you have this problem w/o CAM_NETFLIX_IOSCHED? What version of virtualbox? I've not booted with that in 3 years. Warner On Fri, Apr 15, 2016 at 2:44 AM, Ivan Klymenko <fidaj@ukr.net> wrote: > On Thu, 14 Apr 2016 16:42:33 -0600 > Warner Losh <imp@bsdimp.com> wrote: > > > The CAM I/O scheduler has been committed to current. This work is > > described in > > https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf though the > > default scheduler doesn't change the default (old) behavior. > > > > One possible issue, however, is that it also enables NCQ Trims on ada > > SSDs. There are a few rogue drives that claim support for this > > feature, but actually implement data corrupt instead of queued trims. > > The list of known rogues is believed to be complete, but some caution > > is in order. > > > > Warner > > Hi. > Thanks for you work. > But i have problem with VirtualBox if i use the kernel with option > CAM_NETFLIX_IOSCHED > http://imgur.com/JpcfW1h >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqC5yAO35N3A-9Nus5HpAujHzcy=t=nKGdT7BVf8-_G8g>