Re: Heads up

I'll try virtualbox again, but it booted fine when I tried it before.
I'll give bhyve a sping. I haven't tried it in quite some time, but
it worked about 9 months ago.

But since I don't even know what the errors you are seeing are,
I can't tell you that it is similar to some other error reports or
something completely new.

Warner


On Sun, Apr 24, 2016 at 11:49 AM, Ivan Klymenko <fidaj_at_ukr.net> wrote:

> On Fri, 15 Apr 2016 11:44:43 +0300
> Ivan Klymenko <fidaj_at_ukr.net> wrote:
>
> > On Thu, 14 Apr 2016 16:42:33 -0600
> > Warner Losh <imp_at_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
>
> This problem is not over.
> After the update on other hardware from r296979 to r298512 (!!! without
> option CAM_NETFLIX_IOSCHED !!!) due to errors in recording the virtual
> machine to a virtual disk I lost completely virtual machine with
> permanent damage to the integrity of the file system in the inside of
> the virtual machine.
>
> This is a serious bug!
>
> Who cares not to fall into the same situation - is testing yourself
> and needed more testers.
> Because there is a suspicion that the problem is also relevant for
> bhyve VM.
> With me on this no more neither the strength nor the desire nor
> time.
>
> Thanks.
>